Mandatory CPSC eFiling has been live since July 8, 2026. If you import regulated consumer products, your Certificate of Compliance data must now move electronically into CBP’s ACE system at the time of entry, not sit in a file waiting for a request. This CPSC eFiling checklist is built for importers, brokers, and private labelers who are already past the main date and now need to tighten their data, and for Foreign Trade Zone (FTZ) users facing the January 8, 2027 applicability date.

The rule did not change which products need a certificate. It changed how and when certificate data is filed, and it exposed data gaps at the border that used to surface only during an audit. The sections below walk through what to confirm now.

Not sure your certificate data is eFiling-ready across every SKU and supplier? Request a compliance review to see where your gaps are before they surface at entry.

Key Takeaways

📌 CPSC eFiling became mandatory for most regulated consumer product imports on July 8, 2026, under the final rule amending 16 CFR Part 1110.

⏳ Goods admitted into a Foreign Trade Zone and later entered for consumption or warehousing have a separate applicability date of January 8, 2027.

📊 The Full PGA Message Set requires seven certificate data elements per entry; the Reference method requires three identifiers if the certificate is pre-loaded in the CPSC Product Registry.

⚠️ There is no Section 321 or de minimis exemption. Any product requiring certification needs eFiled data regardless of shipment value.

🔗 Roughly 600 HTS codes are flagged in ACE, but the flag list is a trigger, not the legal test for whether a product is in scope.

📄 CBP will not automatically reject entries for missing CPSC data, but CPSC may review, reject the CPSC data, and pursue enforcement, and your risk score is affected either way.

Where CPSC eFiling Stands Now

CPSC eFiling is the electronic submission of Certificate of Compliance data through CBP’s Automated Commercial Environment (ACE) using the CPSC Partner Government Agency (PGA) message set. The obligation is live for general entries and is a structural shift in how trade and customs compliance interacts with product safety evidence.

Two dates matter. General import entries have been covered since July 8, 2026. Covered merchandise withdrawn from an FTZ for consumption or warehousing follows on January 8, 2027, under the rule’s 24-month implementation period for FTZ goods, per the CPSC eFiling FAQ.

The practical effect is that certificate data now has to be structured, accurate, and broker-ready before a shipment arrives. For importers running many SKUs across many suppliers, small inconsistencies that once hid in back-office PDFs now appear at entry. This connects directly to product safety certification and consumer goods supply chains that rely on third-party test reports.

Step 1: Identify Regulated Products and Flagged HTS Codes

Start by confirming which products you import require a CPSC Certificate of Compliance. Children’s products require a Children’s Product Certificate (CPC); many general-use consumer products require a General Certificate of Conformity (GCC).

On January 27, 2026, CPSC published a list of approximately 600 Harmonized Tariff Schedule codes flagged in ACE, and on February 27, 2026 it released further guidance on product safety rules, citations, and testing exclusions. Use the flag list to screen your catalog, but do not treat it as the definition of scope.

⚠️ A product off the flagged list can still require a certificate, and a flagged product that is genuinely out of scope should carry a Disclaimer Message Set rather than silence. Map certification obligations against the actual safety rule, not the tariff code alone. Aligning this work with HTS classification and general import regulations reduces the chance of a misclassified SKU slipping through.

Step 2: Collect the Seven Certificate Data Elements

For products not pre-registered in the CPSC Product Registry, the Full PGA Message Set requires seven certificate data elements for each entry. These are the same facts your CPC or GCC should already contain, sourced from suppliers and testing laboratories.

Source: CPSC eFiling FAQ and the CPSC eFiling CATAIR Implementation Guide.

The failure point for most importers is not the certificate itself but the supplier and lab data behind it. A manufacture date that pre-dates the cited rule, an incomplete factory address, or a substituted sub-component tested under an old report will all surface during CPSC’s risk review. Centralizing this through streamlined supplier documentation keeps each element current and traceable to the specific product. For background on the underlying document, see Certivo’s guide to the Certificate of Conformance.

Seven certificate data elements importers must file for CPSC eFiling compliance

Click on image to view full

Step 3: Choose the Full or Reference Message Set

CPSC gives importers two ways to transmit certificate data to CBP. The right choice depends on how often you ship the same regulated products.

Both routes carry the same legal weight. The Reference method reduces per-entry data entry for high-frequency importers, which describes most private labelers and e-commerce sellers with stable catalogs. Whichever path you choose, your broker transmits the message set in ACE, so confirm your broker’s ACE PGA capability is configured and tested. Treating this as a shared responsibility across compliance, sourcing, and your broker reflects how customer and industry requirements are increasingly enforced at the point of entry.

Managing certificate data across hundreds of SKUs and suppliers in spreadsheets? Speak with a compliance specialist about keeping the seven data elements validated and audit-ready at the product level.

Step 4: Set Up the CPSC Product Registry Correctly

The Reference method depends on the CPSC Product Registry, a standalone repository for certificate data. One operational detail trips up new users: the Product Registry does not communicate automatically with CBP’s ACE system.

Once a certificate is entered and certified in the registry, you must pass the three Certificate Identifiers (Certifier ID, Product ID, Certificate Version ID) to your broker so the Reference Message Set can point to the correct record at entry. If those identifiers are wrong or stale, the reference fails even though the registry record exists. Version control matters here: when a certificate is re-issued, the Certificate Version ID changes, and the identifier handed to your broker must change with it.

Build a simple internal process so that registry updates, version changes, and broker hand-offs stay synchronized. This is where continuous, audit-ready documentation prevents a quiet mismatch from becoming a border hold.

Step 5: Prepare FTZ Inventory for January 8, 2027

If you admit goods into a Foreign Trade Zone and later enter them for consumption or warehousing, mandatory eFiling applies to those withdrawals from January 8, 2027. The grace period is short, and the clock is already running.

FTZ operators often batch entries under CBP’s weekly entry program rather than filing per shipment, so their ACE integrations need adaptation to carry the CPSC message set alongside PGA data already required by agencies such as FDA and USDA. Before the FTZ date:

✓ Inventory every CPSC-regulated SKU currently in or expected in the zone

✓ Confirm each item has complete, current certificate data tied to the specific product

✓ Decide Full or Reference per product line and register certificates where the Reference method is used

✓ Confirm your broker or FTZ operator’s ACE setup transmits the CPSC message set on withdrawal entries

✓ Reconcile manufacture and test dates for goods that have been in the zone across certificate versions

Linking this inventory to your bill of materials through BOM-level compliance tracking lets you answer “which withdrawals are not eFiling-ready” before the date arrives rather than after.

CPSC eFiling compliance timeline showing 2026 general and 2027 FTZ dates

Click on image to view full

Low-Value and De Minimis Shipments

There is no Section 321 or de minimis exemption for CPSC eFiling. If a product requires certification, its certificate data must be eFiled regardless of shipment value. For direct-to-consumer sellers moving small parcels, this closes a gap that previously let low-value consignments avoid formal entry scrutiny. Every covered finished product needs the same certificate data behind it, whether it ships by the pallet or the parcel.

Enforcement: What “No Automatic Rejection” Actually Means

CBP clarified through CSMS #69382435 that ACE will accept entries that are missing a CPSC message set or missing some CPSC data, provided the overall message set requirements are met. In other words, CBP will not automatically reject an entry solely for failure to eFile.

⚠️ That is not the same as safe. Per the same guidance, CPSC may respond with a review of the CPSC data submitted, may reject the CPSC data, and may perform enforcement actions on any entry that should have eFiling data but does not. CPSC continues to enforce certificate requirements and can request seizure of non-compliant products, as stated in the CPSC news release on mandatory eFiling. Complete, accurate filings lower an entry line’s risk profile; absent or inconsistent data raises it and concentrates holds and exams on the importers who treated the deadline as optional.

How Certivo Helps Importers Stay eFiling-Ready

Certivo does not replace your customs broker or file into ACE. It functions as the system of record that keeps the certificate data behind each entry structured, validated, and traceable, so your broker files from clean inputs and your team can answer customer and regulator questions quickly.

For CPSC eFiling specifically, that means assembling the seven data elements per product, flagging where a manufacture or test date conflicts with a cited rule, and mapping certificate obligations to products and HTS classifications across your catalog. CORA, Certivo’s AI intelligence layer, supports AI-assisted document parsing and certificate validation by reading supplier certificates and test reports and checking them against the data each entry needs. When an OEM or marketplace requests proof, faster RFQ and customer response workflows let you retrieve the current, version-correct certificate without a manual search. For the broader context on automating this kind of evidence work, see Certivo’s guide to AI tools for compliance management.

The goal is not to make any importer “audit-proof.” It is to reduce surprises at entry, shorten evidence retrieval, and keep a single, current version of the truth for every regulated SKU, including the electronics and consumer products where certificate volume is highest.

Get ahead of the January 8, 2027 FTZ date. Request a compliance risk assessment to see which of your regulated products are eFiling-ready and where the certificate data gaps are.