|
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 and guidance, 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.
|