CPSC eFiling Is Now Mandatory: What Importers Must Do This Month

As of July 8, 2026, CPSC eFiling is no longer a deadline to prepare for — it is being enforced at the port. Importers of regulated consumer products must now transmit certificate of compliance data through CBP's ACE system at entry, and a missing or defective filing can stop cargo from being released. Here is what to check now if your first covered entries are moving this month.

The CPSC eFiling deadline has passed. As of July 8, 2026, importers of regulated consumer products must transmit certificate of compliance data electronically through CBP's Automated Commercial Environment (ACE) at the time of entry — and CPSC is screening that data before release, not requesting paperwork afterward. If your covered products are moving this month, the question is no longer how to prepare. It is whether your entries are actually filing correctly, and what to do when one is not.

This article reflects CPSC's Final Rule on Certificates of Compliance (amending 16 CFR Part 1110), published in the Federal Register on January 8, 2025. Enforcement began July 8, 2026 for most entries; goods entered from a Foreign Trade Zone for consumption or warehousing must comply by January 8, 2027. Covered products and HTS lines can change — confirm current requirements against CPSC's official eFiling resources.

What Changed on July 8 — and What It Looks Like at the Port

For covered consumer products, certificate of compliance data now travels as a Partner Government Agency (PGA) message set with the entry itself. CPSC has said it will use algorithms to analyze the filed data and target higher-risk shipments — including low-value shipments that occur frequently. In practice, that means a missing, incomplete, or mismatched filing can single out a shipment for increased inspection, a hold, or refused release, while identical cargo with clean data moves through.

The scope has not changed: eFiling applies to finished consumer products subject to a CPSC mandatory standard, rule, or ban — both children's products requiring a Children's Product Certificate (CPC) and general-use products requiring a General Certificate of Conformity (GCC). CPSC has identified over 600 HTS tariff lines within scope, and there is no de minimis exemption — Section 321 shipments valued at $800 or less must eFile too.

The Three Failure Points Showing Up First

1. Products nobody flagged as covered. Scope is driven by HTS classification. A product misclassified out of a covered tariff line — or never screened against the 600-plus covered lines at all — arrives with no certificate data filed, and the gap surfaces at entry, when it is most expensive.
2. Certificate data that exists but is not entry-ready. Many importers hold valid CPCs and GCCs as PDFs. eFiling needs the underlying data elements — product identifier, applicable CPSC rules, dates and places of manufacture and testing, lab and records-custodian contacts — structured and available to whoever transmits the entry.
3. Assuming the broker has it handled. A broker can transmit the data, but the importer remains legally responsible for its accuracy and completeness. If you have not confirmed what your broker is transmitting for each covered SKU, you are carrying exposure you have not looked at.

Entries moving now and not sure your certificate data is transmitting correctly?

If a Shipment Gets Held

When an entry is flagged over certificate data, work the problem in order: identify what CPSC or CBP flagged (a missing filing, a defective one, or a data mismatch), correct and retransmit the certificate data, and coordinate through your broker with the port. Do not treat it as a one-off. A defect in one SKU's certificate data usually repeats on every future entry of that SKU until the underlying record is fixed — in your product file, or in the CPSC Product Registry if you use the reference method.

Full Message Set vs. Product Registry: You Can Still Switch

Importers who scrambled to meet the deadline mostly defaulted to the Full PGA Message Set — transmitting all certificate data elements with every entry. That works, but it re-keys the same data endlessly. The Reference PGA Message Set stores certificate data once in CPSC's Product Registry and transmits a reference identifier per entry line. For importers bringing in the same certified products repeatedly, moving to the Registry now reduces both effort and the surface area for data-entry errors on every future entry.

The Deadline Still Ahead: FTZ Entries, January 8, 2027

One phase-in remains. Goods entered from a Foreign Trade Zone for consumption or warehousing must comply with eFiling beginning January 8, 2027. Importers using FTZs saw July 8 pass without disruption — which makes it easy to assume the rule does not bite. It does; it just bites later. The preparation is identical: screen products against the covered HTS lines, structure the certificate data, choose a filing method, and confirm who transmits.

The Post-Deadline Checklist

• Pull your entries since July 8 and confirm covered products actually transmitted certificate data — do not assume silence means compliance.
• Re-screen your full catalog against the covered HTS lines, including new SKUs added since your original scoping.
• Verify Section 321 / low-value shipments are eFiling — there is no de minimis exemption.
• Confirm with your broker, in writing, exactly what is transmitted per covered SKU and who maintains the source data.
• If you are re-keying full certificate data every entry, evaluate moving to the CPSC Product Registry reference method.
• If you enter goods from an FTZ, start the same preparation now against the January 8, 2027 date.

This article summarizes CPSC's Certificates of Compliance Final Rule (amending 16 CFR Part 1110) and CPSC's official eFiling guidance as of publication. Requirements, covered HTS lines, and program details can change — confirm current details on CPSC's eFiling pages before acting.

This article is for general informational purposes only and is not legal advice. Whether a specific product is covered, which certificate applies, and how to respond to a hold should be reviewed based on the facts of each product and entry.