Blue Asia Labs - Testing, Inspection and Certification Services

Certification Guides

FCC Certification Guide for Wireless Products Exporting to the USA

FCC certification is the gateway for electronic products entering the United States. Choosing the right rule part and approval route at the start determines your cost and schedule — this guide explains the decision points we cover with every client.

Which FCC Rule Part Applies?

Rule partProduct typeApproval route
Part 15Unintentional radiators and low-power transmitters (Wi-Fi, Bluetooth)SDoC or Certification
Part 18ISM equipment (induction cooking, wireless charging)SDoC
Part 22/24/27Cellular handsets and modulesCertification (FCC ID)
Part 90/95Private land mobile and PCS devicesCertification (FCC ID)

SDoC vs Certification

Supplier's Declaration of Conformity (SDoC) applies to devices that do not transmit (digital products, LED drivers) and some Part 15 receivers: you test at an accredited lab, keep the report, and self-declare — no FCC filing, no FCC ID.

Certification applies to transmitters: measurements must be performed at an FCC-recognised accredited lab, and the report is submitted by a TCB (Telemetry Certification Body) to obtain an FCC ID. The FCC ID must be labelled on the product.

Certification Process

  1. Grants and scoping — confirm the rule parts, applicable standards (FCC Part 15.247/15.407, RSS-247 etc.) and whether SAR evaluation is needed.
  2. Pre-scan and formal testing — conducted at our accredited lab with TCB-recognised scope.
  3. TCB filing — we submit the test report, photos, block diagram, user manual and operational description through the TCB.
  4. Grant issued — typically 2–6 weeks after filing; the FCC ID becomes public and can be labelled.

Timeline and Pitfalls

A typical FCC ID project takes 3–5 weeks end-to-end. The most common delays come from: missing antenna gain data, firmware changes between test and production, host/module combination confusion, and SAR requirements for body-worn devices. Sending complete documentation with the samples avoids most of these.

Frequently Asked Questions

What is the difference between FCC ID and SDoC?

FCC ID (Certification) is required for transmitters and involves TCB filing and a public grant; SDoC is a self-declaration for non-transmitting or receiver-only devices with no FCC filing.

Can I test in China and still get an FCC ID?

Yes, as long as the laboratory holds FCC-recognised accreditation (A2LA or equivalent) with the correct scope. Blue Asia Labs tests in Shenzhen and files through an accredited TCB.

How much does FCC certification cost?

Costs scale with the number of radio technologies, power levels and whether SAR is required. Transmitter certifications generally start higher than SDoC projects; request an itemised quotation for your exact configuration.

Does the FCC ID expire?

The grant does not expire, but it covers a specific hardware/firmware/antenna configuration. Any material change requires a new grant or a Class II permissive change.

Request a free quotation — we will confirm the rule parts, route and timeline for your product within one business day.

SHARE

Written by

Blue Asia Labs Engineering Team

CNAS-accredited testing engineers sharing field notes on RF, EMC and global certification.

Get a Quote

Online service

[email protected] 4000259520 8613534225140
Home Hotline Mobile E-mail
Top
Contact Us
We use cookies to improve your online experience. By continuing to browse this website, you agree to our use of cookies.

Cookies

About Cookies

Cookies are small text files stored on your device when you visit a website. Blue Asia Labs uses cookies to remember your language preference, keep forms secure and understand how visitors use our pages.

Cookies We Use

Strictly necessary — language selection and form security. These cannot be disabled.
Performance — anonymous visit statistics that help us improve the site.

We do not use advertising or tracking cookies. You can block or delete cookies in your browser settings at any time; some features may not work as expected.

Contact

Questions about this policy? Email [email protected].