The deciding criterion is whether the product actively emits RF energy: intentional radiators go through FCC ID, unintentional radiators go through SDoC. Products with wireless transmission functions such as Wi-Fi, Bluetooth, cellular, LoRa, or UWB are intentional radiators and must apply for an FCC ID. Electronic products without any wireless transmission, operating only via cables or internal clocks, generally go through the SDoC self-declaration procedure. For products with wireless functions whose modules have already obtained a separate FCC ID, the host device may still need to be evaluated according to the conditions, and the module certificate cannot simply be carried over.
| Comparison Item | FCC ID (Certification) | SDoC |
|---|---|---|
| Applicable products | Intentional radiators, including wireless transmission | Unintentional radiators, ordinary electronics |
| Reviewing party | TCB review and issuance | Enterprise self-declaration |
| Entry into FCC database | Yes, certificate publicly searchable | No |
| FCC ID marking required | Yes | No |
| Typical timeline | 3-6 weeks | 1-2 weeks |
The six steps in order are: certification route determination, sample and documentation preparation, laboratory testing, report and technical documentation compilation, TCB review, and FCC database publication. An error in the first step will cause all subsequent work to be redone—this is the most common process risk point. The second step requires confirming that the prototype is a production-representative sample, with RF parameters and antenna conditions consistent with mass production. The third step is completed by a qualified laboratory, covering RF, electromagnetic compatibility, and RF exposure testing. The fourth step compiles test reports, circuit diagrams, block diagrams, user manuals, and other materials into technical files that the TCB can review. The fifth step is TCB review and issuance of the Grant. The sixth step enters the certificate information into the FCC equipment authorization database for public display.
Core documents include: FCC ID application form, authorization letter, circuit schematics, block diagram, circuit description, user manual, label sample and location description, RF exposure assessment materials, and test reports. Where module reuse is involved, the module's Grant and integration instructions must also be provided. For software-defined RF parameters, the method for locking power, frequency, and bandwidth must be described. The language of the documents, completeness of signature pages, and consistency of model naming all affect how quickly the TCB accepts the application. Model naming must be completely consistent across the application form, label, reports, and manual.
Once TCB review passes, the Grant is issued, and the FCC database then publishes it automatically—the two are sequential. The TCB is a telecommunications certification body authorized by the FCC, responsible for substantive review and direct issuance, with no case-by-case FCC approval required. After the Grant is issued, the certificate information is searchable in the FCC equipment authorization database, including applicant, model, FCC ID, frequency range, and testing basis. Once published, the information is publicly visible; if the model or applicant information is entered incorrectly, a change process is required, so verification before submission is especially critical. According to data in the database, the certificate data range is 05/06/2026 to 2026-10-25, with 1,156 new certificates and 695 new companies in the past 30 days, indicating that the authorization database is continuously updated and enterprises should refer to the latest publication when checking.
Time is concentrated in two segments—testing and TCB review: testing takes about 1-3 weeks, and TCB review about 1-2 weeks. Documentation preparation takes about 3-10 working days depending on the enterprise's cooperation, retesting after corrective actions takes about 1-2 weeks depending on the number of issues, and database publication is usually visible within a few working days after issuance. The overall 3-6 weeks assumes smooth testing; if RF metrics exceed limits or documentation is returned, the timeline extends accordingly. The SDoC timeline is 1-2 weeks. Multi-band, multi-standard products have more test items, and the testing segment will trend toward the upper limit.
The most common reasons for rejection are inconsistent documentation and missing RF exposure assessments, not test failures themselves. Specifically: the model on the application form does not match the model in the report, the label sample lacks the FCC ID marking location, the user manual lacks compliance statement wording, the RF exposure assessment does not cover the actual use distance, module reuse lacks integration instructions, and the authorization letter signature or validity period is non-compliant. Test-level rejections mostly center on spurious emissions exceeding limits, power exceeding limits, and bandwidth out of bounds. A checklist-based self-review in advance can significantly reduce back-and-forth.
No. An FCC ID must be reviewed and issued by an FCC-authorized TCB, and the enterprise must complete testing through a qualified laboratory and submit to the TCB. The enterprise is the applicant, but the issuance step is completed by the TCB.
It depends on whether the RF parameters and circuitry are identical. Models with completely identical RF sections and differences only in appearance or non-RF configuration can be applied for as a family of models; models with different RF parameters must be applied for separately.
The Grant itself has no fixed validity period, but after changes to product design, RF parameters, or key components, re-evaluation is required and re-application may be necessary. Published information remains searchable long-term.
In most cases, yes. The host device must be evaluated for RF exposure and electromagnetic compatibility under conditions where the module and host coexist, and the module Grant and integration instructions must be retained; whether a new FCC ID is required depends on the host's transmission characteristics.
Send your product spec and target market — we reply with scope, timeline and cost within one business day.
Email Mr. TaoBeice Testing · Tao Gong · CNAS L5516 · CMA 202319013572 · NTEK Group Partner Lab · Shenzhen, China
+86 199-2684-3993 · taowushuang@ntek.org.cn · 中文站