CSMS #69382435

Information from the Consumer Product Safety Commission (CPSC) Related to CPSC’s PGA Message Set (eFiling)

· View this week in context on the trade timeline

Action requiredPGA UpdateMedium urgency
Share this messageLinkedInEmail
"Update to CSMS #69177694" The U.S. Consumer Product Safety Commission (CPSC) fully implemented its eFiling Partner Government Agency (PGA) message set requirements on July 8, 2026.  While the eFiling of CPSC certificate of compliance data is mandatory, CPSC has, per its final rule federalregister.gov/documents/2025/01/08/2024-30826/certificates-of-compliance and guidance cpsc.gov/FAQ/eFiling-Frequently-Asked-Questions-FAQ, determined that US Customs and Border Protections (CBP) Automated Commercial Environment (ACE) can accept entries that do not have a CPSC message set or entries where the CPSC message set is missing some CPSC data (as long as the overall CBP and Trade Automated Interface Requirements (CATAIR) PGA message set spec is followed). Therefore, software developers should allow their users to submit CPSC data even if the CPSC flagging requirements are not met. Although CBP will not reject the entry in the above scenarios (i.e., generate an SX message with a reject), CPSC may respond to trade in an SO message, with a review about the CPSC data submitted on the entry, including rejecting the CPSC data. REMINDER: CPSC may perform enforcement actions on any entry that does not have eFiling data attached when required. For any questions regarding this CSMS message, please contact efilingsupport@cpsc.gov.
Agencies affected
CPSC
Type
UPDATE

This week in context

This message came out the week of July 25 to July 31, 2026. See that week against the 90 days before it, with every CSMS message by subject and the trade actions behind them.

Trade timeline preview: the week of July 25 to July 31, 2026 highlighted against the 90 days beforeView this week in context on the trade timeline →