Home / FCC authorization for electronic toys

Last reviewed: September 2026 · Copy link

FCC authorization for electronic toys

A CPC covers product safety under the CPSC; the FCC covers a completely different regime: radio emissions and digital electronics. A Bluetooth-enabled toy needs FCC equipment authorization for the radio, a plug-in electronic toy with a digital circuit may need it as an unintentional radiator, and none of that replaces the CPC. Sellers of electronic toys usually need both certificates, from both agencies’ systems.

Which toys trigger FCC rules

  • Radio-enabled toys: Bluetooth, Wi-Fi, or any intentional radiator (remote-control links, wireless mics).
  • Digital electronics: devices with clock circuits above the exemption frequency are unintentional radiators requiring verification or certification.
  • Toys with adapters or chargers: the adapter itself often needs its own FCC evaluation.

The two certificates, side by side

The CPC certifies product safety rules under the CPSC: mechanical hazards, lead, phthalates, tracking labels. FCC equipment authorization certifies electromagnetic compliance under a different agency with its own lab requirements. They do not substitute for each other, and electronic toy sellers should maintain both files per product: safety report plus CPC in one folder, FCC authorization in the other, both linked in the vault notes.

Questions people ask

Do cordless toys with no radio need FCC authorization?

Purely mechanical or simple battery toys without digital circuitry generally stay outside FCC equipment authorization. When the toy contains any digital electronics, verify the exemption rather than assuming it.

Who issues the FCC authorization?

A Telecommunication Certification Body (TCB) certifies based on accredited lab measurements; the importer is responsible for having it. Your test lab can coordinate both the safety and radio testing.

Does the CPC mention the FCC authorization?

No: the CPC cites CPSC safety rules only. The two documents live in the same product file but certify different regimes.

Related guides