FCC ID or SDoC? How to Choose, in One Read

Start with the answer, because one sentence settles it: whether the product contains an RF transmitter decides whether you need FCC ID or SDoC.

If it does — Bluetooth, WiFi, Zigbee, a cellular module, even one used only for pairing, at short range and low power — you need FCC ID: the lab tests RF plus EMC, a TCB reviews the file and issues the grant, and you end up with an ID you can look up in the FCC database.

If it does not — purely wired electronic equipment with no RF at all — you need SDoC: EMC testing only. The lab issues a report, the company signs its own declaration of conformity, and there is no ID number.

Getting the classification wrong costs real money. File an ID product as SDoC and you burn the test fee plus several weeks, no ID is issued, the Amazon or Temu review stops right there, and the whole thing has to be done again. Push a purely wired product through ID and the cost and timeline climb, while what comes back is an ID the platform never asks for. We run into both kinds of rework dozens of times a year.

Timelines assume complete documentation and a test that passes first time; they exclude rework and document back-and-forth. The lab/TCB assessment governs in each case.

The real difference: FCC ID means someone else reviews you, SDoC means you sign it yourself

Plenty of people treat these two as an "advanced version" and a "simplified version" of the same thing. The difference is not difficulty — it is who is responsible for the compliance conclusion.

FCC ID goes through the Certification route. The lab tests RF output power, occupied bandwidth, spurious emissions and frequency stability under FCC Part 15C (Bluetooth/WiFi 2.4G), Part 15E (5G WiFi) and Part 22/24/27 (cellular). 5G WiFi also needs DFS radar-avoidance testing, and portable products used close to the body need a SAR assessment. The report and supporting documents then go to an FCC-recognised TCB, which reviews them and issues the Grant, and the ID is entered in the public FCC database. The TCB review catches part of the responsibility, and you also have to designate a US local agent (US Agent).

SDoC is a supplier's declaration of conformity. The lab is responsible for the test data only; the compliance conclusion is signed by the company. There is no ID and no entry in the FCC database, so when a regulator, a platform or a customer asks for the file, you have to produce it on the spot. SDoC looks like the easy option, but what it really tests is a company's document management.

Decision tree: which products need ID, which need SDoC

Before you open with "what will this cost me" to a lab, walk the four steps below yourself — they usually settle the classification.

① Is there an RF transmitter at all? If the product actively emits RF energy, it is a transmitting device and needs FCC ID. This test does not look at output power, at the intended use, or at whether wireless is the selling point.

② Does the transmission come from an already-certified module? With a wireless module that already holds an FCC ID, host certification can be simplified considerably — only host EMC and the antenna influence need assessing — but that is a simplification, not an exemption, and the host usually still needs its own FCC ID.

③ Frequency bands and how it is used. 2.4G Bluetooth/WiFi falls under Part 15C, 5G WiFi under Part 15E and involves DFS, and cellular products under Part 22/24/27. Products held to the ear, worn on the wrist or used close to the body need a SAR assessment, and may be exempt only when output power is below the exemption threshold (typically <3mW is exempt).

④ Confirm the boundary. For receive-only, wired-only or passive products the boundary is not always obvious — ask the lab for a written conclusion rather than deciding on your own judgement.

For product-specific mappings see the Bluetooth earphone, camera and security and smart watch pages; clause-level detail sits in our USA FCC knowledge base.

SDoC does not mean "no testing": report, declaration and records are all required

One misunderstanding we come across fairly often: the assumption that SDoC is a sheet of paper you write and stamp yourself. It is not. What SDoC removes is the step of applying to a TCB for an ID — not the testing.

It requires at least two things:

• A complete EMC test report — tested to the FCC Part 15B EMC requirements for non-wireless electronic devices, with every report element and test item present, plus an English version for platform submission.
• A declaration of conformity (DoC) — model, manufacturer, applicable standards, lab information and signatory must all match the physical product.

Both documents have to be kept on file long term. Amazon's review team wants the complete report, not a summary page, and the product photos, model name and applicant have to match the documents too. An incomplete file means a rejection round that costs one or two weeks, and in peak season that effectively means missing a slot. For more on the platform side see the full FCC process for Amazon US.

Four common misjudgements: modules, Bluetooth, wireless charging, receive-only

Misjudgement one: a certified module means the host needs no attention

A module holding an FCC ID only says that the module level has passed. Host EMC, antenna layout and enclosure shielding all change the RF behaviour, so the host still needs its own assessment and its own FCC ID. Submit the module ID alone, with no host ID, and some customers and platforms will not accept it.

Misjudgement two: Bluetooth is only for pairing, the power is low, so it counts as SDoC

Bluetooth is a transmitter, so it needs FCC ID — whether it carries data or only pairs makes no difference. Products that look unremarkable, such as BLE beacons and Bluetooth remotes, are FCC ID too. The only point open to discussion is whether SAR is needed, and that is an extra item inside the ID route, not a reason to switch routes.

Misjudgement three: wireless charging does not communicate, so treat it as a wired device

Wireless charging transfers energy by RF, so it cannot be filed as SDoC on the grounds of being "wired only, no RF". Such products are assessed as transmitting devices, and the applicable clauses are confirmed by the lab according to operating frequency and output — do not put one on the shelf by filling in an SDoC template yourself.

Misjudgement four: receive-only, no transmission, so nothing needs doing

Receive-only devices usually do not need an FCC ID, but they are still electronic devices, so EMC compliance still applies (the SDoC route). Check as well whether a Bluetooth or WiFi module was "added along the way" — if it was, you are back on the ID route.

What Amazon and Temu actually ask for

Platform review is not asking "do you have a certificate" — it is asking "do the documents you submit line up with this product". On Amazon US the logic runs roughly like this:

Frequent rejections come down to a few causes: the company name on the FCC ID certificate does not match the seller entity, the report provided is incomplete, the product photos do not match the model in the certification file, a non-wireless product is missing its SDoC declaration, or the battery documents are absent. None of these is a technical problem — they are document-alignment problems — but any one of them can stop a listing.

For the full set of platform requirements, read this alongside our Temu listing certification guide; if you want to check item by item, the certification lookup tool pulls up a list by product category.

Process, timeline and cost: where the money and time go

How each route runs

On timeline, FCC ID usually takes 2-4 weeks and SDoC 1-2 weeks, provided the documentation is complete and the test passes first time. An FCC ID is valid long term, needs no update while the standards are unchanged, and involves no factory inspection — unlike UL/ETL, which requires quarterly factory checks.

What the cost is made up of

A quotation is rarely a single number; it is several blocks added together. Understanding the structure is more useful than memorising a total.

For the same product, the total FCC ID cost is typically several times that of SDoC (broadly in the 2-5x range, including TCB and RF items); products with 5G WiFi, DFS and SAR go higher still. Actual amounts vary widely with product complexity and certification scope — the formal lab/TCB assessment governs. For the cost structure see the USA FCC/UL certification service page, or let us map the route for your product directly.

Common pitfalls, and a pre-listing checklist

Pitfall one: file as SDoC first, add ID after the platform rejects it

The thinking is "do the cheap one first and get by". The result is an EMC report with no ID, a platform asking for an FCC ID, the whole process run again, and the test fee paid twice. Getting the classification right at the start saves everything downstream.

Pitfall two: relying on a supplier's FCC ID

The applicant on the certificate is the manufacturer and may differ from the seller, but the supply-chain relationship has to be explainable. If you list with someone else's ID, you will have no answer when the platform asks about the entity relationship, and the risk lands on the store.

Pitfall three: submitting only the report summary page

Platform review requires the complete report. A summary page looks tidy, and it comes straight back.

Pitfall four: derivative models not covered

The main model is certified, but the packaging shows five or six models, none of them mentioned in the report, and the model in the photos does not match either. Whether a derivative needs extra testing depends on whether the RF section differs, and that requires the lab's assessment.

Pitfall five: antenna changed, module swapped, band added, old ID still used

The RF characteristics of the host have changed, so the original report no longer covers this product. Whether retesting is needed, and which items, is for the lab to judge — do not gamble on review with old documents.

Pitfall six: missing documents that are not FCC but the platform wants

UL/ETL safety certification, Bluetooth SIG trademark authorisation, UN38.3 plus MSDS and California Prop 65 are not FCC matters, but all of them come up in Amazon US review. Preparing them once, against the product list, beats patching round after round.

Pre-listing checklist — work through it line by line and you will rarely take the wrong route:

On the FCC line, the cost of choosing the wrong route is not "a little more money" — it is money spent, time gone, and stock still sitting in the warehouse. Classify first, quote second; do not reverse the order. Related reading: FCC knowledge base, all articles.