FCC equipment authorisation has two routes. Unintentional radiators — wired keyboard and mouse, power adapters, wired small appliances — take the SDoC route: EMC testing plus an enterprise self-declaration, with no body review. Intentional radiators — Bluetooth, Wi-Fi, cellular — take the FCC ID route, submitted to a TCB for review and certification.
Pick the wrong route and everything downstream fails: a device with a wireless module cannot sneak by on SDoC; it must take FCC ID, or customs blocks it, platforms delist it, goods sit in port costing daily, and order defaults pile on.
Register a free FRN company number in the CORES system; the first Grantee Code application fee is paid with a normal review of 3 to 7 business days. In parallel prepare the English manual, schematic, internal and external photos, and RF parameters — assemble the documents once to avoid detours.
Body-worn devices (headsets, phones) also need radio-frequency exposure (SAR) material. Incomplete documents get bounced by the TCB directly; checking the list up front saves trouble — do not wait until submission to fill gaps, when one revision adds another week.
FCC 22-84's covered-list and prohibited-entities-list rules affect lab and TCB authorisation and are implemented in phases. When selecting a body, first verify the current FCC covered list and TCB recognition list and the current scope of authorisation; do not apply an old list, or the finished report will not be accepted.
Lab testing: the core measures RF performance — output power, frequency tolerance, bandwidth, modulation characteristics, sensitivity, blocking, intermodulation and spurious emission. EMC measures conducted and radiated emission and immunity; power-adapter conducted emission is the easiest to exceed, and remediation often stalls there. Body-worn devices add SAR at the 1.6 W/kg limit, with tighter accuracy required from 2025. Single-mode Bluetooth finishes in two weeks; Wi-Fi 6E's key mechanisms are AFC and low-power indoor limits, 5 GHz Wi-Fi involves DFS, and 5G terminals stacking SAR/HAC approach four weeks; multi-antenna multi-band products are scanned item by item, and time rises with the RF combinations — no one-size estimate.
Submit the test report with FCC Form 731 and Form 159 to an authorised TCB for online review: normally 4 to 8 weeks, expedited to 2 to 4. The review only asks about material explanation, photo angles and label size, not retesting.
Pass and the FCC ID is issued in the format "Grantee Code + product code", entered into the public database. Only 6 GHz standard-power devices need a PAG pre-approval (dependent on AFC coordination); indoor low-power (LPI) devices are exempt from PAG and the TCB can issue directly — this segment is outside the normal cycle.
The FCC ID must be permanently marked on the product body, not only on the packaging; too small and an electronic label is allowed. The manual embeds the standard FCC warning text. Minimum font height is 1.6 mm; in practice 3 mm is safer to avoid non-compliant print shrinkage.
The FCC ID requires a US agent per Section 2.911(d)(7) (mandatory since November 2022), with the information submitted with the application and not placed in the product manual. The SDoC responsible party must be in the US (Section 2.1077) with name and address written into the manual or compliance information — both routes have a US-side requirement, just carried differently; do not confuse them.
For FCC, the route and lab compliance are confirmed with the client first, avoiding the costly discovery at sampling that the body is limited and the whole report is wasted.
For those doing CE-RED and FCC together, BlueAsia's one-stop testing and certification submits the RF and EMC samples once and compiles the documents together, queuing only once and sharing data across both countries.
SDoC itself has no review; with documents ready it finishes in just over a week. FCC ID, including testing and TCB, normally takes two to three months, longer for complex cases — do not estimate optimistically.
Lab queue and TCB review are two independent waits; do not count only testing time, because the review segment is often overlooked and takes a large share of the waiting.
A major hardware change requires re-certification; many factories do not assess before revision and discover the old certificate is invalid while goods are in transit — the whole batch becomes non-compliant.
After the report is done, check the public database for correctness; one wrong number or model and later queries and customs will not match.
The SDoC responsible-party name and address in the manual is a hard requirement; missing it early means revising the manual another round. The FCC ID US-agent information submits with the application — do not leave it until just before submission.
The certificate has no annual review but changes require re-certification; any hardware move may restart it, so assess the impact before iterating.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
相关新闻
