FCC Certification: What It Actually Requires
“FCC certification” gets used loosely to mean any US approval for an electronic product, but it’s actually one of two distinct paths — and most consumer electronics don’t go through Certification at all. The FCC’s equipment authorization framework splits devices into two procedures: full Certification, reviewed by an FCC-recognized Telecommunications Certification Body and resulting in a public FCC ID, reserved for devices with the highest potential to cause radio interference; and Supplier’s Declaration of Conformity (SDoC), a self-responsibility route for lower-risk digital devices that still requires testing but no FCC review or FCC ID. Confusing the two — assuming every device needs an FCC ID, or assuming SDoC means no testing at all — is the most common mistake sellers make with this requirement.
This guide covers both procedures, what actually has to be tested, the FCC ID and FCC logo (which are not the same thing and don’t both apply to the same devices), and where sellers most often get it wrong — including a few points that trip up even sellers who’ve already handled CE marking or CPSC certification for the same product.
FCC certification at a glance
The fork that determines everything is whether a device intentionally transmits radio signals (Bluetooth, Wi-Fi, cellular) or only unintentionally radiates as a side effect of its digital circuitry (a switching power supply, an LED bulb, a set of computer peripherals).
The two FCC equipment authorization paths: Certification for intentional radio transmitters, SDoC for devices with only unintentional digital emissions.
The two equipment authorization procedures
Per the FCC’s own equipment authorization rules, the required procedure depends entirely on the type of equipment and the specific rule part it falls under — not on a general “electronics” category.
Certification
Reserved for RF devices with the greatest potential to cause harmful interference — intentional radio transmitters like Bluetooth, Wi-Fi, and cellular modules. Testing has to happen at an FCC-recognized accredited testing laboratory, and the results go to an FCC-recognized Telecommunications Certification Body (TCB) for review. If approved, the TCB issues a Grant of Equipment Authorization and assigns an FCC ID, which becomes publicly searchable in the FCC’s equipment database. Devices with only unintentional emissions can also choose to go through Certification voluntarily, even when SDoC would have been sufficient — some manufacturers do this because an FCC ID carries more market credibility than an SDoC filing, even though it isn’t required.
Supplier’s Declaration of Conformity (SDoC)
Covers digital devices that don’t intentionally transmit radio signals — computer peripherals, switching power supplies, LED light bulbs, microwave ovens, and similar unintentional radiators. Testing is still required, but not necessarily at an FCC-recognized lab — the lab just needs to meet specific measurement and record-keeping standards. No FCC review happens, no FCC ID is issued, and the manufacturer or importer (the “responsible party”) stands behind the result on their own authority. This is the route most ordinary consumer electronics actually go through — SDoC, not full Certification, despite “FCC certified” being the phrase people default to for both.
Verification (largely phased out)
Older FCC rules included a third procedure, Verification, for lower-risk devices with minimal or no in-house testing oversight. This route was phased out for new authorizations starting November 2017, replaced functionally by SDoC. It’s worth knowing the name exists mainly because older compliance documentation or legacy products might still reference it — a “Verification” label on an older device isn’t a mistake, just a procedure that no longer applies to new products.
How long does this actually take?
SDoC testing can move quickly if a qualifying lab has availability — since accreditation isn’t required, sellers sometimes have more lab options and shorter queues than the Certification route offers. The certification-relevant paperwork (the compliance information statement) is comparatively simple to assemble once test results exist.
Certification takes longer end to end, because it adds a TCB review step on top of lab testing — the lab has to be FCC-recognized specifically, which narrows the pool compared to SDoC, and the TCB then has to review the full application and test data before issuing a grant. Sellers launching a product with a new radio module for the first time should treat Certification lead time as a real constraint on launch timing, not something to schedule after everything else is ready — a failed or incomplete first submission can add weeks to the process.
What it costs
As with CE marking and CPSC certification, cost is driven by testing and review, not by the paperwork itself. SDoC testing tends to be the less expensive of the two routes, since it doesn’t require FCC-recognized lab accreditation or a TCB review fee. Certification costs more by design — the accredited lab requirement and the TCB’s own review fee are both specifically part of why the process is more rigorous, and a product needing retesting after a failed submission adds to that cost further. Devices that combine both transmitting and non-transmitting elements can end up paying for both a Certification process on the transmitting portion and separate emissions testing on the rest, which is worth budgeting for upfront rather than discovering partway through.
What actually has to be tested
Under both procedures, the underlying technical question is the same: does the device’s radio-frequency emissions — intentional or not — stay within the limits set by FCC rules (Part 15 covers most consumer electronics). For an intentional transmitter, this includes the transmission itself (power, frequency, modulation) plus any unintentional emissions from the same circuitry. For an unintentional radiator, it’s specifically the conducted and radiated emissions the device produces as a byproduct of its digital circuitry — power-line conducted emissions and radiated field strength are both measured against defined limits.
The specific limits and test methods depend on which rule part applies, and on the device’s classification within that part — a device sold for use in a home (Class B) is generally held to tighter emissions limits than one intended for a commercial or industrial setting (Class A), on the reasoning that consumer environments sit closer to other sensitive equipment and have less tolerance for interference. Getting the class wrong — testing a consumer product against the looser commercial limits — is its own quiet way to end up non-compliant even with genuine test data in hand.
Certification and SDoC both require real testing — the difference is who reviews the result and whether an FCC ID gets issued.
FCC ID vs. the FCC logo — not the same thing
This is a genuinely common point of confusion. The **FCC ID** is assigned only to devices that go through Certification — it’s the alphanumeric code (grantee code + product code) tied to a specific Grant of Equipment Authorization, and it must appear on the device. The **FCC logo** is a completely separate, voluntary mark that can optionally be used on SDoC-authorized devices that fully meet the requirements — it is not required, and it is not part of FCC ID labelling. A device can legitimately carry an FCC ID and never use the logo, or carry the logo (SDoC) and never have an FCC ID at all. Seeing one on a product doesn’t tell you the other is present.
This distinction matters commercially, not just technically. Buyers and retailers sometimes treat “has an FCC ID” as the marker of a legitimate, compliant product, and treat its absence as a red flag — which unfairly penalizes perfectly compliant SDoC devices that were never supposed to have one. If your product goes through SDoC, it’s worth explaining that in your own product documentation or listing copy, rather than leaving a buyer to wonder why a lookup in the FCC database comes back empty.
Common mistakes
Assuming every device needs an FCC ID
Most consumer electronics — anything without an intentional radio transmitter — go through SDoC and never receive an FCC ID at all. Sellers sometimes worry their product is non-compliant because they can’t find it in the FCC’s public database, when the real answer is that SDoC devices were never meant to appear there in the first place.
Treating SDoC as “no testing required”
SDoC removes the FCC review step, not the testing step. A device still has to be tested against the applicable emissions limits at a lab meeting FCC’s measurement standards — the manufacturer just certifies the result themselves instead of submitting it to a TCB.
Assuming CE/RED testing covers FCC requirements
The EU’s Radio Equipment Directive and the FCC’s Part 15 rules test broadly similar physical phenomena — but against different limits, different frequency allocations, and different test methods. Our complete guide to CE marking requirements covers the EU side of this; passing RED testing is a useful starting point for FCC testing, not a substitute for it.
Not updating the FCC ID after a product modification
A change to the RF circuitry, antenna, or power output after certification can require a permissive change filing or an entirely new FCC ID — the original grant covers the device exactly as tested, the same pattern that shows up under CE marking and CPSC certification alike.
Assuming a modular radio component covers the whole product
Sellers sometimes buy a pre-certified Bluetooth or Wi-Fi module and assume the finished product automatically inherits that module’s FCC ID. Modular certification can carry over under specific conditions — the module has to be integrated exactly as the module’s own certification allows, with no modifications to its RF-relevant parts — but it’s a conditional inheritance, not an automatic one. A modification to how the module is mounted, shielded, or powered can break that inheritance even if the module itself never changes.
FCC vs. EU Radio Equipment Directive
| United States — FCC | European Union — RED | |
|---|---|---|
| Who reviews | TCB for Certification; self for SDoC | Self-certification for most products; notified body for higher-risk cases |
| Public record | FCC ID database, for Certification only | No public database — technical file kept on request |
| Marking | FCC ID (Certification) or FCC logo (SDoC, voluntary) | CE mark, mandatory |
Selling into both the US and the EU?
The additional-market report extends an existing report or kit to a second market.
A quick pre-launch checklist
- Confirm whether the device intentionally transmits RF — this decides Certification vs. SDoC
- For Certification, confirm testing happens at an FCC-recognized accredited lab
- For SDoC, confirm the lab meets FCC’s measurement and record-keeping standards, even without formal accreditation
- Confirm you’re not confusing the FCC ID requirement (Certification only) with the FCC logo (SDoC, voluntary)
- Confirm any post-launch design change to RF-relevant components triggers a review of the existing authorization
- If using a pre-certified radio module, confirm your integration matches the module’s own certification conditions exactly
As with the EU and CPSC checklists elsewhere on this site, none of this is a one-time task — a product’s authorization is tied to the device exactly as tested, and stays valid only as long as the device stays exactly as authorized. Revisit it whenever the design, the supplier, or the intended market changes.
Not sure which rules apply to your product?
Run the free applicability check — closed questions, no account needed, result on screen.
Frequently asked questions
Do I need an FCC ID for a Bluetooth device?
Generally yes — Bluetooth is an intentional radio transmitter, which puts it under the Certification procedure rather than SDoC, meaning it needs testing at an FCC-recognized lab and review by a TCB before it can carry an FCC ID.
Can I look up whether a product has valid FCC authorization?
Yes, for Certification — the FCC maintains a public database searchable by FCC ID. SDoC-authorized devices won’t appear there, since no FCC ID is issued for that route; for those, the compliance information statement that ships with the product is the relevant record, not a public database entry.
Does a product with both a transmitter and non-transmitting digital circuitry need both procedures?
Often yes — where a device combines transmitting and non-transmitting functions, the transmitting portion is generally subject to Certification and must be covered by an FCC ID, while the rest of the device’s emissions may be handled under the same certification or evaluated separately, depending on how the specific rule part applies.
Is testing for SDoC cheaper than testing for Certification?
Usually, yes — SDoC testing doesn’t require an FCC-recognized accredited lab, which broadens the pool of labs that can perform it and removes the TCB review fee entirely. Certification testing and the associated TCB review add cost specifically because of the extra rigor and public accountability the process carries.
What happens if I sell a product without required FCC authorization?
Consequences range from a marketplace suspending the listing, to customs holding a shipment, to FCC enforcement action independent of either. As with CE marking and CPSC certificates, the product being technically fine doesn’t prevent enforcement if the required authorization or testing record doesn’t exist.
Does private labelling change who’s responsible for FCC compliance?
No — the same pattern that applies under CE marking and CPSC rules applies here. Putting your own brand on someone else’s manufactured product generally makes you the importer or responsible party for FCC purposes, and the authorization obligation sits with you, not automatically with the original factory, even if their testing supports your filing.
If a similar product from the same factory already has an FCC ID, does mine automatically qualify?
No — an FCC ID covers the specific device exactly as tested and described in its grant, not a general product line. A different model, a different antenna, or even a different enclosure that changes the RF environment can mean the existing FCC ID doesn’t extend to your version, regardless of how similar the underlying design looks.
Start with the free check
Confirm whether your product needs FCC Certification, SDoC, or nothing at all.