FCC Equipment Authorization: Certification, SDoC, and How to Choose

TL;DR -- Before any RF device can be legally sold in the US, it needs FCC equipment authorization under 47 CFR Part 2, Subpart J. There are two paths: Certification (third-party review, FCC ID issued) and SDoC (self-declaration, no FCC ID). Which path applies depends on whether your device is an intentional or unintentional radiator. Misclassify your device and you will waste months and tens of thousands of dollars.

What equipment authorization actually is

Equipment authorization is how the FCC keeps electronic devices from interfering with licensed radio services. The rules live in 47 CFR Part 2, Subpart J (Sections 2.901 through 2.1093), which spell out who can market RF devices, what testing is required, and which procedural path applies.

The system is not optional. Under 47 USC 302a, it is illegal to market, import, or operate a device that does not comply with the applicable FCC rules. Customs and Border Protection can seize non-compliant shipments at the border. Amazon, Walmart, and other major retailers require proof of FCC authorization before listing a product.

There are two authorization paths:

• Certification -- Testing at an accredited lab, review by a Telecommunication Certification Body (TCB), issuance of an FCC ID that goes into the public EAS database. Required for intentional radiators and higher-risk devices.
• Supplier's Declaration of Conformity (SDoC) -- Testing at an accredited lab, self-declaration by the manufacturer or importer. No third-party review, no FCC ID. Used for unintentional radiators and lower-risk devices.

Before 2017, there were actually three paths: Verification, Declaration of Conformity, and Certification. The FCC consolidated Verification and DoC into SDoC, simplifying the framework. If you encounter references to Verification or DoC in older documentation, they both map to what is now called SDoC.

Intentional vs unintentional: the split that matters

One question determines your authorization path: does your device deliberately emit RF energy?

Intentional radiator (47 CFR 15.3(o)): A device designed to generate and emit RF energy by radiation or induction. WiFi radios, Bluetooth chips, Zigbee modules, RF remotes, NFC readers, wireless chargers -- all intentional radiators.

Unintentional radiator (47 CFR 15.3(z)): A device that generates RF energy internally (all digital circuits do) but is not designed to emit it. The radiation is an unwanted side effect of clock signals, switching regulators, and high-speed data buses. Laptops, monitors, USB hubs, LED drivers, power supplies.

flowchart TD
    A["Does your device contain\nelectronic circuitry?"] -->|No| B["No FCC authorization needed"]
    A -->|Yes| C{"Does it deliberately\ntransmit RF energy?"}
    C -->|No| D["Unintentional Radiator\n→ SDoC path"]
    C -->|Yes| E{"Using a pre-certified\nRF module?"}
    E -->|Yes| F["Module's FCC ID covers the radio\nHost device → SDoC for Part 15B"]
    E -->|No| G["Custom RF design\n→ Certification path"]
    D --> H["Cost: $1,500 – $5,000\nTimeline: 2 – 4 weeks"]
    F --> I["Cost: $2,500 – $5,500\nTimeline: 3 – 6 weeks"]
    G --> J["Cost: $8,000 – $50,000+\nTimeline: 6 – 16 weeks"]
    style D fill:#1e3a5f,color:#fff
    style F fill:#1e3a5f,color:#fff
    style G fill:#1e3a5f,color:#fff

Most modern products are composite devices. A WiFi router has an intentional radiator (the radio) and an unintentional radiator (the processor, memory, and switching power supply). Each portion is tested under its own subpart. The intentional radiator needs Certification; the unintentional portions use SDoC.

Certification: the full path

Certification is the path for intentional radiators and higher-risk devices. The end result is a public record (the FCC grant) and a unique identifier (FCC ID) that stays with the product for its entire market life.

Who reviews your application

The FCC does not review most certification applications itself. Since 1999, that work has been delegated to Telecommunication Certification Bodies (TCBs) -- private, accredited organizations that review test reports and issue FCC grants on the Commission's behalf.

The accreditation chain works like this:

flowchart TD
    A["NIST (via NVCASE program)"] -->|Recognizes| B["Accreditation Bodies\n(A2LA, NVLAP, ANAB, IAS, SCC)"]
    B -->|Accredit against\nISO/IEC 17065| C["TCBs\n(UL, Intertek, Bureau Veritas, TÜV, etc.)"]
    B -->|Accredit against\nISO/IEC 17025| D["Test Labs"]
    D -->|Test report| C
    C -->|Issues grant| E["FCC EAS Database\n(public record)"]
    style E fill:#1e3a5f,color:#fff

There are roughly 42 active TCBs globally, organized into eight scope categories (A1 through B4). Not every TCB can review every device type. A TCB without an A4/B4 designation cannot grant a 6 GHz WiFi device, for instance, even if it handles Bluetooth certifications all day long. When selecting a TCB, verify that its designation covers your device's scope category.

Key differences between test labs and TCBs:

Some organizations operate both a test lab and a TCB under one corporate roof (UL, Intertek, Bureau Veritas, TÜV SÜD). This is convenient -- one contract, one project manager -- but the lab and TCB functions must be functionally independent under their respective accreditations.

The FCC ID

Every certified device receives a unique FCC ID composed of two parts:

FCC ID: [GRANTEE CODE]-[PRODUCT CODE]
         3–5 chars       1–14 chars
         Assigned by FCC  Chosen by applicant

The grantee code is a permanent identifier tied to your company. Codes starting with "2A" are post-2013 assignments (most current international filers). Legacy codes from pre-2000s US companies use single letters. A company gets one grantee code; it applies across all products.

The product code is chosen by the applicant and must be unique within that grantee's portfolio. Teams typically encode model numbers or internal SKUs.

The FCC ID becomes a public record in the EAS database. It must appear on the product (physical label or e-labeling for devices with screens). Our FCC label requirements guide covers placement, minimum font size, and when electronic labeling is permitted.

The FCC ID is also a competitive intelligence tool. When a company files for a new FCC ID, the filing often appears in the database months before the product launch. Tech journalists and industry analysts routinely monitor FCC filings to get early reads on unreleased products from Apple, Google, Samsung, and Amazon.

SDoC: the self-declaration path

Supplier's Declaration of Conformity is the authorization path for unintentional radiators and lower-risk devices. Under SDoC, the manufacturer or importer declares that the product complies with FCC technical standards after testing at an accredited lab.

There is no third-party review, no FCC ID, and no public filing. The emission limits are identical to Certification -- the difference is purely procedural.

What SDoC requires:

1. Testing at a lab with ISO/IEC 17025 accreditation
2. A formal declaration of conformity (47 CFR 2.1071 through 2.1077)
3. Retention of all test reports and documentation
4. A compliance statement on the product or in the user manual

What SDoC does not give you:

• No FCC ID
• No TCB review to catch errors before you ship
• No public database record

The lack of a public record cuts both ways. Less overhead, yes, but also no safety net. If your test report has a flaw or your product drifts out of spec in production, nobody catches it until the FCC investigates a complaint or CBP holds a shipment at the port. For a deeper comparison, see our SDoC vs Certification guide.

The filing process step by step

For Certification

Step 1: Register with the FCC (1-2 days). Create an FCC Registration Number (FRN) through the CORES system at fcc.gov. Free.

Step 2: Obtain a grantee code (1-2 days). Apply through the FCC Equipment Authorization System. The grantee code becomes the first part of your FCC ID. Fee: approximately $40 (one-time, adjusted periodically for CPI).

Step 3: Select a test lab (1-2 weeks). Choose an FCC-recognized lab with ISO/IEC 17025 accreditation and experience with your device type. Lab queue times vary by season -- post-CES (January through March) and pre-holiday (July through September) are peak periods.

Step 4: Pre-compliance testing (optional, 1-3 weeks). Informal testing to identify problems before committing to formal lab time. About half of consumer electronics fail formal EMC testing on the first pass, so this step has high ROI. Budget $500 to $2,000 per day. Our EMC pre-compliance testing guide covers what you can do in-house.

Step 5: Formal compliance testing (3 days to 3 weeks). The accredited lab performs all required measurements per your applicable rule parts: radiated emissions, conducted emissions, spurious emissions, band edge compliance, occupied bandwidth, transmitter power, and RF exposure evaluation (SAR or MPE). You will need 2-3 production-representative test samples.

Step 6: Test report generation (3-7 days). The lab produces formal reports documenting all measurements, test configurations, and pass/fail results per FCC formatting requirements.

Step 7: TCB submission (3-10 business days). Submit to the TCB: test reports, internal and external product photos, label artwork, user manual, block diagram, operational description, and schematics if required. The TCB reviews for technical compliance and administrative completeness. Expect deficiency letters if anything is missing or unclear -- rounds of back-and-forth are common for complex devices.

Step 8: Grant issued. The TCB uploads the grant to the FCC EAS database. Your FCC ID is live and searchable. You can legally market and sell the product in the US.

For SDoC

The process is shorter: select a lab, test, generate reports, prepare your declaration of conformity, and retain all records. No grantee code, no TCB submission, no FCC database entry.

Fees and costs

The FCC itself charges very little. Most of the money goes to lab testing and TCB review.

Government fees

Total cost by device type

These ranges cover testing, TCB review, report generation, and documentation. They do not include the hidden costs that catch teams off guard: prototype shipping ($50-$500 per round), test fixture fabrication ($200-$2,000), board respins if testing fails ($1,000-$15,000), and expedite premiums (50-100% surcharge for rush service). Our FCC certification cost breakdown covers these in detail.

TCB review fees specifically

Application types

Not every filing is for a brand-new product. The FCC system recognizes several application types:

Permissive changes are how you modify a certified product without starting from scratch. Firmware updates, minor hardware revisions, and component substitutions may qualify. Our permissive changes guide covers what qualifies as Class I vs Class II and when full recertification is unavoidable.

What the TCB actually reviews

A TCB does not re-run any tests. It reviews the documentation package for:

1. Completeness -- Are all test reports, block diagrams, photos (internal and external), user manuals, operational descriptions, antenna specifications, and RF exposure evaluations present?
2. Rule applicability -- Is the device correctly classified? Correct Part 15 subpart? Correct rule sections?
3. Compliance margins -- Do measured values meet applicable limits with appropriate measurement uncertainty?
4. Label and manual statements -- Do required warnings, FCC ID placement, and user notices appear correctly?
5. KDB compliance -- For devices with FCC pre-approval guidance, does the submission follow specified procedures?

If anything is missing or non-conforming, the TCB issues a deficiency letter. Expect at least one round of back-and-forth on a complex submission. Incomplete applications are the most common cause of timeline slippage, adding 1 to 4 weeks.

Pre-Approval Guidance: when the FCC gets involved directly

For most devices, TCBs handle the entire review. But the FCC maintains a Pre-Approval Guidance (PAG) list (KDB Publication 641163) that identifies technologies where a TCB cannot issue a grant without first getting FCC sign-off.

PAG-listed device types tend to be new or policy-sensitive: novel 6 GHz operations, certain UWB configurations, new modulation schemes, and devices transitioning from experimental waivers to production. As a technology matures, the FCC typically removes it from the PAG list and lets TCBs handle it independently.

If your device falls under PAG, budget extra time. The TCB packages your application and submits it to the FCC for review, which adds weeks to the cycle. A TCB that has handled PAG submissions for similar devices will move through this faster than one doing it for the first time.

Which rule parts require which authorization

The authorization method depends on the rule part governing your device:

Modern smartphones are certified under five or six rule parts simultaneously: Part 15 Subpart B for the digital circuitry, 15.247 for 2.4 GHz WiFi and Bluetooth, 15.407 for 5/6 GHz WiFi, and Parts 22, 24, and 27 for the cellular bands. For a full map of which rule part applies to which device, see our FCC Part 15 guide.

Mistakes that actually cost money

These show up over and over in TCB rejections and failed lab tests.

Misclassifying the device. Treating an intentional radiator as an unintentional radiator sends you down the wrong path entirely. The most common version: a product with an embedded radio gets submitted as SDoC-only because the engineering team did not realize the radio module lacked modular approval. Fixing this after the fact costs months.

Submitting incomplete applications. Missing internal photos, vague operational descriptions, and user manuals without required compliance statements are the top reasons TCBs issue deficiency letters. Every round of back-and-forth adds a week or more.

Skipping pre-compliance testing. Roughly half of consumer electronics fail formal EMC testing on the first attempt. A first-pass failure means diagnosing the issue, potentially redesigning the PCB, and rebooking the lab. That adds $5,000 to $30,000 and 4 to 12 weeks. Pre-compliance testing ($500-$2,000 per day) drops the failure rate below 10%.

Using a bare chip instead of a pre-certified module. Soldering an ESP32-S3 chip onto your board is not the same as using the ESP32-S3-WROOM module. The chip alone does not have modular approval. Without the module's shielding, power regulation, and matched antenna, you need full intentional radiator Certification. This mistake typically adds $5,000 to $15,000 and several weeks.

Modifying the antenna on a pre-certified module. The module's FCC grant specifies antenna requirements. Changing the antenna type, cable length, or ground plane geometry can invalidate the grant and push you back to full Certification. Check KDB 996369 D04 for host integration requirements.

Exceeding granted power levels via firmware. Your FCC grant specifies maximum transmitter power for each modulation mode. A firmware update that increases TX power even by a fraction of a dB is a compliance violation. At minimum this triggers a permissive change filing; at worst it requires full recertification.

What to run in parallel

Not everything in the certification process is sequential. Planning what runs in parallel can shave weeks off the schedule:

Can run in parallel:

• EMC testing and SAR testing (different equipment, often different labs)
• FCC and ISED (Canada) filings -- the same test data is accepted under the Mutual Recognition Agreement
• FCC and CE/RED filings -- significant test overlap if the lab handles both
• Documentation preparation (photos, manual, label artwork) and lab testing
• Safety testing (UL/IEC) and EMC testing -- different labs, fully independent

Must run sequentially:

• Testing, then test report, then TCB submission, then grant
• Hardware redesign (if testing fails), then retest

Related guides

• SDoC vs Certification -- detailed comparison of the two authorization paths
• FCC certification cost -- full cost breakdown by device type, including hidden costs
• FCC Part 15 guide -- the rule part that governs most consumer electronics
• FCC permissive changes -- how to modify a certified product without full recertification
• FCC label requirements -- what goes on the device and in the manual
• Pre-certified modules -- how modular certification lets you skip intentional radiator testing
• FCC testing timeline -- phase-by-phase timeline from pre-compliance through grant

Where to start

Not sure which path applies? Ask one question: does any part of your device deliberately transmit RF? If yes, that part needs Certification (unless a pre-certified module already covers it). If no, SDoC.

To map your specific product to the right rule parts and authorization path, use our requirements tool or start with the FCC certification hub.