Product Compliance

US eFiling of consumer-product certificates became mandatory 8 July: customs won't reject an unfiled shipment yet, but it's already scoring you for it

On 8 July 2026, the US Consumer Product Safety Commission's eFiling rule became mandatory: importers, domestic manufacturers and private labelers of CPSC-regulated consumer products must now file their certificate-of-compliance data electronically, through CBP's Automated Commercial Environment, at the moment of entry, not produce it later on request. Most coverage has filed this as a customs-paperwork upgrade. What it misses: CPSC itself says it will not have ACE reject entries solely for missing eFiling data at launch, only warning messages. The consequence that actually starts on day one is a risk score, built from whether certificate data is there, complete and correct, that determines how often CBP holds a company's containers for inspection from here on.

Naomie HaliouaCDO and co-founder 13 July 2026 · 6 min read

What actually changed on 8 July

CPSC's final rule revising 16 CFR Part 1110 was published in the Federal Register on 8 January 2025 (a correction followed on 24 September 2025), replacing the old model, where a paper or PDF certificate simply had to accompany or be producible for a shipment, with electronic filing of the certificate data itself. As of 8 July 2026, importers of most CPSC-regulated consumer products must eFile certificate data through CBP's ACE system, in CPSC's Partner Government Agency (PGA) message set, at time of entry. Two filing paths exist: the Full PGA Message Set, where the importer hands the complete certificate to its customs broker to file entry-by-entry, or the Reference PGA Message Set, where the importer pre-loads certificate data into CPSC's Product Registry once and gives the broker a reference identifier to cite on each subsequent entry. Goods admitted into a Foreign-Trade Zone and later entered for consumption or warehousing get a later date, 8 January 2027, to comply.

Three nuances that separate signal from noise

It's a soft launch, not a hard wall

CPSC does not intend to have ACE automatically reject an entry solely for missing eFiling data at launch: only warning messages are expected at first.

The certification duty itself didn't change: its visibility did

A valid General Certificate of Conformity or Children's Product Certificate was already required under the Consumer Product Safety Act. What's new is that a gap in that data is now visible to CBP electronically at entry, not just on later request.

Two filing paths, one upstream data requirement

Whether filed as a Full or Reference PGA Message Set, the same structured fields (product ID, applicable CPSC rule, certifier, manufacture and test dates and locations) must exist and be accurate before an entry can be filed at all.

8 Jan 2025

CPSC's final rule revising 16 CFR Part 1110 is published in the Federal Register.

24 Sep 2025

A correction to the final rule is published in the Federal Register.

8 Jul 2026

Mandatory eFiling of certificate-of-compliance data through CBP's ACE takes effect for most CPSC-regulated products entered for consumption or warehousing.

8 Jan 2027

Mandatory eFiling extends to products admitted into a Foreign-Trade Zone and later entered for consumption or warehousing.

No blocked shipments yet, but the score has already started

CPSC and CBP built the rule around a phased posture: at launch, an entry missing eFiling data still moves, flagged by a warning message rather than an automatic hold. But that leniency applies to the filing mechanism, not to the certification requirement behind it: a missing, false, or inaccurate certificate remains a violation of the Consumer Product Safety Act, exposing the certifier to civil penalties, criminal penalties, seizure of the goods, or a recall, exactly as before 8 July. What genuinely starts now, independent of any single blocked shipment, is that CPSC and CBP use eFiling completeness and accuracy as an input to an importer's risk score, which drives how often that importer's future entries get pulled for examination. In practice, an importer that treats 8 July as a soft deadline is opting into more frequent holds later, even while nothing visibly stops their shipments today.

2 message sets

Full PGA (broker files the complete certificate) or Reference PGA (pre-loaded in CPSC's Product Registry, cited by identifier)

6 months

the gap between the 8 July 2026 mandatory date and the 8 January 2027 date for Foreign-Trade Zone entries

7 data fields

product ID, applicable CPSC rule, certifier contact, records custodian, manufacture date/location, test date/location, attestation

The real subject: a "produce on request" duty became a real-time data feed

Before 8 July, a brand could hold a valid certificate somewhere in a compliance folder and treat the obligation as satisfied unless CBP or CPSC specifically asked to see it. That model tolerated certificates that existed but weren't structured, weren't centrally tracked at the SKU level, or weren't tied cleanly to the specific CPSC rule a given product was tested against. eFiling removes that slack: the certificate has to exist as structured data (product identification, the applicable rule number, testing and manufacturing dates and locations, a named records custodian) filed at the moment each shipment crosses the border, for every SKU, every entry. A brand sourcing the same product from two factories, or updating a formulation mid-year, now needs that certificate data current and correctly linked at the SKU level continuously, not refreshed only when someone asks.

Why it matters for brands

The rule reaches every importer, domestic manufacturer and private labeler of a CPSC-regulated consumer product (toys, apparel with drawstrings or flammability limits, electronics, juvenile products, and more) regardless of where that product was manufactured. A European brand exporting toys or electronics into the US through a US subsidiary or distributor is exposed exactly like a domestic importer: its certificate data has to be complete, structured and eFiled at entry, or its US-bound shipments start accumulating the kind of filing gaps that raise a risk score even while nothing visibly stops them today. Because the launch posture is lenient on rejections but not on the underlying certification duty, the brands most exposed are the ones reading "no automatic rejection" as "no urgency", and building up an inspection-risk profile they won't see the cost of until CBP starts pulling their containers more often.

Two ways to read 8 July

The narrow read

CPSC certificates go digital. Importers adapt their customs filing process. A back-office IT change, not a compliance one.

The structural read

A "produce on request" duty became a real-time, SKU-level data feed with a risk score attached, and the absence of a hard wall at launch is exactly what will let filing gaps compound quietly into more frequent inspections for any brand shipping into the US.

Frequently asked questions

What changed for consumer-product importers into the US on 8 July 2026?

CPSC's eFiling rule, revising 16 CFR Part 1110, became mandatory: importers, domestic manufacturers and private labelers of most CPSC-regulated consumer products must now eFile their certificate-of-compliance data through CBP's Automated Commercial Environment (ACE), in CPSC's Partner Government Agency message set, at the moment of entry, rather than simply holding a paper or PDF certificate available on request. Products admitted into a Foreign-Trade Zone and later entered for consumption or warehousing get a later date, 8 January 2027.

Will CBP reject a shipment that is missing eFiling data?

Not automatically, at launch. CPSC has stated it does not intend to have ACE reject entries or deny admission solely for a failure to eFile when the rule first takes effect: only warning messages are expected initially. But CPSC continues to enforce the underlying certification requirement separately, and uses eFiling completeness and accuracy to set an importer's risk score, which drives how often its future shipments are held for inspection.

What data has to be filed, and does this create a new certification obligation?

The eFiling itself does not create a new substantive certification duty: a General Certificate of Conformity or Children's Product Certificate was already required under the Consumer Product Safety Act. What's new is the format and timing: product identification, the applicable CPSC rule, certifier contact information, the records custodian, manufacturing date and location, testing date and location, and an attestation of compliance must now exist as structured data and be filed electronically at time of entry, either as a Full PGA Message Set or a Reference PGA Message Set drawn from CPSC's Product Registry.