The CPSC eFiling Final Rule, explained for importers.
This is a final rule under 16 CFR part 1110—not an executive order. Proof2Ship’s product education should use the precise regulatory terminology.
What changed?
CPSC’s eFiling program requires electronic filing of Certificate of Compliance information for covered imported regulated consumer products. The requirement became effective July 8, 2026 for most covered imports; products entered from a Foreign Trade Zone for consumption or warehousing have a January 8, 2027 effective date.
Two filing paths
Full PGA Message Set
The importer provides its broker the seven required certificate data elements for filing in ACE: Product ID, Citation Codes, Manufacture Date, Manufacture Place, Product Test Date, Testing Laboratory, and Point of Contact.
Reference PGA Message Set
The importer pre-enters and certifies certificate data in the CPSC Product Registry, then provides the broker three Certificate Identifiers: Certifier ID, Product ID, and Version ID. The broker references those identifiers in ACE.
Why Proof2Ship focuses on the Product Registry
The Product Registry is designed to store reusable certificate data, which is useful for importers repeatedly bringing in products covered by the same certificate. Proof2Ship can organize documents, map structured data, validate API structure, and prepare Registry imports. It does not need to become customs-entry software in the first release.
Product Registry is not ACE
The Product Registry is a stand-alone CPSC repository and does not automatically communicate with CBP’s ACE system. A certified Registry certificate must still be connected to the customs entry by the appropriate PGA filing path.
Certificate types
CPC: Children’s Product Certificates apply to covered children’s products and generally rely on required third-party testing from CPSC-accepted laboratories.
GCC: General Certificates of Conformity apply to covered general-use products subject to CPSC-enforced rules requiring certification.
What Proof2Ship should never promise
Proof2Ship should not promise that uploading a document makes a product “100% compliant” or legally cleared for shipment. The software can validate data structure, completeness against encoded rules, and CPSC API responses. Regulatory applicability, test sufficiency, classifications, and certification remain the responsibility of the appropriate business and authorized professionals.
Useful terms
CPSC eFiling · Certificate of Compliance · Product Registry · CPC · GCC · Product ID · Certifier ID · Version ID · Citation Codes · Testing Laboratory · Manufacture Date · Manufacture Place · Product Test Date · Point of Contact · PGA Message Set · CBP ACE · HTS Codes · Product Certification.
Educational content only; not legal, customs, or testing advice. Official CPSC and CBP materials control if requirements change.