The long-anticipated rollout of the Consumer Product Safety Commission’s (CPSC) mandatory e-filing for certificate data in the Automated Commercial Environment (ACE) went live on Wednesday, July 8. This marks a significant shift in trade compliance, and the industry is actively adjusting to the new requirements.
At Sobel Network Shipping Co., Inc., we recognize that readiness levels vary across the trade community. While some importers have successfully integrated with the CPSC Product Registry, others are still navigating the onboarding process or have opted out for the time being. Consequently, customs brokers are stepping up to manually input full CPSC message sets for a large portion of their importer clients during this initial transition.
It is critical to remember that it is never too late for importers to utilize the Product Registry. We highly encourage importers to register, as leveraging the Registry is the most efficient, streamlined method for managing data compliance for all CPSC-regulated products.
To help our clients and partners navigate this new regulatory landscape, we have broken down the vital operational insights and technical requirements you need to know now:
Key Compliance & Implementation Guidelines
-
Effective Date: The e-filing mandate applies to all applicable entries filed on or after July 8, regardless of the cargo’s arrival or anticipated release date.
-
The Risk of Non-Compliance: Currently, failing to provide the required certificate data will trigger an automated warning rather than an immediate CBP rejection. However, do not mistake a warning for a pass. Missing data will negatively impact the importer’s risk score, significantly increasing the likelihood of future exam targeting, shipment holds, CPSC violations, or potential cargo seizures.
-
Strict Rules for CP2-Flagged HTS Codes: For HTS codes carrying a CP2 flag, certificate data must be transmitted via either the full message set or the reference message set. No disclaims are allowed for CP2 flags.
-
Exceptions for CP2 Transactions: If an HTS code is flagged as CP2 but the specific transaction falls outside CPSC jurisdiction (e.g., B2B transactions not intended for consumer distribution, or goods manufactured prior to the standard’s enactment), the CPSC advises brokers not to file a message set. CBP will not reject the entry, and only a warning will be generated.
-
Unique Rules for CP1 Disclaims: Unlike other Partner Government Agencies (PGAs), disclaims for CP1-flagged HTS codes are permitted but not strictly required. However, failing to file either a message set or a disclaim will damage an importer’s risk score. Therefore, filing a disclaim is highly recommended.
Note: A CP1 disclaim must include an Intended Use Code. When a disclaim is transmitted, the entry will temporarily show an “Under Review” status while the CPSC processes it.
-
Registry Alignment (IOR vs. Certifier ID): To utilize the efficient reference message set, the Importer of Record (IOR) and the certifying entity (identified by the Certifier ID) must be the same legal entity. An IOR cannot use a third-party’s Certifier ID. Importers wishing to streamline their clearances must register and obtain their own Certifier ID.
-
Citations for the Full Message Set: If you are utilizing the full message set, a specific citation code must be submitted for every applicable rule, ban, or standard governing the product. These are entered in the PG60 line item data.
The Road Ahead
This is an undeniably complex regulatory transition, and both the trade community and the agency will face teething issues in the weeks ahead. Navigating these compliance changes requires a proactive approach and a knowledgeable logistics partner.
As your trusted customs broker, Sobel is here to ensure your supply chain remains compliant, resilient, and clear of costly targeting delays. If you have questions about onboarding to the CPSC Product Registry or need assistance managing your upcoming filings, reach out to the Sobel team today.
