If you import anything a consumer could plug in, wear, feed to a toddler, or plug into a wall, July 8, 2026 quietly became one of the most consequential compliance dates on your calendar. That's the day the Consumer Product Safety Commission stopped taking your word for it. Certificates of compliance that importers used to keep in a drawer — pulled out only if a customs officer happened to ask — now have to be filed electronically, product by product, before a shipment is even allowed to clear the port.
For a big-box retailer with a compliance department, this is a workflow change. For a solo Amazon seller sourcing baby gates from a factory in Shenzhen, it can mean a container sitting at the dock while nobody can produce the one document CBP is now looking for automatically instead of occasionally.
What Actually Changed
Since 2011, importers of CPSC-regulated consumer products have been required to have a valid certificate of compliance — a Children's Product Certificate (CPC) for kids' items or a General Certificate of Conformity (GCC) for general-use products like extension cords or space heaters. But "having" one and "proving" one were very different things. In practice, that certificate lived in a filing cabinet or a shared drive, and Customs and Border Protection only asked to see it if your shipment was flagged for inspection.
The new rule, finalized by the CPSC in December 2024 and phased in through mid-2026, eliminates that gap entirely. Starting July 8, 2026, importers must eFile certificate data directly into CBP's Automated Commercial Environment (ACE) — the same electronic system that processes tariff classifications and duty payments — at the time of entry, for every applicable shipment. No inspection trigger required. The certificate data becomes part of the standard entry filing, alongside your HTS code and country of origin.
A second wave applies to goods that pass through a Foreign Trade Zone before entering U.S. commerce: those get a 24-month runway, with the eFiling requirement kicking in January 8, 2027.
What You Actually Have to Submit
Importers now have two ways to get certificate data into ACE, and picking the right one matters for how much manual work this creates on every shipment.
Full PGA Message Set. You hand your customs broker seven data elements for every entry: product identification, the specific CPSC rules or standards the product is certified against, the manufacturing date and location, the testing date and testing lab, and a point of contact for the certifier. Your broker files it as part of the standard Partner Government Agency (PGA) message set that already accompanies every ACE entry. This is the simpler option to set up, but it means resubmitting the same data every time you import the same product — fine for occasional or low-SKU importers, tedious if you're shipping the same 40 SKUs every month.
Reference PGA Message Set. You pre-load your certificate data into CPSC's Product Registry once, get back a Certifier ID, Product ID, and Version ID, and then your broker just transmits those three reference identifiers on each entry instead of the full data set. This is the better option if you have recurring shipments of the same certified products — but it has a trap: uploading data to the Registry doesn't automatically flow through to your broker. You still have to hand your broker those three identifiers for every shipment, or the ACE filing comes in incomplete.
Either way, there's no shipment-value exemption. A $40 de minimis parcel carrying a CPSC-regulated product is subject to the same eFiling requirement as a container of 20,000 units. If the product legally requires a CPC or GCC, it requires an eFiled certificate — full stop.
What Happens If You Don't File
The CPSC has said that, at least initially, ACE won't hard-reject entries purely for a missing eFiling — expect warning messages rather than an automatic bounce in the first stretch after go-live. But "no auto-reject" is not the same as "no consequence." The agency has been explicit that it will still pursue formal enforcement: cargo holds, increased inspection targeting, and civil penalties that can run up to $120,500 per violation for a knowing or false certification. A missing or defective certificate is treated the same as any other Consumer Product Safety Act violation — which can also mean product recalls and, in serious cases, criminal referral.
The more immediate cost for most small importers won't be a fine. It'll be the shipment that doesn't move. A broker who can't complete a PGA filing because you never sent the certificate data is a broker who can't get your entry released, which means your inventory sits in a bonded warehouse accruing storage fees while you scramble to produce paperwork that should have been ready before the ship left port.
Getting Ready Before Your Next Shipment
A few concrete steps make the difference between a routine ACE filing and a stuck container:
- Audit your existing certificates first. Pull every CPC and GCC you currently rely on and confirm the required data elements — testing dates, testing lab, manufacture location, citation codes — are actually complete and current. A certificate that's technically on file but missing a data element is functionally useless under the new system.
- Talk to your customs broker now, not in your next shipping cycle. Confirm whether they have ACE PGA Message Set capability configured and tested for CPSC data specifically. Not every broker had this built out before the mandate; some smaller or regional brokers are still catching up.
- Decide Full vs. Reference PGA based on your shipment pattern. If you reorder the same handful of SKUs repeatedly, the upfront work of loading the CPSC Product Registry pays for itself within a few shipments.
- Build the certificate data into your sourcing paperwork. The cleanest fix is structural: require your factory or supplier to deliver complete, eFiling-ready certificate data as a condition of the purchase order, not as an afterthought you chase down after the goods are already on the water.
- Retain everything for five years. The eFiling requirement doesn't replace the underlying recordkeeping obligation — you still need to keep the certificates and their supporting test reports on file well after the shipment clears.
Why This Matters Beyond the Import Desk
The CPSC eFiling mandate is really a preview of where trade compliance is headed generally: fewer manual spot checks, more automated, real-time data matching against your entries. Import compliance data is now effectively part of your transaction records — reviewed automatically, tied to specific shipments, and expected to reconcile cleanly with what you're reporting elsewhere. That's the same discipline that good bookkeeping already demands of your financial data: every transaction traceable, every document where it's supposed to be, nothing that only exists as a promise you'll produce it if asked.
If a customs audit or a CPSC penalty ever intersects with your books — say, a seized shipment that needs to be written off, or storage fees that show up as an unplanned expense — having clean, auditable records makes that reconciliation straightforward instead of a forensic exercise. Beancount.io offers plain-text accounting that keeps every transaction transparent and version-controlled, so when compliance costs or one-off disruptions hit your business, your financial records are never the thing slowing down the response. Get started for free and see why developers and finance professionals are switching to plain-text accounting.