SDoC covers unintentional-radiator devices and is short: with documents sorted, take them to an accredited lab for EMC, and the enterprise issues its own declaration and files it — no body reviews it. With documents complete and one pass, it closes in 7 to 15 business days. The technical file is kept for two years per FCC Section 2.938(f) (from discontinuance), and the FCC ID certification record for one year (also from discontinuance); after that it is basically left alone.
FCC ID covers most wireless products and sits between testing, TCB review and database filing, with a floating cycle. The most complex multimode products can reach 16 weeks; the sections below break each apart, because any link can delay you.
FRN registration takes 2 to 3 business days; the first Grantee Code application, once paid, normally takes 3 to 7 business days. Use that window to assemble the English manual, schematic, photos and RF parameters; body-worn devices add SAR material — have the list ready early and stay calm.
Incomplete documents are the top rejection cause; TCB back-and-forth revisions take longer than testing. Have the lab pre-check the list before submission — low-level errors like photo angle and label size are cheapest to kill early.
Lab testing is the biggest variable: a single-frequency Bluetooth headset or simple remote finishes in two weeks; a Wi-Fi 6E router, dual-mode wearable or 5G terminal stacking SAR/HAC takes about four weeks. The TCB application must already include the schematic, BOM, component list and their compliance information (the Section 2.1033 set); missing material gets bounced outright. One-pass testing keeps the cycle stable; spurious emission and frequency deviation are the two most common failures, each adding 1 to 2 weeks of rework. Solid pre-testing means a one-pass formal run that saves real money — intervene at the development stage rather than firefight after submission.
The report goes to an authorised TCB: normally 1 to 2 weeks; the September-to-November peak can stretch to three. Parameter mismatch or non-compliant labelling that bounces materials adds another 1 to 2 weeks. Pass and the FCC ID is issued into the public database.
A few 6 GHz U-NII devices must take a PAG pre-approval first; this is outside the normal TCB cycle, and upfront communication can add weeks more — plan a separate allowance and do not fold it into the normal estimate.
Simple wireless is about 3 to 4 weeks, complex multimode 5 to 8 weeks, and cellular multimode terminals 8 to 16 weeks. These are one-pass reference values; rework and retest double them — do not use the ideal number to commit to a client.
The second half of the year is the overseas-shipping peak, adding 1 to 2 weeks overall; book as early as you can. Changing the antenna, amplifier or RF matching all count as major hardware changes requiring re-certification — think through the FCC impact before revising.
For FCC, pre-testing starts at the development stage, pushing spurious emission and frequency deviation down before submission, avoiding two months of road-test remediation later.
For those doing multiple-country wireless, BlueAsia's one-stop testing and certification reuses the RF data across countries, one test yielding multiple certificates with a single schedule.
Simple wireless is 3 to 4 weeks, complex multimode 8 to 16 weeks — do not commit to a client on the shortest number; leave enough margin or you will be passive, and treating the ideal as the plan will flip eventually.
One-pass testing is cheapest. Hold problems down with pre-testing so the formal submission needs little remediation and the cycle stays contained — a month of formal delay costs far more than pre-testing.
The second-half peak adds 1 to 2 weeks overall; book and submit early. Last-minute insertion basically cannot be scheduled; better to submit early and receive late than miss the delivery date and throw the whole line off.
Do not move RF components after hardware is frozen; any move may trigger re-certification, so lock the scheme early and assess before revising.
Keep a 10-to-12-week buffer; rework and retest routinely double, so do not plan on the ideal cycle — more buffer beats less.
Document bounce-back is a hidden pit; check the list early and kill the low-level photo-and-label errors up front to avoid two months of drag later.
For multi-country parallel work, reuse the RF data — one test yields multiple certificates, saving both time and money over single-country applications one by one.
Do not send only bare units; send accessories and packaging together and verify the label in sync, avoiding another round of labelling later.
Follow standard updates; an old-version report cannot support a new declaration, and when revising remember to reissue the documents — do not use old documents for new goods.
Certification is not the end; post-market spot checks and change tracking need an owner — do not assume the job is done once the certificate arrives.
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!
Related News
