FCC Certification: The Complete Guide

If you're building an electronic product for the US market, FCC equipment authorization isn't optional. Every device with electronic circuitry needs some form of FCC compliance before it can be legally sold, whether it's a USB charger or a 5G smartphone. The process is governed by 47 CFR Part 2, Subpart J and Part 15.

This guide covers the full certification journey: figuring out which authorization path applies to your product, what testing looks like, how the TCB review works, what it costs, how long it takes, and where teams get tripped up. Each section links to a deep-dive article for the full picture.

Who needs FCC authorization

Almost everyone shipping electronics in the United States. The FCC regulates the sale and marketing of devices that emit radio frequency energy. That includes any product with a digital clock, a microprocessor, a switching power supply, or (obviously) a radio.

There are three categories your product falls into:

Intentional radiators deliberately generate and emit RF energy. WiFi routers, Bluetooth speakers, LoRa gateways, cellular modems, NFC readers, garage door openers, key fobs. If your design includes a component whose purpose is to radiate RF, you have an intentional radiator. These require Certification (an FCC ID issued by a TCB).

Unintentional radiators generate RF as a byproduct of their operation. Computers, monitors, LED drivers, motor controllers, power supplies, USB hubs. The clock oscillator and digital bus traces in these devices emit RF even though that's not their purpose. These typically go through SDoC (Supplier's Declaration of Conformity).

Exempt devices are narrow exceptions under 47 CFR 15.103: purely mechanical products, passive cables, devices operating below 1.705 MHz, certain government equipment, and a handful of other specific categories. Don't count on your product being exempt unless you've checked the regulation carefully.

If you're unsure where your product falls, our Do You Need FCC Certification? guide walks through the full decision process step by step.

Certification vs SDoC: the two authorization paths

Since 2017, the FCC has two equipment authorization procedures. The old "Verification" and "Declaration of Conformity" paths were folded into SDoC. Which path applies to your product determines your cost, timeline, and regulatory obligations, so get this right before anything else.

flowchart TD
    A["Does your product\ncontain electronics?"] -->|No| B["No FCC authorization\nrequired"]
    A -->|Yes| C{"Does it intentionally\ntransmit RF?"}
    C -->|No| D["Unintentional radiator\n→ SDoC path"]
    C -->|Yes| E{"Using a pre-certified\nRF module?"}
    E -->|Yes| F["Host device → SDoC\nModule covers RF grant"]
    E -->|No| G["Full Certification\nrequired → FCC ID"]
    style B fill:#1e3a5f,color:#fff
    style D fill:#1e3a5f,color:#fff
    style F fill:#1e3a5f,color:#fff
    style G fill:#1e3a5f,color:#fff

Certification (FCC ID required)

Certification is the more rigorous route. It applies to intentional radiators and produces an FCC ID, a unique identifier in the format GRANTEE-PRODUCT (e.g., 2A2UNR3D00) that gets listed in the FCC's public Equipment Authorization System (EAS) database.

The process: you test at an FCC-recognized accredited lab, compile a technical submission package, and file through a Telecommunication Certification Body (TCB). The TCB reviews your test report, documentation, and labeling for compliance, then issues the grant. Typical cost runs $3,000–$20,000+ and takes 4–12 weeks depending on device complexity.

SDoC (self-declaration)

SDoC is the lighter path. It applies to unintentional radiators, digital devices that emit RF as a byproduct rather than by design. You still need to test at an accredited lab, but there's no TCB review, no FCC ID, and no government filing fee.

After testing confirms your device meets the applicable Part 15 Subpart B limits, you self-declare compliance. You keep the test report on file (the FCC can request it at any time), include the required compliance statement in your user manual, and label the product appropriately.

Typical cost: $800–$5,000. Timeline: 1–4 weeks.

The hybrid path: pre-certified modules

This is the path most IoT and connected device teams actually take. If your product uses a pre-certified RF module (ESP32-WROOM, nRF52840, QCA6174A, etc.), the module's existing FCC ID covers the intentional radio emissions. Your host device only needs Part 15B unintentional emissions testing via the SDoC path.

This is the most common path for IoT products, smart home devices, and wearables. It cuts certification cost by 60–80% and roughly halves the timeline. Our Pre-Certified Modules & Host Device Testing guide covers the requirements in detail, including the eight conditions for modular approval under KDB 996369 and what host-level testing you still need.

For a full breakdown of which path applies to which device type, see SDoC vs Certification: Which FCC Path Is Right for Your Product?.

The certification process from start to finish

The full process from first prototype to a shippable FCC ID has eleven steps. The walkthrough below focuses on the Certification path. If you're on the SDoC path, skip steps 2, 9, and 10.

flowchart LR
    A["1. Register\nwith FCC"] --> B["2. Get\nGrantee Code"]
    B --> C["3. Determine\nAuth Path"]
    C --> D["4. Select\nTest Lab"]
    D --> E["5. Pre-Compliance\n(optional)"]
    E --> F["6. Formal\nTesting"]
    F --> G["7. Test Report\nGeneration"]
    G --> H["8. TCB\nSubmission"]
    H --> I["9. TCB\nReview"]
    I --> J["10. Grant\nIssued"]
    J --> K["11. Label,\nShip, Sell"]
    style A fill:#1e3a5f,color:#fff
    style F fill:#1e3a5f,color:#fff
    style J fill:#1e3a5f,color:#fff

Step 1: Register with the FCC (1–2 days)

Create an FCC Registration Number (FRN) through the CORES system. It's free and fast. You need this before any equipment authorization activity.

Step 2: Obtain a Grantee Code (1–2 days)

Apply at the FCC Grantee Registration site. Your grantee code is a 3- to 5-character alphanumeric string that becomes the first part of your FCC ID. Fee is approximately $40 (post-2025 CPI adjustment under 47 CFR 1.1103). You can do this any time before TCB submission. No rush, but don't leave it for the last minute.

Step 3: Determine your authorization path

Use the decision tree above. The key question is whether your device intentionally transmits RF. If yes and you're not using a pre-certified module, you need full Certification. If no, or if your radio is a pre-certified module, SDoC handles it.

Step 4: Select a test lab (1–2 weeks)

Choose an FCC-recognized lab with ISO/IEC 17025 accreditation from a recognized body (A2LA, NVLAP, or equivalent). What to look for:

• Experience with your device type. A lab that tests Bluetooth speakers every week will move faster on yours.
• Turnaround time and current queue. Post-CES (January–March) and pre-holiday (July–September) are peak seasons. Book 4–6 weeks ahead during these periods.
• Combined lab + TCB. Organizations like UL, Intertek, Bureau Veritas, TUV SUD, and Nemko operate both test labs and TCBs under one roof. Using one eliminates the 3–7 day lab-to-TCB handoff.
• Location. US labs are the straightforward choice. Taiwan-based labs are absorbing overflow as capacity shifts in the testing market.

Step 5: Pre-compliance testing (optional but high-ROI, 1–3 weeks)

Roughly 50% of consumer electronics fail formal EMC testing on the first attempt. Each failure triggers a redesign-rebook-retest cycle that adds $5,000–$30,000 and 4–12 weeks.

Pre-compliance testing catches most of these issues before you burn money on formal lab time. A basic setup (spectrum analyzer, LISN, near-field probes) runs $3,000–$8,000 to buy outright. Even renting a pre-compliance bench for $500–$2,000 per day pays for itself. Teams that do pre-compliance drop their first-pass failure rate below 10%.

Step 6: Formal compliance testing (3 days to 3 weeks)

The lab performs all required measurements per your applicable rule parts:

• All devices: Radiated emissions, conducted emissions
• Intentional radiators add: Spurious emissions, band edge, output power, occupied bandwidth
• If applicable: SAR testing (body-worn or handheld devices), receiver testing

You'll need 2–3 production-representative test samples. That word "production-representative" matters: hand-soldered prototypes with different PCB stackups can behave differently from production units, and labs can reject samples that don't match the final product.

Testing duration depends on complexity. A straightforward SDoC for a digital device might take 1–3 days. A multi-radio Certification (WiFi + Bluetooth + Zigbee) can take 2–3 weeks.

Step 7: Test report generation (3–7 days)

The lab produces formal test reports per FCC/ANSI formatting requirements, documenting every measurement, test configuration, piece of equipment used, and pass/fail result. A typical report has 16 sections and includes the exhibits required under 47 CFR 2.1033.

Step 8: TCB submission

You submit a complete package to your chosen TCB:

• Formal test report(s)
• Internal and external product photos (annotated)
• Label artwork showing FCC ID placement
• User manual with FCC compliance statements
• Block diagram
• Operational description
• Schematics (may be filed under confidentiality)
• RF exposure evaluation (SAR report or MPE analysis if applicable)
• Antenna specifications

Incomplete submissions are the second most common cause of delays after test failures. Get this right the first time.

Step 9: TCB review (1–4 weeks)

The TCB doesn't re-run your tests. They review your submission for five things:

1. Completeness — all required documents present and properly formatted
2. Rule applicability — correct device classification, correct Part 15 subpart, correct rule sections
3. Compliance margins — measured values meet limits with appropriate measurement uncertainty
4. Labeling — FCC ID placement, user warnings, and compliance statements are correct
5. KDB compliance — submission follows applicable Knowledge Database guidance

If something's off, you'll get a deficiency letter. Each round of back-and-forth adds 1–2 weeks. Complex multi-radio devices commonly go through 2–3 rounds.

Step 10: Grant issued (1–3 days)

The TCB uploads the grant to the FCC EAS database. Your FCC ID is live and publicly searchable. You can legally market and sell the product in the United States.

Step 11: Label, ship, sell

Affix the FCC ID to your device (minimum 4-point font, readily visible), include the required statements in your user manual, and ensure production units match the tested configuration. Our FCC Label Requirements guide covers physical labels, electronic labeling under 47 CFR 2.935, and the common mistakes that trigger enforcement.

How much FCC certification costs

Cost depends almost entirely on two things: does your device have a radio, and is that radio a pre-certified module or custom silicon?

The FCC itself charges almost nothing — about $40 for a grantee code. The real cost is lab testing (40–50% of total), TCB review (15–20%), and documentation prep (10–15%). The biggest hidden cost is re-testing after a first-pass failure: budget a 50% contingency if this is your first product.

Our FCC Certification Cost Breakdown covers every line item, including the hidden costs that don't show up in initial lab quotes.

Timeline: what to actually expect

Lab testing is rarely the bottleneck. Queue time, documentation prep, and deficiency rounds usually eat more calendar time than the actual measurements.

These are typical timelines. Best case runs about 30% faster. Worst case, particularly when test failures enter the picture, can double these numbers.

For the full phase-by-phase walkthrough with acceleration strategies, see FCC Testing Timeline: What to Expect from Lab to Approval.

The TCB system: who actually grants your FCC ID

Most people assume the FCC reviews equipment authorization applications directly. It doesn't. Since 1999, that job has been delegated to Telecommunication Certification Bodies (TCBs), private accredited organizations that review test reports and issue grants on the FCC's behalf.

The accreditation chain goes four layers deep:

1. NIST (via NVCASE) recognizes accreditation bodies
2. Accreditation bodies (A2LA, NVLAP, ANAB, etc.) accredit TCBs against ISO/IEC 17065
3. TCBs are designated by the FCC for specific scope categories (A1–B4)
4. Grants are uploaded to the FCC EAS database as the official public record

Each TCB is authorized for a subset of eight scope categories. The main ones hardware teams encounter:

• A1/B1 — Unintentional radiators (Part 15B digital devices)
• A2/B2 — Low-power intentional radiators (WiFi, Bluetooth, Zigbee — the bulk of consumer IoT)
• A3/B3 — Licensed services (cellular, land mobile radio)
• A4/B4 — UNII and emerging unlicensed spectrum (5 GHz WiFi, 6 GHz AFC devices, UWB)

When picking a TCB, verify their designation covers your device's scope category. A TCB without A4 designation can't grant a 6 GHz WiFi device no matter how good they are at everything else.

What matters when choosing a TCB

Not all TCBs are interchangeable. The differences that matter:

• Turnaround. Ranges from about 1 week (rush, premium fee) to 6+ weeks depending on load and complexity.
• Device-type experience. A TCB that regularly handles your type of device will catch issues earlier and move faster.
• Bundled lab + TCB. UL, Intertek, Bureau Veritas, and TUV SUD all operate both. One vendor relationship, no handoff delay, often bundled pricing.
• PAG experience. For devices on the FCC's Pre-Approval Guidance list (novel technologies that require FCC sign-off before TCB grant), you want a TCB with a track record of successful pre-approvals.

FCC rule parts: which regulations apply to your device

The specific regulations your product must comply with depend on what it does. Here are the rule parts hardware teams encounter most often:

Many devices span multiple rule parts. A WiFi + Bluetooth smart speaker might need testing under Part 15.247 (for the Bluetooth and 2.4 GHz WiFi), Part 15.407 (for 5 GHz WiFi), and Part 15 Subpart B (for unintentional emissions from the digital circuitry). Each rule part adds testing scope and cost.

Post-grant obligations: what happens after you get your FCC ID

Getting the grant is not the finish line. You now have ongoing obligations.

Labeling

Every certified device must display FCC ID: XXXXX-YYYYYY in a permanent, readily visible location (minimum 4-point font). Devices using pre-certified modules display Contains FCC ID: XXXXX-YYYYYY. SDoC devices need the Part 15 compliance statement but no FCC ID.

Electronic labeling (e-labeling) under 47 CFR 2.935 is available for devices with integrated displays, but it supplements physical labeling. It doesn't replace it in all cases. E-labeling requires no more than three menu steps to reach the regulatory information, and the display path must be write-protected against user modification.

Details in our FCC Label Requirements guide.

Permissive changes

After your product is certified, modifications to the hardware or firmware may trigger re-authorization:

The rules are in 47 CFR 2.1043. The principle is simple: any change that could affect emissions characteristics requires at minimum a permissive change evaluation. Don't guess. Have your TCB advise on classification. The enforcement consequences are real: HobbyKing paid $2.86 million and Sound Around paid $1.2 million for violations that included unauthorized modifications.

Production consistency

Your production units must match the tested configuration. Material changes to the PCB layout, components, antenna, or firmware that could affect emissions characteristics trigger the permissive change evaluation above. Good configuration management and golden sample documentation aren't optional here. You need to demonstrate that what's shipping matches what was tested.

Common pitfalls and how to avoid them

The same mistakes come up again and again in FCC filings. These are the ones that actually cost teams time and money:

1. Skipping pre-compliance testing. Roughly half of consumer electronics fail formal EMC testing on the first pass. Each failure adds 4–12 weeks and $5,000–$30,000 to your program. Pre-compliance costs $3,000–$8,000 and drops the failure rate below 10%. The math isn't close.

2. Using prototype-quality samples for formal testing. Labs need production-representative units. Hand-soldered boards with different stackups, missing shielding, or prototype power supplies will produce results that don't reflect your production device. Some labs will reject non-representative samples outright.

3. Incomplete TCB submissions. Missing internal photos, label artwork that doesn't match the physical device, user manuals without the required FCC compliance statements — each gap triggers a deficiency letter and adds 1–2 weeks per round.

4. Misclassifying the authorization path. Treating an intentional radiator as an unintentional radiator (or vice versa) wastes time and can result in enforcement action. The distinction is based on whether your design deliberately radiates RF, not on power level or device size.

5. Ignoring module integration requirements. Dropping a pre-certified module onto your PCB doesn't automatically transfer the FCC grant. The module must meet the eight requirements for modular approval under KDB 996369. If you modify the antenna, use a limited modular approval module outside its conditions, or create co-location interference, additional testing is required.

6. Assuming the FCC ID is permanent. An FCC grant applies to the specific configuration that was tested. Material changes require a permissive change filing or new certification. Teams that iterate on hardware after certification without evaluating the permissive change implications are at risk.

7. Forgetting about RF exposure. Body-worn and handheld devices need SAR (Specific Absorption Rate) testing or an MPE (Maximum Permissible Exposure) evaluation. SAR testing for a multi-band cellular device can cost $10,000–$30,000 on its own. Even a simple BLE wearable needs at least a $500–$2,000 exemption analysis.

8. Not budgeting for peak season. Lab queue times surge in January–March (post-CES product rush) and July–September (pre-holiday launch window). During peak, a 2-week queue becomes 6 weeks. Book your lab 4–6 weeks ahead during these periods.

Cost reduction strategies

If you're looking to minimize certification spend without cutting corners:

Use a pre-certified module. For most IoT and connected products, nothing else moves the needle as much. The certification cost difference between a pre-certified ESP32 and a chip-down WiFi design is $5,500–$14,500. Below 50,000 units, modules almost always win on total cost even with the higher per-unit BOM. See Pre-Certified Modules & Host Device Testing.

Run FCC and ISED (Canada) together. Canada's ISED accepts FCC test reports for most device types under the US-Canada Mutual Recognition Agreement. Filing both simultaneously adds only $1,000–$3,000 and zero additional testing time.

Pick a combined lab + TCB. Using one organization for testing and certification eliminates the 3–7 day handoff delay and often saves on bundled pricing.

Get documentation right the first time. TCB deficiency rounds add 1–4 weeks each. Have your internal/external photos (annotated), label artwork, user manual with compliance statements, block diagram, and operational description ready before submission.

Invest in pre-compliance. The $3,000–$8,000 you spend on pre-compliance saves $5,000–$30,000 when it prevents a formal test failure. Nothing else in this process has a better return.

The cost of not certifying

Marketing an unauthorized device in the United States violates 47 USC 302a. This gets enforced:

• FCC enforcement: Warning letters, citations, and fines up to $100,000+ per violation
• Customs seizure: CBP can impound shipments lacking proof of FCC authorization at the border
• Retailer gates: Amazon, Best Buy, Target, and most major retailers require proof of FCC compliance before listing. No compliance documentation, no listing.
• Liability exposure: If your device causes interference, you're liable for remediation costs

The minimum cost of proper SDoC testing is $800–$2,000. The minimum cost of getting caught without it is orders of magnitude higher.

Next steps

Start with the question that matters most to your product:

• Not sure if you need certification? → Do You Need FCC Certification?
• Deciding between SDoC and Certification? → SDoC vs Certification
• Evaluating modules vs chip-down? → Pre-Certified Modules & Host Device Testing
• Building your budget? → FCC Certification Cost Breakdown
• Planning your schedule? → FCC Testing Timeline
• Getting your labels right? → FCC Label Requirements