Skip to main content

eFiling – CPSC’s Modern Approach for Filing Certificate Data

eFiling hero image

About eFiling

What is eFiling?

eFiling is a CPSC initiative to enable importers of regulated consumer products to file electronically (eFile) with U.S. Customs and Border Protection (CBP) certain data elements from a certificate of compliance, via a Partner Government Agency (PGA) Message Set.

What does eFiling mean for Brokers and Importers?

  • Store product data electronically in a secure CPSC registry.
  • Multiple options for electronically filing a PGA Message Set before a shipment arrives.
  • Real-time data capture and streamlined processes allows the Trade Industry to more easily comply with U.S. Laws and Regulations.

Contact Us: 

How does Trade Industry benefit from eFiling?

Automation reduces the need for paper forms 

  • Digitizing the filing process may lead to reduced cost

Reductions in Risk Score

  • Organizations will see reductions in risk scores over time based on the amount of data provided which may result in reduced hold times, fewer exams, and reduced costs to the importer

Greater Focus on Higher Risk Products 

  • CPSC will be able to focus on higher risk shipments resulting in fewer holds to check for certificates, and may result in reduced costs to the importer
  • Holds will be performed for substantial violations as certificate data will be provided ahead of time

How does eFiling Work?

Load Certificate Data to Product Registry

  • Certificates data can be loaded to the Product Registry using an API
  • Existing certificates can be updated to accommodate new labs or test dates

Receive Unique Product ID

  • The Product Registry assigns a unique Product ID for each valid certificate
  • Product ID allows brokers to enter a short Reference Message Set

File PGA Message Set

  • PGA Message Set is filed at entry using the unique product ID

eFiling Video Library

beta pilot

Beta Pilot Kickoff Meeting

Watch CPSC and Beta Pilot participants kickoff eFiling.

product registry

Product Registry Training

Learn how to manage certificate data in the CPSC Product Registry. 

Beta Pilot Status

Beta Pilot Status & Prep Meeting

Watch this video for an update on pilot activities and to see a live walkthrough of the .CSV template for organizing certificate data for upload to the Product Registry. 

welcome meeting

Beta Pilot Participant Welcome Meeting

Watch this video to understand expectations, timing, roles, and responsibilities for eFiling preparedness and participation. 


eFiling Beta Pilot Workshop

Learn about the purpose and mechanics of eFiling certificate data in the Beta Pilot test and other associated topics. 

Explore All Multimedia
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 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 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 and Testing Exclusion Code Guidance document. 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. 

Report an unsafe product