CPSC eFiling Mandate: The 2026 Deadline Importers Can't Miss
From July 8, 2026, importers of CPSC-regulated consumer products must eFile their certificate of compliance into CBP's ACE at the time of entry. Here's who's covered, the data you'll file, the two filing paths, and how SMB importers get ready in time.
If you import toys, children's products, apparel with drawstrings, lighters, mattresses, electronics, or any other consumer product subject to a U.S. Consumer Product Safety Commission (CPSC) safety rule, a new electronic-filing mandate changes how you clear customs. Starting July 8, 2026, the certificate of compliance you already have to keep must be filed electronically into CBP's system at the moment of entry — not produced later if someone asks. Miss it and your shipment can be held or refused.
The short version: Under a CPSC final rule (published January 8, 2025, amending 16 CFR Part 1110), importers of CPSC-regulated consumer products must "eFile" the data from their certificate of compliance into U.S. Customs and Border Protection's (CBP) Automated Commercial Environment (ACE) at the time of entry or entry summary. The mandatory compliance date is July 8, 2026 for most entries — and January 8, 2027 for goods entered from a foreign-trade zone (FTZ) for consumption or warehousing. It applies to both children's products (which need a Children's Product Certificate, CPC) and covered general-use products (which need a General Certificate of Conformity, GCC), and it applies even to low-value Section 321 de minimis shipments under $800. The single most useful prep step for a small importer: identify which of your SKUs are CPSC-regulated, get the certificate data ready, and make sure your customs broker can transmit it in ACE before your goods arrive.
What actually changes on July 8, 2026
Nothing about who must certify changes — the duty to issue a certificate of compliance for CPSC-regulated products already exists. What changes is the timing and the format of how that certificate reaches the government.
Today, an importer keeps the certificate on file and "furnishes" it to CBP or CPSC on request. After July 8, 2026, the certificate data must be transmitted electronically through CBP's ACE system at the time of entry, where CBP shares it with CPSC. In practice this turns a passive recordkeeping obligation into an active, transaction-by-transaction filing — one that happens inside the same customs entry your broker already files.
This is why the deadline matters even though "you already needed a certificate." If the data isn't in ACE when the entry is filed, the entry is incomplete, and CPSC/CBP can hold, delay, or refuse the goods.
Who is covered — and who is not
The mandate reaches finished consumer products that are subject to a CPSC mandatory safety rule, standard, or ban for which a certificate of compliance is required. It does not reach every product on the truck — only the regulated ones. The two certificate types map to two product categories:
| Product type | Certificate required | Typical examples |
|---|---|---|
| Children's products (designed/intended primarily for children 12 and under) | Children's Product Certificate (CPC) — must be based on third-party testing by a CPSC-accepted lab | Toys, cribs, strollers, children's apparel, children's jewelry, pacifiers, kids' furniture |
| Covered non-children's (general-use) products subject to a mandatory rule | General Certificate of Conformity (GCC) | Mattresses, lighters, certain household chemicals, portable generators, some electrical products, bicycle helmets |
| Products with no applicable CPSC mandatory rule | None | Many general merchandise items not tied to a CPSC standard |
Two scope points that surprise importers:
- Section 321 de minimis shipments are covered. Even products valued under $800 that claim the de minimis duty exemption under 19 U.S.C. § 1321 must eFile the certificate data if the product is CPSC-regulated. Low value does not exempt you from product-safety certification.
- FTZ entries get a later date. Goods imported into a foreign-trade zone and later entered for consumption or warehousing have a separate compliance date of January 8, 2027.
If you're not sure whether a product you import is CPSC-regulated, that determination — not the filing mechanics — is usually the harder question, and it's worth resolving well before July 2026.
What's on the certificate: the data you'll eFile
The rule doesn't invent brand-new facts; it standardizes the certificate fields you already need and pushes them into ACE. Rather than memorize a count, treat the certificate as a checklist. The core data elements are:
| Data element | What it means |
|---|---|
| Product identification | At least one unique identifier (GTIN, UPC, SKU, model number, serial number, or a registered/alternate ID) plus a description sufficient to match the product to the certificate |
| Applicable CPSC rule(s) | Each consumer-product safety rule, standard, or ban the product is certified to |
| Certifier identification & contact | The U.S. importer (for imports) or domestic manufacturer responsible for the certificate, with contact details |
| Records custodian | The party that maintains the supporting test records, with contact details |
| Date and place of manufacture | When and where the product was manufactured |
| Date and place of testing | When and where the product (or its components) was tested |
| Attestation of compliance | The affirmative statement that the product complies with the cited rules (and, for children's products, that testing was done by a CPSC-accepted lab) |
For children's products, the testing must trace back to a CPSC-accepted third-party laboratory; for general-use products, a GCC can rest on a reasonable testing program or, where permitted, the applicable standard. Getting these fields organized per SKU now is the bulk of the preparation work.
How you'll file: two paths (pick the one that fits your volume)
CPSC built two ways to get the data into ACE. The choice has real workflow consequences for a small importer:
- Full PGA Message Set. Every certificate data element is transmitted through ACE with the entry. Best for importers (or brokers) whose products and certificates change frequently shipment to shipment.
- Reference PGA Message Set (Product Registry). You enter the certificate once into CPSC's Product Registry, receive a unique reference ID, and then transmit just that reference ID through ACE on each entry. This is the efficient path for importers who repeatedly bring in the same certified products — set the certificate up once, reuse the reference ID, and avoid re-keying every field on every entry.
For most SMBs importing a stable catalog of consumer goods, the Reference / Product Registry path is the one to plan around. It front-loads the work and then makes each subsequent entry lightweight.
This isn't a new, untested system bolted on at the last minute. CPSC and CBP have run a voluntary beta pilot since 2023 (starting with roughly three dozen importer participants and later expanded to thousands of seats), so the message sets and the Product Registry are already live to learn on before the mandate bites.
What SMB importers should do now
You have until July 8, 2026, but the preparation is mostly inventory and coordination work that takes time:
- Build a SKU-by-SKU map of what's CPSC-regulated. For each product you import, determine whether a CPSC mandatory rule applies and which certificate (CPC or GCC) is required. This classification step is the foundation — everything else depends on it. Our first-time importer checklist and import/export documentation guide walk through the broader entry-documentation picture.
- Collect and clean your certificate data per SKU. Confirm you have a valid certificate with all the required fields — including a unique product identifier and the testing/records-custodian details — for every regulated product.
- Decide Full vs. Reference (Product Registry) filing. If you reimport the same products, register them in CPSC's Product Registry now and capture the reference IDs.
- Talk to your customs broker early. Your broker is almost certainly the one transmitting in ACE. They need your certificate data (or reference IDs) before the goods arrive, not at the dock. If you don't have a broker, or aren't sure whether you need one, see when to hire a customs broker.
- Pressure-test the de minimis assumption. If part of your volume comes in as sub-$800 Section 321 shipments, remember those are covered too — confirm your fulfillment/3PL flow can attach the eFiling data.
- Don't let classification errors cascade. A wrong product classification can pull the wrong CPSC rule (or none) into your certificate. The same discipline that prevents HS-code misclassification penalties applies here.
How this fits with tariffs and the rest of your entry
CPSC eFiling is a product-safety requirement, not a tariff. It sits alongside — not instead of — your duty obligations: a regulated consumer product still owes whatever Section 301, Section 232, or reciprocal tariffs apply, and now also needs its certificate data in ACE at entry. The two are filed in the same customs transaction but answer to different agencies (CBP/Treasury for duties, CPSC for safety).
If you want help mapping a specific product to its CPSC rule, certificate type, or HS classification, the TariffCenter.AI assistant can talk through your SKUs and point you to the right certificate path before the July 8, 2026 deadline.
Bottom line
The CPSC eFiling mandate doesn't add a new product-safety obligation — it changes when and how you prove the one you already have. From July 8, 2026 (January 8, 2027 for FTZ consumption/warehouse entries), the certificate data for every CPSC-regulated consumer product must be eFiled in CBP's ACE at the time of entry, covering both CPC children's products and GCC general-use products, down to sub-$800 de minimis shipments. The importers who treat the next stretch as setup time — mapping regulated SKUs, cleaning certificate data, registering repeat products in CPSC's Product Registry, and briefing their broker — are the ones whose consumer goods keep clearing customs without a hold.