Home / Guides / CPSC certificate eFiling from July 8, 2026

Last reviewed: September 2026 · Copy link

CPSC certificate eFiling from July 8, 2026

Beginning July 8, 2026, importers of most regulated consumer products must electronically file certificate of compliance data with U.S. Customs and Border Protection through a Partner Government Agency (PGA) Message Set. A PDF in a desk drawer is no longer enough for entry — brokers need structured certificate fields tied to the shipment.
Export an eFiling pack

What “eFiling” means in practice

Instead of only keeping a paper or PDF certificate available on request, importers (or their brokers) transmit certificate data electronically at entry. That data must match the products in the shipment: identification, rules, certifying party, testing dates and places, and laboratory details for children’s products.

How sellers should prepare now

  • Issue certificates with complete, consistent fields — not free-text Word docs that omit required elements.
  • Keep one structured record per SKU/SKU family your broker can map into ACE.
  • Align commercial invoices, packing lists, and certificate product IDs.
  • Export a vault CSV/JSON for your broker well before July 2026, not the week of go-live.

Relationship to Amazon document asks

Amazon compliance and CBP eFiling are separate systems. Clearing Amazon does not clear customs, and vice versa. USA sellers who import children’s products need marketplace documents and entry-ready certificate data.

Questions people ask

Does eFiling replace the CPC PDF?

No. You still create and retain the certificate. eFiling is how certificate data is transmitted at import for covered products.

Who files — me or my broker?

Typically your customs broker or filer transmits the PGA Message Set, using data you provide. Give them clean structured fields, not screenshots.

Where can I export structured certificate data?

CPC ShadowOps can export vault certificates as CSV or JSON for broker handoff via the eFiling pack tool.

Related guides