Two paths, one goal
Every electronic product sold in the United States needs some form of FCC equipment authorization before it can legally reach the market. Since 2017, when the FCC consolidated the old Verification and Declaration of Conformity procedures, there are exactly two paths: Supplier's Declaration of Conformity (SDoC) and Certification.
Picking the wrong path wastes money. Picking no path at all risks enforcement action, customs seizure, and retailer delisting. This guide walks through how to determine which path applies to your product, what each path actually requires, and where teams consistently get tripped up.
What SDoC is (and is not)
SDoC stands for Supplier's Declaration of Conformity. Under 47 CFR Part 2, Subpart J, the supplier (manufacturer or importer) declares that the product complies with the applicable FCC technical standards. There is no government review, no FCC ID issued, and no public filing.
What SDoC is:
- A self-declaration that your product meets FCC emission limits
- Backed by testing at an accredited lab (ISO/IEC 17025)
- Your legal assertion that production units match the tested configuration
- A recordkeeping obligation -- you must retain test reports and make them available if the FCC asks
What SDoC is not:
- A free pass to skip testing
- An exemption from FCC rules
- A lesser standard of compliance
The emission limits your product must meet under SDoC are identical to those under Certification. The difference is procedural: who reviews the test results and whether a government-issued identifier (FCC ID) is created.
What Certification requires
Certification is the more rigorous procedural path. Your product is tested at an FCC-recognized accredited lab, and the results are reviewed by a Telecommunication Certification Body (TCB) -- a private organization authorized by the FCC to evaluate applications. If the TCB determines your product complies, it issues an FCC grant with a unique FCC ID in the format GRANTEE-PRODUCT.
The FCC ID becomes a public record in the FCC Equipment Authorization System (EAS) database. It must appear on the product label (or via e-labeling for devices with displays). The grant is permanent unless revoked.
The core rule: intentional vs unintentional radiators
The distinction that determines your authorization path comes from 47 CFR 15.3:
Intentional radiator: A device that deliberately generates and emits RF energy by radiation or induction as part of its core function. The RF emission is the point.
Unintentional radiator: A device that generates RF energy internally (all digital circuits do) but does not deliberately radiate it. The RF emission is a byproduct.
| Device Type | Intentional? | Authorization Path |
|---|---|---|
| WiFi router | Yes | Certification |
| Bluetooth speaker | Yes | Certification |
| LoRa sensor (custom RF) | Yes | Certification |
| USB hub | No | SDoC |
| LED driver | No | SDoC |
| Monitor | No | SDoC |
| Power supply | No | SDoC |
| BLE sensor with pre-certified module | Module: yes (already certified) / Host: no | Host uses SDoC |
The last row is critical. When you use a pre-certified module (like ESP32-WROOM or nRF52840), the module's existing FCC ID covers the intentional radio emissions. Your host product only needs Part 15 Subpart B unintentional emissions testing, which follows the SDoC path.
Part 15 subpart breakdown
Understanding which subpart applies to your device clarifies what testing you need and which authorization path to follow.
Part 15 Subpart B -- Unintentional radiators
Subpart B covers devices that use digital circuitry internally but do not intentionally emit RF. It defines two classes:
- Class A: Commercial/industrial environments. Limits are more lenient.
- Class B: Residential environments. Limits are approximately 10 dB stricter than Class A.
If your product will be used in homes (which includes most consumer electronics), you must meet Class B limits. The authorization path is SDoC.
Testing scope under Part 15B:
- Radiated emissions: 30 MHz to 40 GHz
- Conducted emissions on AC mains: 150 kHz to 30 MHz (per
15.207) - Measurement procedures per
ANSI C63.4
Typical cost: $800 -- $2,000 for bare testing; $1,500 -- $5,000 including documentation.
Part 15 Subpart C -- Intentional radiators
Subpart C covers low-power intentional radiators that do not fall under a more specific subpart. This includes RF remote controls, wireless doorbells, garage door openers, key fobs, baby monitors, and low-power wireless microphones.
Authorization path: Certification (FCC ID required).
Testing includes radiated emissions, conducted emissions, field strength measurements, spurious emissions, occupied bandwidth, and frequency stability.
Part 15.247 -- Spread spectrum and digital modulation (2.4 GHz, 900 MHz, 5.8 GHz)
This is the rule section governing most WiFi (2.4 GHz), Bluetooth, Zigbee, Z-Wave, Thread, LoRa (900 MHz), and other ISM band devices using spread spectrum or digital modulation.
Authorization path: Certification.
Testing is extensive: radiated emissions, conducted emissions, band edge compliance, occupied bandwidth, power spectral density, peak output power, antenna conducted power, and spurious emissions. For frequency-hopping systems, channel count and dwell time verification is also required.
Part 15.407 -- U-NII devices (5 GHz and 6 GHz WiFi)
Covers 5 GHz and 6 GHz unlicensed devices including WiFi 5, WiFi 6, WiFi 6E, and WiFi 7. Requires Dynamic Frequency Selection (DFS) testing for U-NII-2A and U-NII-2C bands to protect radar systems. Standard-power 6 GHz outdoor devices require Automated Frequency Coordination (AFC).
Authorization path: Certification.
DFS testing alone adds significant cost and complexity -- the lab must verify radar detection probability (minimum 60% per waveform), channel availability check timing (60 seconds minimum), and channel move time (10 seconds maximum).
Decision tree
Here is the practical decision flow:
Step 1: Does your product contain any electronic circuitry? No -- FCC authorization does not apply. Stop here. Yes -- Continue.
Step 2: Does your product intentionally transmit RF energy?
No -- Your product is an unintentional radiator. Path: SDoC under Part 15B. Cost: $800 -- $5,000.
Yes -- Continue.
Step 3: Does the intentional radiator use a pre-certified module?
Yes -- The module's FCC ID covers the radio. Your host needs Part 15B unintentional emissions testing only. Path: SDoC for the host. Cost: $2,500 -- $5,500.
No (custom RF design) -- You need full Certification. Cost: $8,000 -- $20,000+.
Step 4: Check for exemptions under 47 CFR 15.103.
A small number of device types are exempt: devices operating below 1.705 MHz, certain low-power devices, test equipment not marketed to end users, and government-operated equipment. These exemptions are narrow. If you are building a consumer product, assume you need authorization.
Cost and timeline comparison
| Factor | SDoC | Certification |
|---|---|---|
| Testing required | Yes | Yes |
| Lab accreditation | ISO/IEC 17025 | FCC-recognized + ISO/IEC 17025 |
| Third-party review | None | TCB review required |
| FCC ID issued | No | Yes |
| Government fee | $0 | ~$40 (grantee code, one-time) |
| Testing cost (unintentional radiator) | $800 -- $2,000 | N/A |
| Testing cost (host + pre-certified module) | $2,500 -- $5,500 | N/A |
| Testing cost (custom RF, single-band) | N/A | $8,000 -- $20,000 |
| Testing cost (multi-radio) | N/A | $15,000 -- $30,000 |
| TCB review fee | $0 | $1,000 -- $5,000 |
| Timeline | 1 -- 4 weeks | 4 -- 16 weeks |
| Public database listing | No | Yes (FCC EAS) |
The cost gap between SDoC and Certification is not about the emission limits (those are the same) -- it is about the scope of testing (RF parameters on top of EMC) and the procedural overhead of TCB review.
Common mistakes
Mistake 1: "SDoC means we don't need testing"
This is the most dangerous misconception. SDoC requires testing at an accredited lab against the same emission limits that apply under Certification. The "self-declaration" part refers to who reviews the results (you, not a TCB), not whether testing happens. Marketing an untested product under SDoC is a violation of 47 USC 302a.
Mistake 2: Confusing chip-down with module
Soldering a bare ESP32-S3 chip onto your PCB is not the same as using the ESP32-S3-WROOM module. The chip does not have modular approval. Without the module's shielding, power regulation, and antenna matching network, you need full intentional radiator Certification. This mistake typically costs $5,000 -- $15,000 to correct.
Mistake 3: Ignoring antenna modifications
If you use a pre-certified module but change the antenna (different type, different cable length, modified ground plane), the module's grant conditions may no longer apply. The module's FCC grant specifies antenna requirements. Violating them can void the modular approval and push you back to the Certification path. Check KDB 996369 D04 for host integration requirements.
Mistake 4: No SDoC recordkeeping
SDoC has no public filing, but you are legally required to keep all test reports, the compliance statement, and documentation showing production units match the tested configuration. The FCC can request these records at any time. Customs and Border Protection can also demand proof of FCC compliance at import. Teams that skip recordkeeping find this out when a shipment gets held at the port.
Mistake 5: Assuming SDoC covers the whole product
If your product has both unintentional emissions (digital circuitry) and intentional emissions (a radio transmitter), the SDoC only covers the unintentional emissions portion. The intentional radiator still needs either its own FCC ID (if custom RF) or coverage under a pre-certified module's grant. You cannot SDoC your way out of Certification for the radio.
When SDoC is the right choice
SDoC is the correct path when:
- Your product is a pure digital device with no intentional RF transmission (USB hub, LED controller, power supply, display)
- Your product uses a pre-certified RF module and you have not modified the antenna or exceeded the module's grant conditions
- You want the fastest, lowest-cost path to market for an unintentional radiator
When Certification is unavoidable
You need Certification when:
- Your product uses a custom RF design (chip-down, no pre-certified module)
- You are designing a new RF module intended for sale to other manufacturers
- Your product operates under
Part 15C,Part 15.247, orPart 15.407with no pre-certified module - You have modified a pre-certified module's antenna in ways that exceed the module grant's conditions
The hybrid scenario: most IoT products
The most common path for IoT and connected consumer products is a hybrid: SDoC for the host device + a pre-certified module's existing FCC ID for the radio. This gives you the speed and cost advantages of SDoC while using the module vendor's existing Certification to cover the radio.
Under this approach:
- Select a pre-certified module with full (unrestricted) modular approval
- Follow the module's grant conditions for antenna type, cable length, and separation distance
- Test your host product for
Part 15Bunintentional emissions at an accredited lab - Self-declare compliance (SDoC) for the host
- Label your product with "Contains FCC ID: XXXXX-YYYYYY" referencing the module
- Include the
Part 15compliance statement in your user manual - Retain all test documentation
Total cost: $2,500 -- $5,500. Timeline: 3 -- 6 weeks. This is how the vast majority of WiFi-enabled consumer devices reach market.
Bottom line
The authorization path is not a choice you make -- it is determined by what your product does. Intentional radiators need Certification. Unintentional radiators use SDoC. Pre-certified modules let you shift the intentional radiator Certification to the module vendor and keep your host on the faster, cheaper SDoC path.
Get the classification right first. Everything else follows from that.
Found an error or something out of date? Let us know.