Product category

General-use electronics, GCCs, and CPSC eFiling

Prepare GCC-oriented electronics records around model identity, power/battery configuration, warnings, reasonable testing, and broker packet data.

Audience: Importers of general-use consumer electronics, accessories, battery-powered products, and electronic household items.

GCC records need a testing basis

General-use electronics may use a GCC certificate process when a covered rule or ban applies. The packet should make the testing or reasonable testing basis explicit.

Confirm whether a GCC is appropriate and which CPSC rules apply.
Track model, power source, charger, battery, enclosure, warnings, and instructions.
Do not treat CPSCReady as the source for deciding product rules or tariff codes.

Collect electronics-specific data

Supplier, factory, and lab records should match the exact electronic configuration being imported.

Model/SKU, firmware/hardware revision if relevant, power adapter, battery, enclosure, and accessory list.
Report number, test date, lab details, CPSC rules/standards tested, and exclusions.
Factory, manufacture date range, batch/lot, supplier, component, battery, charger, or label changes after testing.

Packet outputs

Prepare broker data with clear version notes for model or component changes.

GCC draft from source records.
Product and certificate details when the broker needs full product data.
Product Registry ID numbers if Product Registry is used.

Copy-ready assets

Templates you can adapt

Electronics supplier request

Please confirm model/SKU, hardware revision, firmware revision if relevant, power source, battery/charger/accessories, enclosure, warnings/instructions, factory, manufacture date range, batch/lot, report number, lab details, CPSC rules tested, and whether components, battery, charger, labels, packaging, supplier, or factory changed after testing.

Mini FAQ

Common questions

Is a GCC always needed for electronics?

No. Applicability depends on product-specific rules and facts. CPSCReady organizes records after those requirements are identified.

Next step

Prepare general-use electronics packet data with model/version notes.