CPSC eFiling requirements: What businesses need to do before 8 July 2026

First published: June 2026

From 8 July 2026, importers of regulated consumer products in the U.S. need to submit certificate data electronically to U.S. Customs and Border Protection through the Automated Commercial Environment (ACE) at the time of making product entry.

That may sound like a simple filing change, but in practice it is much bigger than that. CPSC eFiling moves product compliance closer to day-to-day import operations. Instead of keeping certificates somewhere in the background, businesses now need the right product testing and certificate data ready when shipments move.

For brands, manufacturers, and importers across softlines, hardlines, and toys, the issue is not only regulatory compliance but also data quality, internal ownership, and team collaboration. Businesses that identify the right partner for support and prepare early should find it easier to control risk, reduce border friction and keep goods moving. Those still relying on scattered spreadsheets, old test records or ad hoc document requests are more likely to feel the strain.

Learn about the CPSC eFiling digital solution from Eurofins Softlines & Hardlines. With seamless submission workflows, flexible operations, and no set-up fees, we have put the right process in place so you have one less requirement to worry about.

Contact us now to ensure the smooth transition to CPSC eFiling and receive best-in-class support.

How CPSC eFiling changes import operations?

CPSC eFiling does not create a new category of regulated product; however, it changes how certificate information is submitted and used at the point of entry. That means compliance teams, sourcing teams, suppliers and brokers all need access to accurate, current product information in a form that can actually be used.

In practical terms, businesses need to know exactly which products are in scope, whether a product needs a Children’s Product Certificate (CPC) or a General Certificate of Conformity (GCC), which citation codes apply, and how product identifiers are being managed across shipments. If that information is incomplete or inconsistent, the filing process becomes harder than it needs to be.

What importers need to do now?

Importers sit at the centre of the process. Even where a customs broker files on their behalf, CPSC’s guidance is clear that the importer is ultimately responsible for product certification. That makes eFiling a business process issue, not something that can simply be handed off.

In practice, importers need a reliable way to identify in-scope SKUs, maintain accurate certificate data, and deliver usable information to brokers at the right time. They also need to make sure product data stays aligned when a supplier changes, a factory moves, a product is modified, or annual testing is renewed. This is where many businesses discover that they do have compliance records, but not in a form that supports real-world import activity.

What manufacturers and suppliers need to understand?

Manufacturers and suppliers may not file directly into ACE, but they have a direct influence on whether the filing goes smoothly. If factory details are incomplete, test references are unclear, or certificate data does not match the exact product version being imported, the importer will struggle to file accurately.

That matters especially in product categories with wide SKU ranges and changing specifications, such as toys, children’s clothing, homewares and hardlines. Suppliers that can provide clear, current and traceable compliance data will be much easier for U.S. importers to work with. In that sense, CPSC eFiling is also pushing better upstream discipline.

Full PGA Message Set or Reference PGA Message Set?

CPSC gives importers two routes for electronic filing.

The Full PGA Message Set means the importer provides all the required certificate data directly for filing in ACE. CPSC’s final rule identifies seven data elements for this route: a unique product identifier; all applicable CPSC rules, regulations, bans, or standards; the name and contact details of the party certifying compliance; the name and contact details of the individual maintaining the records; the date and place of manufacture, including manufacturer details; the most recent testing date and location, including the testing body or laboratory details; and the required certification attestation confirming the product complies and that the information provided is true and accurate.

The Reference PGA Message Set works differently. The importer first stores the certificate information in the CPSC Product Registry, then files three certificate identifiers through ACE: Certifier ID, Product ID and Version ID. CPSC says this route is particularly useful for businesses that repeatedly import the same regulated products, because certificate records can be reused when the certificate details remain unchanged.

There is no single best option for every business. A company with frequent repeat imports may prefer the control and reusability of the Product Registry model. A business with a smaller range or less repetitive import patterns may find the Full PGA route more practical. The right choice depends on product volume, internal systems, broker coordination, and the maturity of the company’s compliance data.

If you are unsure which option best suits your business, contact us. Our dedicated CPSC eFiling experts would be happy to help!

Why is data governance the real challenge?

For many businesses, the most challenging part of eFiling will not be the filing itself. It will be the quality of the underlying data.

To file consistently, companies need accurate product identifiers, correct citation codes, manufacturing details, testing information, and clear ownership of certificate records. That sounds manageable until the product line expands, suppliers change, or a single SKU is available in several versions from different factories. At that point, weak data governance becomes a real commercial problem.

This is why many organisations are now reviewing where their compliance records sit and who controls them. Test reports buried in email chains, certificates saved in supplier folders, and product data spread across multiple systems may have been tolerable before. Under CPSC eFiling, that kind of fragmentation becomes much more visible.

Common mistakes businesses should avoid

One common mistake is assuming the customs broker can solve the problem alone. Brokers are critical, but they can only file what they are given. If the importer cannot provide complete and accurate certificate data, the risk remains with the importer.

Another common misunderstanding is believing that the CPSC Product Registry automatically sends data to ACE. It does not. CPSC describes the Product Registry as a stand-alone repository, and importers still need to provide the required identifiers to their broker so the Reference PGA Message Set can be filed correctly.

There is also confusion around Section 321 shipments. CPSC’s FAQ is explicit: where a product requires certification, there is no de minimis exemption for eFiling. Low-value shipments are not automatically outside scope.

The same applies to Disclaim PGA Message Sets. They are not mandatory, including for Section 321 shipments, although CPSC encourages them because they may help improve risk scoring and reduce confusion for products that are not covered.

How can Eurofins Softlines & Hardlines support CPSC eFiling compliance?

If your business imports regulated consumer products into the United States, now is the time to review your certificates, product data and broker workflow before the 8 July 2026 deadline. Our dedicated CPSC eFiling experts can help you assess product scope, strengthen certificate readiness and build a practical eFiling process that works across suppliers, SKUs and shipments.

Our CPSC eFiling digital solution is a robust and flexible process designed to help you link product testing, certification and entry processes more effectively. Specifically, we manage the submission of your certificate data into the CPSC Product Registry, via CSV bulk upload or API integration, enabling you as an Importer of Record to file the Reference PGA Message Set in the CBP ACE at the time of entry. You track certificate status and access issued certificates through the Eurofins Connected client portal, giving you visibility across your entire product programme.

Please note: Eurofins manages the Product Registry submission on your behalf. The ACE filing itself, whether the Reference or Full PGA Message Set, remains the responsibility of the Importer of Record and their designated customs broker.

For businesses, the strongest approach combines accurate testing and certification with the practical execution of CPSC eFiling data submissions. This is where Eurofins Softlines & Hardlines can add real value by bringing together regulatory expertise and operational excellence to support smooth, reliable compliance with CPSC eFiling requirements.

Contact us or visit our CPSC eFiling service page for more details.