Quick Links
About eFiling
eFiling is a CPSC initiative under which importers of regulated consumer products will electronically file (eFile) data elements from a certificate of compliance with U.S. Customs and Border Protection (CBP), via a Partner Government Agency (PGA) Message Set.
eFiling Implementation Overview
CPSC is actively developing the eFiling program and finalizing rulemaking! Importer participants are currently testing the eFiling system and preparing for full rollout. Importers not participating in the Beta Pilot can now begin preparing for implementation! To learn more, access eFiling resources in the eFiling Document Library
For additional support, reach out to eFilingPilot@cpsc.gov
Subscribe Now
| Product Registry Frequently Asked Questions (FAQ) |
|---|
|
The Product Registry has a security feature that automatically logs out a user after 15 minutes of inactivity. Users should return to the Product Registry login page and enter their user ID and password to return to the system. |
|
Users can click “Forgot Password?” on the Product Registry login page and follow the on-screen instructions to complete the password reset process. |
|
A Business Account Administrator may submit an email request for updates to the eFiling Support Mailbox at eFilingSupport@cpsc.gov. A new feature is coming soon that will allow Business Account Administrators to update Business Account information. |
|
There are two options. Users can either type the citation in the search box and press enter or scroll through the dropdown list and select the citation(s). |
|
A Business Account Administrator must submit an email request for correction of Trade Party Data to the eFiling Support Mailbox at eFilingSupport@cpsc.gov. A new feature is coming soon that will allow Business Account and Collection Administrators to modify Trade Party contact information within the Product Registry. |
|
To correct a completed certificate that is ’certified’ by the authorized party, users must create a new Version ID, enter the correct certificate data, and submit for certification. If a certificate is not yet ‘certified,’ then it can be edited. |
|
Version IDs must be unique for the Product ID to which they apply. Once a Version ID has been used for a specific product, it cannot be used again; however, that same Version ID can be used for other certificates with different Product IDs. |
|
Use a testing exclusion code when a certificate is required for the product, but the product is not required to be tested to a specific performance requirement in a rule based on an exemption, exception, or determination in the underlying rule. More information can be found in the eFiling Beta Pilot Citation Testing Exclusion and Disclaim Guidance document found in the eFiling Document Library. Use a disclaim when no certificate is required for the product because the product is not within CPSC’s jurisdiction; is not subject to a rule, ban, standard, or regulation that requires certification; or because the Commission has issued an enforcement discretion for the product (i.e., certain refrigerators and adult wearing apparel). Instead of filing a Full or Reference Message Set, a Disclaim Message Set is filed. |
|
Users must enter the following certificate data elements for a Reference PGA Message Set: (1) Certifier ID; (2) Product ID; and (3) Version ID. Please refer to the CATAIR for additional details. |