Guide to the US CPSC eFiling Mandate for Cross-Border Shippers
By Rubi Rodriguez
Published on July 28, 2026
In short
As of July 8, 2026, importers of CPSC-regulated consumer products must electronically submit Certificate of Compliance data with the U.S. customs entry. To avoid filing errors and border delays, shippers should identify affected products, standardize product-level data, and coordinate with importers and customs brokers before tendering the shipment.
In short
As of July 8, 2026, importers of CPSC-regulated consumer products must electronically submit Certificate of Compliance data with the U.S. customs entry. To avoid filing errors and border delays, shippers should identify affected products, standardize product-level data, and coordinate with importers and customs brokers before tendering the shipment.
Since July 8, 2026, importers of regulated consumer products subject to Consumer Product Safety Commission certification rules must electronically submit data from the CPSC Certificate of Compliance when filing a U.S. customs entry.
These CPSC eFiling requirements call for the relevant certificate data to be submitted through a CPSC PGA Message set in ACE as part of the shipment’s entry filing.
For teams managing CPSC eFiling for cross-border shipping, physical readiness is no longer enough. A shipment may be packed, labelled, and handed to the carrier, yet still face a hold or border clearance delay if its compliance data is unavailable, submitted too late, or inconsistent with the customs entry.
The CPSC eFiling mandate therefore tests more than whether a valid certificate exists: it tests whether product-level data can move accurately between the supplier, the Importer of Record, the customs broker, and the shipping workflow.
Key Takeaways
- Since July 8, 2026, importers of CPSC-regulated products must electronically submit Certificate of Compliance data with the U.S. customs entry, via a PGA message set in ACE.
- A later deadline (January 8, 2027) applies to goods brought into a Foreign Trade Zone and subsequently entered for consumption or warehousing.
- The Importer of Record is generally responsible for filing, but shippers, manufacturers, certifying parties, and customs brokers all need aligned, consistent data well before the shipment reaches the border.
- eFiling applies to any commercially imported product that requires CPSC certification, regardless of shipment value or DTC/ecommerce model — there is no Section 321 exemption.
- Importers can file a full PGA message set per shipment, or use the CPSC Product Registry for products imported repeatedly, submitting a handful of identifiers instead of repeating full data every time.
What is the CPSC eFiling mandate?
The CPSC eFiling 2026 rule moves product certification from a mostly document-based process to electronic filing.
Importers must transmit the required Certificate of Compliance data to the Consumer Product Safety Commission through a Partner Government Agency (PGA) message set in ACE, as part of the corresponding customs entry.
A valid certificate still matters, but keeping it on file is no longer enough. The correct data must reach CPSC in the required format and at the right stage of the entry process.
What changed on July 8, 2026?
As of July 8, 2026, eFiling is mandatory for imported regulated consumer products that are subject to CPSC certification requirements.
Importers must now submit the required data with the customs entry instead of waiting for a document request. That preparation is especially important when shipping from Canada to the United States, where missing data can slow border clearance.
A later deadline applies to products brought into a Foreign Trade Zone and subsequently entered for consumption or warehousing: those requirements take effect on January 8, 2027.
Who is responsible for CPSC eFiling?
For CPSC eFiling for importers, the importer is generally the Importer of Record, which may be the owner, purchaser, or an authorized customs broker.
When a broker acts as the Importer of Record but is not responsible for product testing and certification, the owner, purchaser, or consignee may be identified as the certifying party.
Filing should never become the broker’s last-minute task. The shipper, manufacturer, importer, certifying party, and broker need to align the certificate details and shipment data well before the goods reach the border. Strong customs broker coordination helps prevent missing or conflicting information from delaying clearance.
Which products require CPSC certificate data?
CPSC eFiling does not apply to every product entering the United States. The mandate applies to products that already require CPSC certification. That includes goods covered by a General Certificate of Conformity (GCC) or, for children’s products, a Children’s Product Certificate (CPC).
Is your shipment subject to CPSC eFiling?
Start with a product-level self-assessment.
- Is the item a finished consumer product entering the United States?
- Is it subject to a rule, ban, standard, or regulation enforced by the CPSC?
- Is it designed or primarily intended for children aged 12 or younger?
- Does the applicable rule require a CPC or GCC?
- Have the relevant testing and certification requirements been completed?
An HTS code flagging alert in ACE is an important signal, but it is not a complete checklist. Some products may still require certification even when their code is not flagged. The business remains responsible for reviewing the product, the applicable safety rules, and whether certificate data must be filed. The CPSC Regulatory Robot can help businesses identify product-safety requirements by asking questions about the product’s intended users, materials, design, and function.
CPC or GCC: which certificate applies?
| Certificate | Applies to | Issued by | Testing basis | Records |
|---|---|---|---|---|
| CPC | Children’s products for ages 12 and under | Domestic manufacturer or importer | CPSC-accepted third-party testing | Kept by the certifying party or records custodian |
| GCC | General-use products subject to CPSC rules | Domestic manufacturer or importer | Product testing or a reasonable testing program | Kept by the certifying party or records custodian |
Does the rule apply to low-value or direct-to-consumer shipments?
Yes. If a commercially imported product requires CPSC certification, eFiling applies regardless of the shipment’s value or whether it is sold through an ecommerce or DTC model. There is no Section 321 or de minimis exemption for products that require certification.
What information must be filed?
The required certificate data covers seven core details: the finished product, the applicable safety rule or ban, the domestic manufacturer or importer certifying it, the person who keeps the test records, the dates and places of manufacture and testing, and the third-party laboratory when one is required.
This product-level data must be accurate and consistent with the shipment records. Even valid compliance data can cause problems when product names, identifiers, dates, or business details do not match across systems.
Lazr’s cross-border compliance checklist and solutions help teams centralize shipment details, connect data from ERP or WMS systems, and prepare customs documents before goods reach the border.
Full message set vs. Product Registry reference
Importers have two practical filing options. They can send all required data for each product with the CPSC PGA message set as part of the ACE filing. This may work well for occasional imports or products that change frequently.
For products imported repeatedly, the importer can store reusable certificate information in the CPSC product registry. The broker then makes a shorter PGA submission using three certificate identifiers that point to the existing record.
The product registry does not send information to ACE on its own, so those identifiers must still be included with the entry.
Where cross-border shipments are most likely to fail
Product data does not match the customs entry
When product-level data differs from the customs entry, the PGA message set may be rejected or sent back for correction, delaying release.
The broker receives the certificate data too late
Late or incomplete certificate data can lead to holds, extra broker work, added fees, and missed delivery dates.
Teams rely only on HTS flags
HTS flags are helpful, but they are not exhaustive. The Importer of Record must still determine whether the product requires certification.
Product identifiers differ across systems
Different SKUs or product names across suppliers, importers, and shipping records make it harder to match the right compliance data to the shipment, increasing the risk of filing errors.
How to prepare your shipping operations for active enforcement
Start by mapping the SKUs that may require CPSC certification and confirming who will act as the Importer of Record. Review each GCC, CPC, and related test record, then standardize product, manufacturer, and laboratory identifiers across your systems.
Next, choose between filing the full message set or using the Product Registry for reusable data. Test the handoff with your broker or software provider, and add a CPSC check before label creation or carrier tender. This catches missing or mismatched information while there is still time to fix it.
What CPSC eFiling data should you collect before shipping?
| What to collect | Typical source | Final validation |
|---|---|---|
| Product identifier: GTIN, SKU, UPC, model number, serial number, registered number, or approved alternate ID | ERP, product catalogue, invoice, certificate | Importer |
| Applicable CPSC rules: every rule, ban, standard, or regulation covered by the certificate | CPC, GCC, test report, regulatory assessment | Importer or compliance specialist |
| Manufacturing details: month and year, city, state or province, and country | Production or batch records | Importer |
| Testing details: test date or date range and testing location | Test report or certificate | Certifying party |
| Laboratory information: legal name, address, email, phone number, and required laboratory details | Test report and laboratory records | Certifying party |
| Records custodian contact: name, address, email, and phone number | Compliance records | Certifying party |
| Certifying party: legal business name, address, contact details, and role | Corporate and customs records | Importer |
| Electronic filing: complete certificate data or Product Registry identifiers | Broker filing system and ACE | Importer and broker |
Did you know? Lazr centralizes shipment data and documents, connects with ERP or WMS systems, and helps teams share complete information with importers and brokers before tender, reducing manual gaps and preventable delays.
Why CPSC compliance is also a shipping-data problem
A valid certificate is not enough when the information is scattered across ERP systems, product catalogues, suppliers, brokers, shipping platforms, and the product registry.
Compliance depends on complete, structured data reaching the right person at the right time. When those records do not align, even a compliant product can face corrections or clearance delays.
Build CPSC compliance into the cross-border workflow
Treat eFiling as part of the shipping process, not a last-minute fix. Centralizing shipment data and documents helps shippers, importers, and brokers spot missing information before it causes a hold.
Lazr gives shippers, importers, and brokers one place to work from, so missing documents and inconsistent data can be caught before they delay the shipment.
FAQ
What is the CPSC Regulatory Robot?
The Regulatory Robot is a free tool on cpsc.gov that helps businesses identify which product-safety rules may apply to them by asking questions about a product’s intended users, materials, design, and function. It does not replace certification, but it is a useful starting point for determining whether an item needs a GCC or CPC.
What’s the difference between filing a full message set and using the CPSC Product Registry?
A full PGA message set includes all required certificate data for a single shipment, filed directly in ACE. The Product Registry lets importers store reusable certificate information once, then reference it in later ACE filings with three certificate identifiers, which is generally more efficient for products imported repeatedly.
Does eFiling apply to low-value or direct-to-consumer (DTC) shipments?
Yes. If a commercially imported product requires CPSC certification, eFiling applies no matter the shipment’s value or whether it moves through an ecommerce or DTC channel. There is no Section 321 or de minimis exemption for products that require certification.
What is the difference between a CPC and a GCC?
A Children’s Product Certificate (CPC) applies to products intended for children age 12 and under and requires CPSC-accepted third-party testing. A General Certificate of Conformity (GCC) applies to general-use products subject to CPSC rules and can be based on product testing or a reasonable testing program. Both are issued by the domestic manufacturer or importer.
-
Rate sheet processing is costing you more than you think
By Rubi Rodriguez • July 24, 2026The hidden cost of manual rate sheet processing shows up in stale quotes, margin leakage, and high-value staff spending time on data entry instead of… -
What Is a Purchase Order & How Do They Work?
By Rubi Rodriguez • July 17, 2026A purchase order, or PO, is the document a buyer sends a supplier to formally request goods or services at an agreed price and quantity…. -
How to calculate dimensional weight for parcel shipping
By Rubi Rodriguez • July 10, 2026Carriers charge based on billable weight, meaning the higher of actual weight or dimensional weight, which is calculated using length × width × height divided…
