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

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.

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.

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