CPSC eFiling Checker
Screen one SKU for likely CPC/GCC data gaps before shipment.
What the checker returns
Product path, missing fields, supplier request.
Your result appears here
Enter one product or SKU. The checker will return a likely certificate path, missing eFiling fields, and a supplier request template.
The first answer is the certificate path
The checker is a first-screening tool. It routes the SKU to the most likely next action before you ask the factory for documents.
Likely CPC
Children products, toys, and child-use signals usually need a CPC path.
Likely GCC
General-use consumer products may need GCC data when a CPSC rule applies.
Manual Review
Unclear age, category, material, or rule signals should be checked by a specialist.
Low Risk
No obvious CPSC certificate signal appears from the screening answers.
Then close the data gaps
CPSC eFiling preparation usually turns into seven practical data fields. The checker shows which fields are missing for the screened SKU.
Ask suppliers for fields, not vague compliance paperwork
After the check, copy a supplier request that asks for the certificate, report details, factory data, lab, and responsible contact in one message.
Subject: CPSC eFiling data request
Please provide CPC/GCC certificate data for this SKU.
Include Product ID, rule citation, manufacture details.
Include test date, testing lab, report number, contact.
Official CPSC references
Use these CPSC pages as the source of truth when your team needs to confirm program rules, certificate paths, or filing references.
CPSC eFiling
Program hub for CPSC eFiling updates and implementation.
eFiling FAQ
Questions and answers for importers, brokers, and filers.
Does eFiling Apply to Me?
CPSC guidance on whether imported consumer products fall under eFiling.
Certificates and eFiling
Certificate guidance for products subject to CPSC rules.
Product Registry
Reference filing path for repeatable certificate records.
eFiling Document Library
CPSC user guides, data references, and filing documents.
Guidance and HTS List
January 2026 CPSC guidance and HTS list for electronic certificates.
Children's Product Certificate
Official CPC guidance for children products.
General Certificate of Conformity
Official GCC guidance for general-use consumer products.
CPC and GCC mean different handoffs
The form does not generate certificates. It helps you decide which certificate data conversation should happen next.
CPC: children product data
Toys, children apparel, and products intended for children 12 or younger usually need test-backed children product certificate data.
GCC: general-use product data
Adult consumer products may need general certificate data when a CPSC rule, ban, standard, or regulation applies.
Product Registry or Full PGA Message Set?
Filing method comes after SKU readiness. Stable repeat products may fit registry references; limited or changing products may need full certificate data in the entry workflow.
Read comparisonConfirm product and certificate data
Decide whether records repeat across shipments
Hand broker a registry reference or full data set
Built for shipment preparation teams
The checker is useful when the team has a product list but not enough certificate context to brief the supplier or broker.
Importer operations
Pre-check regulated SKUs before the broker asks for data.
Amazon and marketplace sellers
Separate CPC/GCC questions from generic supplier paperwork.
Sourcing teams
Ask factories for the fields that actually block shipment.
Broker handoff
Turn vague product notes into a cleaner certificate checklist.
Batch Check is next
CSV should reuse the same single-SKU logic after the product check flow has enough real feedback. Until then, send a product list for manual review when shipment timing matters.
Send product listUpload CSV
Planned after the checker has enough real SKU feedback.
Map columns
Planned after the checker has enough real SKU feedback.
Export gaps
Planned after the checker has enough real SKU feedback.
Build your CPSC eFiling checklist
Use the guide library to brief suppliers, brokers, and internal SKU owners with the same vocabulary.