Most people ask this question after a US customer, distributor or marketplace listing check asks them for "FCC certification". The email gets forwarded internally, someone searches for the phrase, and the answers they find mix two completely different FCC routes as if they were one thing. So let us separate them first, because which route applies decides your cost, your timeline, and who is legally on the hook once the product ships.
First, a correction: there is no FCC certificate
"FCC certification" as people use the phrase actually covers two different procedures, and neither one produces a certificate.
- Certification is the FCC's formal equipment authorization procedure. A Telecommunication Certification Body (TCB) reviews the test report and issues a Grant of Equipment Authorization - an electronic grant tied to an FCC ID, publicly searchable in the FCC's database. The product carries the FCC ID on its label. There is no paper certificate to frame; when a customer asks for one, what you actually provide is the grant (a printout or link to the FCC database entry) and the test report behind it.
- Supplier's Declaration of Conformity (SDoC) is a self-declaration route. The supplier tests the product, keeps the report, and provides a compliance statement document - but files nothing with the FCC and receives no FCC ID. Since the SDoC procedure replaced the old DoC and Verification routes (effective November 2, 2017, with a one-year transition), it is the standard path for digital devices without a transmitter.
Saying "I have FCC certification" when you actually have an SDoC is not a harmless simplification. A US importer checking your paperwork will notice within a minute, because one of them has an FCC ID behind it and the other does not.
The question that decides everything: does it contain a transmitter?
Walk through your own product with these two questions.
1. Does it intentionally transmit or receive radio? Bluetooth, Wi-Fi, Zigbee, LoRa, cellular, RFID, a 2.4 GHz proprietary link, a wireless microphone - anything that deliberately radiates RF energy is an intentional radiator. Intentional radiators are authorized through the Certification procedure: testing at an FCC-recognized accredited laboratory, an application filed through a TCB, and an FCC ID on the label.
2. If there is no radio, does it contain digital circuitry? Devices without a transmitter but with digital electronics are unintentional radiators under FCC Part 15, Subpart B, and they go through the SDoC route. The FCC's own examples of this category include computer peripherals, switching power supplies, LED light bulbs, radio receivers, TV interface devices, ISM equipment and microwave ovens. No FCC ID, no filing, and the FCC logo is optional; what is required is a compliance statement in the product's accompanying information, naming a responsible party located in the United States.
What about products with neither a radio nor digital circuitry - a passive cable assembly, a purely mechanical switch? Those generally fall outside Part 15 Subpart B entirely. Be careful with this reasoning, though: Subpart B does contain a short list of exempted devices, but it is narrow and specific. Being wired, battery-powered, or inexpensive does not put a product on that list, and we regularly see exporters assume an exemption that does not exist.
| Certification (FCC ID) | SDoC (no FCC ID) | |
|---|---|---|
| Product type | Contains a radio transmitter | No transmitter, digital circuitry only |
| Typical rules | Part 15C (2.4 GHz etc.), Part 15E (U-NII), licensed service rules | Part 15 Subpart B |
| Who approves | TCB files with FCC | The supplier itself |
| Lab requirement | FCC-recognized accredited laboratory | Accreditation not required by FCC rules; test facility description retained |
| Label | FCC ID (or "Contains FCC ID" for module builds) | Compliance statement in accompanying information; FCC logo optional |
| Output document | Grant of Equipment Authorization + test report | Compliance statement + test report |
The case that catches people out: a radio product needs both
A Wi-Fi product is not only "certified". Its radio is authorized by certification, but the digital circuitry around it still has to meet Part 15 Subpart B. In practice this is handled in the same test report set and the same TCB application, so you will not file twice - but it does mean the question "do I need FCC certification" for a typical IoT product has a two-part answer: the radio gets an FCC ID, and the host electronics sit behind it under Subpart B. The grant and the label artwork should reflect both.
An existing FCC ID does not always transfer to your product
Buying a pre-certified radio module looks like a shortcut around the whole question, and sometimes it genuinely is. But a modular approval is granted for the module as tested - with a specific antenna configuration and specific conditions written into the grant.
This is one of the most common situations we see: a buyer selects a module largely on price, the host product uses a different antenna - a PCB trace antenna on the host board, or a different external antenna than the one in the module's grant - and only at quotation or sample review does it turn out that the module's FCC ID does not cover that integration. Depending on the change, the host may need a Class II permissive change filed through a TCB, or a new authorization. And even when the module's grant does carry over, the host product still needs its own Subpart B evaluation, and the label reads "Contains FCC ID: XXX-XXXXXX" rather than the module maker's ID standing alone.
Where FCC projects actually go wrong
The test itself is rarely the surprise. These are the situations that turn a straightforward FCC project into a re-filing:
A second radio mode that was never declared. A device ships with Wi-Fi and Bluetooth both enabled in firmware, but only one mode was declared and tested. Every radio mode that the product can operate in must be covered by the authorization - and adding a mode later is not a paperwork correction, it is a Class III permissive change, which effectively means a new equipment authorization. The cheaper moment to catch this is at scoping, when listing the radio chipsets and firmware modes takes ten minutes.
An antenna changed after the grant. Same chipset, same enclosure, but the antenna type or gain changed between approval and production. Changes to the antenna configuration affect the RF characteristics and are handled as a Class II permissive change - a filing with test data through a TCB. If the production line simply swaps the antenna and ships, the FCC ID on the label no longer describes the product it is attached to.
Nobody in the chain can act as the responsible party. The SDoC compliance statement must name a responsible party located in the United States - a US-registered entity such as the importer, a US subsidiary or the US distributor. An overseas brand or factory cannot fill that line. Separately, since February 6, 2023, an applicant for FCC equipment authorization must designate an agent for service of process located in the US (47 CFR 2.911(d)(7)), with a signed certification filed along with the application. Exporters tend to discover both requirements latest, exactly when documents are being assembled - which is the worst time, because the TCB cannot accept the application without the designation in place.
Assuming an old FCC ID covers a new model. An FCC ID belongs to a specific grantee for a specific authorized product. A new model number, a rebrand, or a new variant is not automatically covered by an existing grant; whether it is a permissive change or a fresh authorization depends on what changed - which is a scope question, not a guess.
A ten-minute self-check before you ask for a quote
- List every radio in the product and every mode the firmware can operate in - not just the ones you plan to sell first.
- If you use a certified module, look up its FCC ID in the FCC's public database and read the grant: which antenna configurations, which conditions, whose grantee code.
- Count the digital circuitry as its own item - it needs Subpart B coverage even when a radio is present.
- Decide who signs as the SDoC responsible party, and who acts as the US agent for service of process if certification is the route.
- Then ask for the test scope. With the four points above, a scope answer takes minutes instead of another round of email.
That last step is where the two FCC routes stop being abstract: the scope we quote for a Subpart B-only device and the scope for a multi-mode radio product differ in test items, samples and lead time, and both are visible line by line in our testing and certification services - including the wireless product categories we handle most often on our products pages. If you are still working out what applies beyond radio, the wider picture sits in what certifications a product needs to sell in the USA.
If you are not sure which FCC route your product takes, send over the product specification, the radio chipset and antenna details, the module's FCC ID if you are building on one, and where you plan to sell it.
We will tell you which route applies, whether the module's grant covers your integration, and what the test report set will include - before you commit to a scope.