First published: August 2026
The U.S. Consumer Product Safety Commission’s eFiling programme changed how certificate information for imported regulated consumer products is submitted at entry. Beginning 8 July 2026, importers of consumer products subject to CPSC certification requirements must electronically file certificate data. For products imported into a Foreign Trade Zone and later entered for consumption or warehousing, the effective date is 8 January 2027.
For many businesses, the main challenge is ensuring that the right product, testing, factory, and certificate data are gathered, verified, and transmitted correctly and on time. In practice, CPSC eFiling is a mix of data and process control issues as well as regulatory compliance requirements.
For importers, brands, retailers, and supply chain partners, a more effective way to prepare is to treat eFiling as a coordinated workflow linking testing, certification, and entry filing. A certificate cannot be reliably eFiled if the supporting compliance records are incomplete, mismatched, outdated, or difficult to retrieve. That is why you should start now by reviewing product scope, assigning ownership, standardising data, validating certificate content, and confirming how information will move between internal teams, suppliers, laboratories, and brokers.
eFiling does not create new product safety rules; rather, it changes how required certificate data is provided for imported regulated consumer products. The first step to be ready for eFiling is to confirm whether the product is actually subject to CPSC certification requirements. CPSC explains that products requiring certification are finished products subject to a consumer product safety rule, ban, standard, or regulation, and imported for consumption or warehousing or otherwise distributed in commerce.
For children’s products, the applicable certificate is a Children’s Product Certificate (CPC). For non-children’s products subject to applicable rules, the certificate is a General Certificate of Conformity (GCC).
Importers should be aware that there is no Section 321/de minimis exemption from eFiling for products that require certification. Any product requiring certification must have an eFiled certificate, regardless of the shipment value.
eFiling generally applies to commercial consumer-to-consumer sales, to resold or overstock products if they are regulated finished products to be distributed in commerce, and to used products manufactured after the relevant rule, ban, or standard took effect. By contrast, used products manufactured before the effective date of the applicable rule do not require a certificate and therefore are not subject to eFiling. Noncommercially consumer-to-consumer shipments, such as gifts or personal effects meeting CPSC’s stated criteria, are excluded.
Confirm whether your products are in scope
To confirm scope, start with the finished product being imported and determine whether it is subject to a CPSC rule, ban, standard, or regulation that requires certification. If so, the product will generally require a GCC or CPC, and its certificate data may need to be eFiled at entry. You should verify the product category, intended user, and use case, then check CPSC’s Regulated Product Database, Regulatory Robot, and eFiling guidance to identify the applicable requirements and citations.
Assign clear internal and external ownership
CPSC is explicit that importers are ultimately responsible for product certification. In practice, however, successful eFiling depends on coordinated inputs from several parties. Suppliers and factories may hold manufacturing details, product identifiers, and production-date information. Testing laboratories hold the evidence that supports certification. Brokers may submit the required data into CBP’s ACE environment, but they cannot create compliant certificate information if the importer has not provided complete and accurate data. The most effective approach is to designate one internal owner or cross-functional team with authority over compliance data, document control, and broker communication so that filing responsibility does not become fragmented.
Build an eFiling-ready compliance data set
A practical CPSC eFiling checklist starts with building an eFiling-ready compliance data set for each covered product. CPSC identifies seven required data elements for the certificate information used in eFiling: Product ID, Citation Codes, Manufacture Date, Manufacture Place, Product Test Date, Testing Laboratory, and Point of Contact.
The Product ID must uniquely identify the product and must be one of the accepted ID types listed by CPSC, such as GTIN, SKU, UPC, model number, serial number, registered number, or alternate ID. It is strongly recommended to use at least one identifier that can also be found on product packaging, the packing list, or the invoice so that the product can be identified more easily by CPSC personnel.
The product’s applicable citation codes must also be correct. CPSC directs businesses to its Document Library, Regulatory Robot, and related guidance to determine applicable citations and testing exclusion codes and advises importers to work with CBP and trade partners on HTS-related questions. This means you should not rely on internal shorthand descriptions alone. Product classification, rule mapping, and certificate content should all align.
The manufacture place and manufacture date fields also deserve careful attention. CPSC requires the place where the finished product was manufactured, produced, or assembled, including the name, full address, and contact information of the manufacturing party. If a product is made at multiple facilities, or if production shifts from one site to another, importers should review whether the existing certificate information still correctly describes the imported goods. Weak factory-data controls are a common source of avoidable filing problems because shipment data, supplier records, and certificate records can drift apart over time.
Choosing your filing workflow: Full PGA vs. Reference PGA
You also need to decide how you will file certificate data. CPSC provides two filing pathways: the Full PGA Message Set and the Reference PGA Message Set.
Under the Full PGA approach, the importer provides the broker with the required product certificate data elements, and the broker files them in the CBP ACE CPSC Partner Government Agency message set. Under the Reference PGA message set approach, the importer pre-enters product certificate data into the CPSC Product Registry and then provides the broker with the certificate identifiers used to reference that stored certificate during entry filing.
For businesses that repeatedly import the same regulated products under the same certificate details, the Product Registry can offer a more efficient structure. Product Registry is a secure online application where importers can store and manage product certificate data for use with Reference PGA Message Sets. It serves as a stand-alone central data repository and does not communicate with CBP’s ACE system, so importers must still communicate the required certificate identifiers to their broker for use in the filing process. For repeated imports, the Product Registry can streamline filing by allowing the same stored certificate to be referenced repeatedly as long as the product certificate details remain identical.
If using the Product Registry, importers should pay close attention to CPSC’s certificate identifier logic. CPSC identifies three certificate identifiers used in the Reference PGA workflow: Certifier ID, Product ID, and Version ID. The Version ID matters because certificate records are not static. If a certificate needs to be updated due to retesting, material changes, production changes, different manufacturing facilities, or other relevant changes, you should ensure that your internal controls can distinguish the current version from older records. Even where companies are not using the Product Registry immediately, this CPSC structure highlights an important operational reality: certificate data needs version control.
Final pre-shipment checks before filing
A robust pre-shipment review can reduce many of these risks. Before entry, importers should confirm that the product being shipped matches the certificate record, that the correct certificate type is being used, that the applicable CPSC citations are complete, that the manufacturing party details are current, that the testing laboratory information is correctly stated, and that the internal point of contact can quickly retrieve supporting records if requested. If the company is filing through a broker, the broker should receive the required data or identifiers early enough to prevent last-minute gaps.
Common CPSC eFiling data errors and how to avoid them
To avoid filing disruptions, companies should review common data-quality errors. One frequent issue is using a Product ID that does not consistently match the identifier used on packaging, invoices, internal ERP records, or shipment paperwork. Since CPSC relies on the Product ID to help identify the certified product, mismatches here can weaken traceability.
Another common problem is incorrect citation mapping, where a product is assigned incomplete or inaccurate CPSC rules. There is also a risk when the manufacturing party named in the certificate does not match the actual production source of the imported goods. Testing data can also create problems if the records relied upon do not support the exact finished product, if the most recent test date is outdated, or if component-part testing relied upon for certification has not been properly reflected in certificate information.
Confusion between GCC and CPC is another preventable error. Children’s products require a CPC and third-party testing by a CPSC-accepted laboratory, while other regulated general-use consumer products require a GCC based on the applicable rules. You should ensure that internal teams, suppliers, and brokers do not use those terms interchangeably.
In addition, if a testing exclusion applies, CPSC says a testing exclusion code must be provided with the product certificate when the product requires certification and a testing exclusion is being relied upon. This means you should not simply omit testing-related details without verifying whether an exclusion code is required.
Testing information is another area where you should prepare carefully. CPSC requires the manufacturer or importer to certify compliance based on passing test results and other reasonable testing programmes, depending on the product and applicable rules. For children’s products, third-party testing by a CPSC-accepted laboratory is generally central to certification requirements.
When certifying a finished product, certificate details must reflect all testing relied upon to support certification, including testing conducted on component parts if that testing is being used to support the compliance affirmation.
The certificate must state all applicable rules, bans, standards, and regulations, the most recent date of testing, and identify each testing laboratory that conducted such testing. Beginning 8 July 2026, revised Part 1110 also requires identification of any testing exclusions relied upon.
That is why testing, certification, and eFiling should not be managed as isolated activities. A finished product may have valid test reports somewhere in the organisation, but that does not automatically mean the eFiling data is ready. Importers should verify that the product described in the testing records matches the finished product being certified, that the cited rules correspond to the actual regulatory scope, that the named laboratory information is complete, and that the most recent testing date reflected in certificate records is accurate. Optional fields such as test report IDs, report keys, or URLs may not be required for filing, but CPSC encourages them, and importers may still be asked to provide supporting test records and related information upon request.
Contact us if you need help aligning test reports, certificate data, and eFiling requirements. As a CPSC-accepted laboratory, we can help you confirm that your testing records support compliant certification and import filing.
If you are reviewing your product portfolio, testing records, or certificate data to comply with the CPSC eFiling requirement, our CPSC eFiling digital solution offers 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 to 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.
Certificate status and issued certificates can be accessed via the Eurofins Connected client portal, providing visibility across your entire product programme. Our dedicated teams can support you with testing, certification-related documentation, and a more structured approach to compliance data preparation for U.S. market access.
Contact us or visit our CPSC eFiling digital solution page for more details.