Any electronic product sold in the US that oscillates above 9 kHz — which in practice means virtually every modern electronic device — must comply with FCC rules before it goes to market. There are two paths: Supplier's Declaration of Conformity (SDoC) for products without intentional radio transmitters, and FCC Certification through an accredited Telecommunication Certification Body (TCB) for anything with Wi-Fi, Bluetooth, cellular, or other intentional radios. Budget roughly a few thousand dollars for simple SDoC testing and roughly $8,000–$30,000+ for certification of a transmitting device, with lab-to-approval timelines commonly running four to twelve weeks once your design is stable.

Which path does your product need?

  • Unintentional radiator → SDoC. Digital devices that generate radio-frequency noise as a byproduct — anything with a microcontroller, display, or switching power supply. You test at a lab, keep the report, and declare compliance yourself. No FCC ID required.
  • Intentional radiator → Certification. Devices that transmit on purpose: Wi-Fi, Bluetooth, LoRa, Zigbee, cellular, custom RF links. An accredited lab tests the device, a TCB reviews and grants the authorization, the device gets an FCC ID, and it is listed in the FCC database.

The strategic shortcut most electronics development teams use: build around a pre-certified radio module. Using a module with its own modular approval means your radio is already certified — your finished product typically still needs unintentional-radiator testing, but you avoid the full (and most expensive) intentional-radiator campaign. This one architecture decision routinely saves five figures and months of schedule, which is why it features heavily in our breakdown of IoT product development costs.

What testing involves

In an accredited EMC lab — usually an anechoic chamber — your device is measured for radiated emissions (RF energy escaping the product), conducted emissions (noise pushed back into the power line), and for transmitters, occupied bandwidth, output power, spurious emissions, and band-edge behavior. Devices with radios near the body may also need RF exposure (SAR) evaluation. The device must be exercised in its worst-case operating mode during testing — labs will ask you for a test firmware build that locks the radio on at maximum power, something your embedded software team should plan for in advance.

Cost and timeline, realistically

  • SDoC testing: commonly a few thousand dollars and one to two weeks of lab time for a well-behaved product.
  • Certification with a pre-certified module: moderate additional testing on top of SDoC-level work.
  • Full certification of a custom radio: often $10,000–$30,000+ across testing and TCB fees, and more for cellular devices, which also need carrier and industry approvals.
  • The hidden cost: failure. A meaningful share of products fail EMC testing on the first attempt. Every failure means debugging, board revision, and a return trip to the lab — the real reason experienced teams do a cheap pre-scan early rather than betting the schedule on one formal session.

Design for compliance from the first schematic

EMC performance is designed in, not tested in. The practices that make boards pass: solid ground planes and careful return paths, decoupling at every IC, slew-rate control on fast edges, filtering at every cable entry (cables are the antennas that fail products), shielding where geometry allows, and disciplined layout around switching regulators and radio sections. This is standard craft in professional electronics design — and retrofitting it into a finished board costs far more than doing it right the first time. Compliance planning belongs in the same early conversation as the broader test strategy covered in product safety testing requirements — FCC covers interference, while UL-style safety and CPSC consumer rules are separate obligations, and products for other markets need CE and similar marks planned alongside.

Labeling and paperwork

Certified devices must display their FCC ID on the product label; SDoC products need US-based responsible-party information in their documentation. Both paths require compliance information in the user manual, and e-labeling is allowed for devices with screens. Keep test reports and technical documentation on file — the obligation to demonstrate compliance continues for as long as you market the device, and it lands on the party whose name is on the product, wherever the units are actually built by your manufacturing partner.

Get your product through the chamber on the first pass

Projects House designs electronics with FCC compliance as a requirement from day one — module-based radio strategy, EMC-aware layout, pre-scan testing before the formal lab — and manages the certification campaign with accredited labs. Tell us about your device through the contact form and we will map out the cheapest compliant path to putting it on the US market.