FCC equipment authorization: SDoC vs certification, explained

Marc HaddadForward Deployed Regulatory Engineer
FCC equipment authorization is what the Federal Communications Commission (FCC) requires before almost any product with a radio, a processor or a switching power supply is marketed or imported in the US. Transmitters need certification through a Telecommunication Certification Body, while most digital devices without a radio can use a Supplier’s Declaration of Conformity instead.
Key points
- Radio transmitters need certification: a Telecommunication Certification Body (TCB) recognized by the FCC reviews your test report and issues a grant tied to an FCC ID.
- Most digital devices without a radio can use a Supplier’s Declaration of Conformity (SDoC), where you declare compliance yourself, against the same limits, through a US-based party.
- The rules for the device type set the route, and your one choice is certification in place of SDoC.
- Work it per product, then per circuit, because one smart device can need a certified transmitter and an SDoC for the electronics around it.
What is FCC equipment authorization?
FCC equipment authorization is the set of procedures that clear a radio frequency (RF) device for the US market, and nobody may market an RF device without a valid one.[1] Marketing includes selling, leasing, offering, advertising, and importing or shipping for those purposes.[1]
Part 15 of the FCC’s rules sorts devices into three kinds:[2]
- Intentional radiators: devices that emit RF on purpose, such as Wi-Fi, Bluetooth, cellular and remote controls.
- Unintentional radiators: devices that generate RF inside but aren’t meant to radiate it, like a laptop’s clock or a charger’s switching circuit. Most are digital devices, meaning anything using digital techniques with timing signals above 9,000 pulses per second.[2]
- Incidental radiators: devices such as a DC (direct current) motor or a mechanical light switch, which need no authorization but must not cause harmful interference.
FCC authorization is one piece of US product compliance. The FCC covers RF emissions and, for transmitters, RF exposure,[1] while electrical safety, consumer product certificates and retailer requirements, such as UL certification where retailers ask for it, sit with other bodies.
Do I need FCC approval for my product?
Almost certainly, if it has a radio, a processor or a switching power supply and will be marketed or imported in the US, unless an exemption applies.
- Electrical and electronic products, radio included: Radio transmitters need certification, and most other electronics are digital devices that may use SDoC. Industrial, scientific and medical (ISM) equipment such as microwave ovens is tested under Part 18 instead of Part 15.
- Children’s products and toys: The same rules apply, so a radio-controlled car’s transmitter needs certification.
- Machinery, appliances and vehicles: Digital devices used exclusively in an industrial plant’s control or power systems, in appliances such as dishwashers, or in vehicles are exempt from the technical standards.[2]
- Purely mechanical products: These sit outside the regime.
The exemptions cover digital devices only, not radios, and equipment is exempt only if every device in it qualifies.[2] A machine controller with a cellular modem is still a certification case for the modem, and in the EU the same kind of product falls under the Radio Equipment Directive.
What is the difference between FCC SDoC and certification?
Certification means a TCB reviews your test results and issues a grant before you sell. Under an SDoC, you test to the same limits and declare compliance yourself, though the FCC can request samples or data.[1]
Intentional radiators under Part 15 must be certified,[2] apart from narrow exceptions such as carrier current systems, which use SDoC.[2] For unintentional radiators, the rules allow SDoC or certification for nearly everything, including personal computers and peripherals, external switching power supplies, and Class A and Class B digital devices.[2]
Scanning receivers, radar detectors and Access Broadband over Power Line (Access BPL) must be certified.[2] You may always choose certification instead of SDoC, but never the other way.[1]
The table shows how the two routes differ in practice.
| SDoC | Certification | |
|---|---|---|
| Typical products | Digital devices without a radio: computers, peripherals, power supplies, most receivers | Anything that transmits: Wi-Fi, Bluetooth, cellular, RFID readers, remotes |
| Who reviews | Nobody before sale; the FCC can request samples or data (§ 2.945) | A TCB reviews the application and issues the grant (§§ 2.907, 2.911) |
| Test lab | Any capable site, but not one owned or controlled by a prohibited entity (§ 2.906(a)) | An accredited lab recognized by the FCC (§ 2.948(a)) |
| FCC ID | No; a unique identifier that must not resemble one (§ 2.1074(a)) | Yes: grantee code plus a product code of up to 14 characters (§ 2.926) |
| US presence | Responsible party must be located in the US (§ 2.909(b)) | Grantee can be anywhere but must name a US agent for service of process (§ 2.911(d)(7)) |
| Records | Test records, compliance statement and a signed Covered List certification (§ 2.938(b)); two-year period (§ 2.938(f)) | Design, production testing and results, until one year after marketing permanently stops (§ 2.938(a), (f)) |
What is the FCC certification process?
You test, then file through a TCB or make your declaration, then label and keep records.
- Test: Test to Part 15 for most products or Part 18 for ISM equipment, using the same limits whichever route you take.
- Apply or declare: For certification, register a grantee code, the company identifier at the start of an FCC ID. The code costs $35,[3] and lapses unless the fee is paid within 30 days.[1] Then file through a TCB, which sets its own fees, with signed certifications that the equipment isn’t barred under the FCC’s national-security Covered List rules, and name your US agent.[1] For SDoC, your test file and compliance statement are the declaration.
- Label: Certified devices carry “FCC ID” and the identifier, permanently affixed and visible.[1] SDoC devices come with a compliance statement giving product identification, the Part 15 compliance sentence,[2] and the US responsible party’s name, address and phone or internet contact.[1] The FCC logo is voluntary.[1]
- Keep records: Keep the required records current as the product changes.[1]
Devices with a screen, or used only with one, may use an electronic label reachable within three steps of the settings menu, but the device or its packaging still needs a physical identifying label.[1] A device too small for 4-point type and without a display puts the information in the manual and on the packaging or a removable label.[2]
Who is the US responsible party for an FCC SDoC?
The responsible party is the company that makes the declaration, and it must be located in the US, so an overseas maker can’t take the role.[1] If the maker ships direct, the importer becomes the responsible party,[1] unless a retailer agrees to take it on.[1]
Settle this before the first shipment, because that name goes on the compliance statement. For certification, the grantee can be anywhere but must name a US agent for service of process, meaning someone who can receive legal papers on its behalf.[1]
What happens if you change an authorized product?
Authorization covers identical units only, so a changed product may need a filing or a new authorization.[1]
For certified products, a change that doesn’t degrade reported performance is a Class I permissive change, made under the existing grant with no filing. A change that degrades it but stays within limits is Class II: you file it, and it must be acknowledged as acceptable before you market the changed unit. Changes to frequency-determining circuits, the modulator or power ratings need a new application, and so does a new FCC ID.[1]
Under an SDoC, anyone who modifies the product without the responsible party’s authority becomes the responsible party.[1]
How is FCC equipment authorization enforced?
Enforcement runs through import conditions, fines and limits on grants. Imports must meet one of the conditions the rules list, normally a valid authorization, and the ultimate consignee must document which one applies.[1]
Fines reach $25,132 per violation or per day, capped at $188,491 for one continuing act.[3] For Covered List equipment, the FCC can also limit an existing grant so that import and marketing stop.[1]
For devices subject to certification, online marketplaces must show the FCC ID at the point of sale.[1] Under rules the FCC has adopted, marketplaces that handle or own the stock must do so from March 1, 2027, and those relying on seller certifications from June 1, 2027, for listings by high-volume third-party sellers.
What is the Covered List, and how is it changing?
The Covered List is the FCC’s national-security list, and equipment on it can’t be authorized.[1] Other equipment produced by a Covered List entity must still use certification.[1] Changes come through FCC rulemakings in the Federal Register, and the national-security docket (ET Docket No. 21-232) moves fastest.
Since December 26, 2025, under rules the FCC adopted, the bar has included modular transmitters and devices built around them.
Since October 13, 2026, under a further rule the FCC adopted, it has also covered devices with a chip or board from a Covered List entity, where the device would be barred if that entity had made it.[1]
On August 7, 2026, the FCC put forward a further proposal that would split the Covered List and address white-labeled equipment. It would also ask for hardware and software bills of materials and require a US-based liable party for certified equipment, but it remains a proposal and comments have closed.
Example: applying the rules to one brand’s products
As an example of applying this article, take an overseas consumer electronics brand that launched three products in the US.
Its smart plug used a Wi-Fi module with its own modular approval. The module’s grant covered the radio within its antenna and installation conditions, so the plug’s housing carries “Contains FCC ID: …”.[2] That didn’t settle the product: the plug’s microcontroller and relay driver make it a Class B digital device, which needed its own SDoC.
Its USB-C power adapter is a Class B external switching power supply, so SDoC applies. The brand had no US entity, so its importer became the responsible party, and the adapter was too small for a label, so the statement went in the manual and on the box.
Its light-emitting diode (LED) driver depended on the sales channel. Whether a driver sold to light-fixture makers to be built in counts as a subassembly depends on its design and how it is marketed,[2] so the brand had to check that for each version it sold.
Working this out for every product line, in every market it ships to, is the job Daptic’s product-level regulatory mapping takes on: it works out which requirements apply to a given product in a given market, tracks regulatory changes across jurisdictions and flags the ones that affect your products.
Frequently asked questions
Do I need FCC approval for my product?
Almost certainly, if it has a radio, a processor or a switching power supply and will be marketed or imported in the US. Incidental radiators and purely mechanical products need none.
What is the difference between FCC SDoC and certification?
Certification has a TCB review your test report and issue a grant with an FCC ID before sale. With an SDoC, you test to the same limits and declare compliance yourself through a US-based responsible party.
Does an SDoC mean we don’t have to test?
No. The technical limits are the same, and the FCC can still ask for samples or data.
If my radio module is FCC certified, is my product?
No. The module grant covers the radio, and the host product’s digital electronics need their own authorization.
Notes and sources
- eCFR, 47 CFR Part 2, Subparts I, J and K: § 2.803, § 2.902, § 2.903, § 2.906, § 2.907, § 2.909, § 2.911, § 2.925, § 2.926, § 2.935, § 2.938, § 2.948, § 2.951, § 2.960, § 2.1043, § 2.1074, § 2.1077, § 2.1204, particularly § 2.803(b); § 2.803(a); § 2.1093; § 2.945; § 2.906(c); § 2.926(c); § 2.911(d); § 2.925; § 2.1077(a); § 2.1074(b); § 2.938; § 2.935; § 2.909(b); § 2.909(b)(2); § 2.909(b)(3); § 2.911(d)(7); § 2.906(b); § 2.1043; § 2.909(b)(4); § 2.1204(a); § 2.803(c); § 2.903(a); § 2.907(c); § 2.903(b).
- eCFR, 47 CFR Part 15: § 15.3, § 15.19, § 15.101, § 15.103, § 15.201, § 15.212, particularly § 15.3; § 15.3(k); § 15.103(a); § 15.103(i); § 15.201(b); § 15.201(a); § 15.101(a); § 15.19(a)(3); § 15.19(a)(5); § 15.212(a)(1)(vi); § 15.101(e).
- eCFR: 47 CFR 1.80 and 47 CFR 1.1103, particularly § 1.1103; § 1.80(b)(10).
Additional sources:
- Federal Register: Authorization of Radiofrequency Equipment, 82 FR 50820 (November 2, 2017); 90 FR 38045 (August 7, 2025); 90 FR 53227 (November 25, 2025); 91 FR 27843 (May 15, 2026); 91 FR 27884 (May 15, 2026, proposed); 91 FR 51139 (August 7, 2026, proposed); 91 FR 57798 (September 11, 2026)
- Last reviewed: November 10, 2026.
This article reflects Marc Haddad’s independent opinions, not necessarily those of Daptic.



