Circuit Breaker Sourcing is an independent sourcing partner. Inquiries go through the RFQ form; no public mailbox is published on this site.

Procurement desk

Circuit Breaker Sourcing

Send specifications, quantity and destination. Circuit Breaker Sourcing is an independent sourcing partner; factory identity, listings and shipment terms belong to named supplier replies. No street address, telephone number or public map pin is published.

How communication works

Work email on the form is the follow-up channel for the same requirement record. Hours are not a walk-in counter. Messages are reviewed as written inquiries. Social channels are not used as a substitute for the requirement field. Optional budget (amount or range, currency, per unit or whole order) and high-end, mid-range, budget or undecided supplier preference can be included. They are buying notes, not verified ratings and not existing quotations.

  • Work email for follow-up on this requirement
  • No invented showroom address or mapped pin
  • No published telephone queue
  • Review window: written inquiries, not same-hour installation dispatch
Illustration of a breaker specification brief handing off to a quotation folder, not a storefront map
Requirement handoff sketch. Not a warehouse, showroom or mapped office.

What to include

  • Product type and intended application (branch, feeder, main or enclosure assembly)
  • Quantity by specification and unit
  • Rated voltage with AC or DC and phase, rated current in A, frequency in Hz
  • Poles, mounting or panel series, enclosure rating (NEMA or IP, not treated as equivalent) and trip interface
  • Interrupting capacity in kA stated separately from rated current in A
  • Destination state or postal code and requested delivery date
  • Required product documents and sample needs
  • Optional budget and supplier preference

Form notes

Name, work email and the procurement requirement field are the fields the endpoint already accepts. Auxiliary product, budget and preference controls, when visible, are merged into that same requirement field at submit. They are not extra backend names. Repeating submit or using the browser back button should not keep an old helper summary in the visible requirement text. If JavaScript is disabled, write budget currency and unit-or-order basis plus supplier preference into the textarea.

Continue from spec check when you already hold a catalog number that still needs a listing file.