CPSC eFiling Resource Center for U.S. Importers
Understand CPSC eFiling requirements, effective dates, covered products, Product Registry options, CSV bulk uploads, and the information importers need before filing certificate data through CBP’s Automated Commercial Environment.
This resource center connects practical guides for importers, private-label businesses, marketplace sellers, brokers, and teams responsible for preparing product certificate data. Start with applicability and filing options, then move to the Product Registry, CSV preparation, data fields, error correction, and special Foreign Trade Zone requirements.
What CPSC eFiling changes for U.S. importers
The revised certificate rule implements electronic filing of certificate information for imported finished products that must be certified under laws enforced by the U.S. Consumer Product Safety Commission. The certificate data is transmitted through CBP’s ACE system at entry using a CPSC Partner Government Agency message set.
Certificate data becomes part of the import filing workflow
If an imported finished product is subject to a CPSC rule, ban, standard, or regulation that requires certification, the applicable certificate information must be eFiled. The rule does not make every imported product certifiable; applicability still depends on the product and the regulations enforced by CPSC.
The filing party and the responsible certifier may not be the same entity
CPSC generally treats the importer as the Importer of Record eligible to make entry, which may be an owner, purchaser, or authorized customs broker. Where a broker lacks the product knowledge needed for testing and certification responsibility, the owner, purchaser, or consignee may be identified as the responsible party.
Initial ACE warnings do not remove certificate obligations
CPSC states that it does not initially intend to request entry denial solely because certificate data was not eFiled and expects warning messages rather than reject messages for missing PGA data. The agency also states that certificate requirements remain enforceable and non-compliant products may still face enforcement or seizure action.
CPSC eFiling dates importers should track
The final rule revised 16 CFR part 1110 and established separate effective dates for most covered imports and merchandise entered from a Foreign Trade Zone.
Certificates of Compliance final rule
CPSC published the final rule at 90 FR 1800. It revises the certificate regulation and implements eFiling with CBP for imported products and substances regulated by CPSC that must be certified.
Requirements take effect for most covered imported products
The main effective date applies to CPSC-regulated products and substances subject to the final rule that are required to be certified, except covered products entered from an FTZ for consumption or warehousing.
Separate deadline for merchandise entered from a Foreign Trade Zone
Covered merchandise withdrawn from an FTZ and entered for consumption or warehousing becomes subject to the eFiling effective date on January 8, 2027.
Choose between a Full PGA Message Set and a Reference PGA Message Set
Importers and their trade partners should choose the filing route that fits their product volume, certificate reuse, broker workflow, and technical systems. The Product Registry is useful for reusable certificate records, but it is not required for a Full PGA Message Set.
Provide the complete certificate data for the entry
The importer supplies the broker with the seven required certificate data elements: Product ID, Citation Codes, Manufacture Date, Manufacture Place, Product Test Date, Testing Laboratory, and Point of Contact. The broker files those elements in the CPSC PGA Message Set.
Store certificate data in the Product Registry and reference it at entry
The importer enters and certifies product certificate data in the CPSC Product Registry, then provides the broker with three Certificate Identifiers: Certifier ID, Product ID, and Version ID. This route can be useful when the same certificate is referenced across repeated imports.
Bulk upload Product Registry certificate data
CPSC provides two bulk-upload routes for Product Registry data: a CSV file or an API integration. The Product Registry is a stand-alone repository and does not automatically transmit records to CBP’s ACE system.
Practical guides for each stage of the eFiling workflow
Use these guides to move from applicability and product review to Product Registry setup, CSV preparation, field completion, upload-error correction, and special importer scenarios.
CPSC eFiling Requirements for U.S. Importers
Review the effective dates, covered imports, importer responsibilities, certificate obligations, filing routes, and practical readiness steps.
How to Use the CPSC Product Registry
Understand Business Accounts, Product Collections, certificate records, Certificate Identifiers, bulk uploads, and the Reference PGA workflow.
CPSC eFiling CSV Template: How to Prepare a Bulk Upload File
Learn how the bulk-upload template is structured, how rows relate to product certificates, and what to check before uploading.
CPSC eFiling CSV Upload Errors and How to Fix Them
Review common formatting, mapping, identifier, conditional-field, and row-level problems that can prevent a clean bulk upload.
CPSC eFiling Data Elements and CSV Field Requirements
Understand required certificate elements, identifiers, citation information, manufacturing data, testing data, laboratories, and points of contact.
Which Products Require CPSC eFiling?
Learn why eFiling depends on the product’s certification requirement and where to research applicable CPSC rules, bans, standards, and regulations.
CPSC eFiling for Amazon and Private-Label Sellers
Connect private-label product data, importer roles, testing records, certificate preparation, broker coordination, and repeat product imports.
CPSC eFiling Requirements for Foreign Trade Zones
Review the separate effective date and the entry-stage requirements for covered merchandise withdrawn from an FTZ for consumption or warehousing.
Prepare the compliance data before the entry reaches the filing stage
A clean filing process begins before CSV generation or broker transmission. Use this sequence to identify the applicable products, assemble certificate data, select the filing route, and resolve file problems early.
Confirm whether each finished product requires certification
Research the product against current CPSC rules and official guidance. Do not infer applicability from the HTS code alone.
Collect identifiers, citation, manufacturing, testing, laboratory, and contact information
Use information supported by the applicable certificate and testing records. Do not invent missing values to make a row appear complete.
Choose the Full or Reference PGA workflow
Coordinate with the importer, responsible certifier, customs broker, and technical provider before building the final data workflow.
Validate the CSV before Product Registry upload
Check headers, required fields, identifier formats, conditional dependencies, duplicate rows, and field relationships before paid generation or official upload.
Provide the correct filing data or Certificate Identifiers
For the Reference route, remember that the Product Registry does not automatically send the certificate record to ACE.
Update records when certificate data changes
Review product IDs, certificate versions, testing details, trade parties, citations, and official technical documents before reusing stored data.
Verify current requirements with CPSC, CBP, and the controlling rule
CPSC may revise guidance, templates, code lists, FAQs, and technical specifications. Always compare working files and internal procedures with the current official materials.
CPSC eFiling Resources
Official starting point for importer, broker, developer, Product Registry, FAQ, and document-library resources.
eFiling Resources for Importers
Official explanation of the Importer of Record, responsible certifier, Business Account, and related implementation resources.
Does eFiling Apply to Me?
Official applicability page linking to product rules, testing, certification, labeling, and small-business resources.
CPSC Product Registry
Official account-registration and Product Registry information, including the stand-alone repository limitation.
eFiling Document Library
Current Product Registry guide, CSV upload guide, CSV template, API specifications, code lists, FTZ guidance, and implementation materials.
Certificates of Compliance, 90 FR 1800
Final rule revising 16 CFR part 1110 and implementing electronic filing of certificate data for covered imported products.
Common questions from importers preparing for eFiling
These short answers summarize the current official framework. Product-specific applicability and certificate decisions should be verified against controlling CPSC requirements and current records.
When did CPSC eFiling become effective?
July 8, 2026 is the effective date for most covered imported products. The effective date for covered merchandise entered from an FTZ for consumption or warehousing is January 8, 2027.
Does every imported product require CPSC eFiling?
No. eFiling applies when the imported finished product is subject to a CPSC-enforced rule, ban, standard, or regulation that requires certification.
Is the CPSC Product Registry required for every filing?
No. The Product Registry supports the Reference PGA route. An importer filing a Full PGA Message Set does not need to use the Product Registry for that filing route.
Can certificate data be uploaded in bulk?
Yes. CPSC states that Product Registry users may bulk upload product certificate data through a CSV file or an API integration.
Does the Product Registry automatically send data to CBP ACE?
No. The Product Registry is a stand-alone repository. For a Reference PGA filing, the importer must provide the applicable Certifier ID, Product ID, and Version ID to the broker or filing party.
Is there a Section 321 exemption from eFiling?
No. CPSC states that a product requiring certification must have eFiled certificate data regardless of shipment value.
Can the CSV Builder determine whether a product is legally covered?
No. The tool checks and transforms information supplied by the user. It does not determine legal applicability, select citation codes, replace product testing, submit to CPSC or CBP, or guarantee acceptance.
Check product certificate data before Product Registry upload
Upload supported source files, confirm the field mapping, identify missing or inconsistent data, and prepare a CPSC Product Registry-formatted CSV from the rows that are ready.
Use current official sources for final compliance decisions
Registry Intelligence is not affiliated with, endorsed by, or operated by the U.S. Consumer Product Safety Commission or U.S. Customs and Border Protection. This page provides educational and data-preparation information, not legal advice, customs brokerage, product testing, certification, or a government filing service. Official rules, agency guidance, current technical documents, and product-specific facts remain controlling.