CPSC eFiling in ACE: certificates are mandatory even when ACE does not reject

CPSC fully implemented its eFiling Partner Government Agency (PGA) message set requirements on July 8, 2026. CSMS #69382435 (July 29, 2026 update to CSMS #69177694) is the filing-ops reminder that matters: certificate data is mandatory, but ACE may still accept an entry that is missing the CPSC message set or some CPSC data elements.

That split creates a false comfort path. No SX reject from CBP does not mean CPSC is satisfied. CPSC can still answer with SO messages and can still enforce against entries that lack required eFiling data.

Mandatory CPSC certificate eFiling does not always produce an ACE SX reject. Missing data can clear CBP and still draw CPSC SO review or enforcement.

What CSMS #69382435 changes in practice

Per CPSC's final rule and guidance, as restated in the CSMS, ACE can accept:

• Entries with no CPSC message set at all
• Entries where the CPSC message set is present but missing some CPSC data
• Provided the overall CATAIR PGA message set specification is followed

CBP will not generate an SX reject message solely for those CPSC-data gaps. Software developers are told to allow users to submit CPSC data even when CPSC flagging requirements are not met. Blocking the transmit button because an internal flag check failed is the wrong product behavior under this CSMS.

SO messages and enforcement

When CPSC reviews the CPSC data on an entry (including rejecting that CPSC data), trade may see an SO message. Separately, the CSMS reminder is blunt: CPSC may perform enforcement actions on any entry that does not have eFiling data attached when required. ACE acceptance is not a CPSC clean bill.

What stays on the certificate (Quick Start context)

CPSC's eFiling Quick Start Guide (v1.1) frames eFiling as changing how certificate data is managed, not which products need a Certificate of Compliance (required since 2008). Regulated consumer products still need a certificate; importers transmit Message Set data into ACE at entry. Full PGA Message Set and Reference PGA Message Set (Product Registry) are the two filing patterns. Domestically manufactured products should not be eFiled. FTZ-related eFiling timing in the Guide points to a later January 8, 2027 tranche for goods entered from an FTZ for consumption or warehousing; the July 8, 2026 date is the main import implementation.

Broker and software checklist

• 1. Confirm July 8, 2026 eFiling coverage for the regulated consumer products on the entry.
• 2. Do not hard-block ACE transmits solely because internal CPSC flagging checks fail; allow submission of available CPSC data per the CSMS.
• 3. Monitor for CPSC SO responses and treat missing required eFiling data as an enforcement-risk item even when ACE accepted the entry.
• 4. Route product/certificate questions to efilingsupport@cpsc.gov (CSMS contact).

This article is for general information and is not legal or tax advice. Drawback eligibility depends on your specific facts, and final refunds are determined by CBP at liquidation. Consult a licensed customs broker or attorney for your situation.