What Is CPSC eFiling and What Is It Used For? Requirements, Timing, and Covered Products

CPSC eFiling is the electronic submission of certain certificate-of-compliance data to U.S. Customs and Border Protection (CBP) through ACE, using a Partner Government Agency (PGA) Message Set. In practice, it is used by importers of regulated consumer products to transmit compliance information at the time of entry rather than waiting to produce the certificate later on request.

The program is designed to help the Consumer Product Safety Commission (CPSC) identify higher-risk imports more efficiently while reducing unnecessary inspections and delays for compliant shipments. It does not replace the underlying product safety obligations; it changes how certificate data is filed and shared with customs authorities.

If you want a broader overview of how import compliance systems fit together, you may also find our guide to CBP compliance platforms for importers useful.

What CPSC eFiling Is and Why It Exists

CPSC eFiling is the mechanism CPSC uses to receive certificate data electronically for regulated consumer products imported into the United States. According to CPSC’s own eFiling program information, the system is a modern way of filing certificate data, and it is built around electronic data transmission through ACE rather than paper handling or ad hoc document production.

The CPSC’s broader mission is consumer product safety. eFiling is one tool that supports that mission by giving the agency structured data earlier in the import process. That allows the agency to focus enforcement resources on shipments that present a greater safety concern while helping compliant importers move goods with less friction.

In other words, the purpose of CPSC itself is much broader than eFiling: the agency sets and enforces product safety rules. eFiling is simply the filing method used for certain regulated imports.

What eFiling is not

It is important not to confuse eFiling with a full replacement for compliance documentation. The system is about transmitting certain data elements from a certificate of compliance. It is not a shortcut that removes the need to have the proper certificate in place, and it is not the same thing as uploading a PDF and moving on.

For importers, that distinction matters. The underlying compliance obligation still exists, and the data filed through ACE has to reflect the correct certificate information for the product being entered.

Who Must File CPSC eFiling and What They Need to Submit

The party responsible for CPSC eFiling is the importer of regulated consumer products. In operational terms, that means the importer must ensure the required compliance data is submitted to CBP at the time of entry, either directly or by using a product registry workflow where supported.

CPSC’s rollout materials and importer guidance frame eFiling as an importer-facing process. That means responsibility does not sit with the regulator in the abstract; it sits with the business bringing the covered product into the United States and managing the customs entry.

What importers need to do

At a high level, importers need to be ready to do three things:

• Identify whether the product is subject to CPSC certification requirements.
• Provide the required certificate data elements electronically through ACE.
• Maintain operational readiness so filings can be made at the time of entry, not after the fact.

In some cases, importers may also self-register for the program and prepare their data in the CPSC Product Registry. That setup step is part of getting ready for eFiling, but the evidence supports it as a readiness measure rather than a detailed onboarding tutorial.

The important practical point is this: compliance depends on the quality and availability of the underlying certificate data, not simply on having access to a portal.

What Products Require CPSC eFiling?

CPSC eFiling does not apply to every imported item. The supported rule-based criterion is whether the product is already subject to CPSC certification requirements. In other words, the covered universe is made up of regulated consumer products that already require a Certificate of Compliance.

That includes products that use the two common certificate types discussed in the sources:

• Children’s Product Certificates (CPCs) for children’s products.
• General Certificates of Conformity (GCCs) for regulated general-use products.

So, when importers ask for a “CPSC eFiling product list,” the safest answer is not a blanket list of every possible item. The real test is whether the product is subject to CPSC regulations and certification requirements. If it is, eFiling may apply. If it is not, eFiling does not automatically apply just because the item has an HTS code that appears on a screening list.

How HTS codes fit into scope determination

HTS codes are part of the screening and operational context, but they are not the only determinant of coverage based on the evidence available here. The sources indicate that CPSC uses HTS-code-based screening in ACE and has issued guidance around HTS codes for electronic certificates, but the product’s regulatory status remains the key issue.

That means importers should treat the HTS code as a starting point for identifying whether a shipment may trigger CPSC review, then confirm whether the product is actually subject to a CPSC certificate requirement.

What about repeated shipments?

For importers that repeatedly bring in the same product or product family, the eFiling workflow can be simplified by storing and managing certificate data in the CPSC Product Registry and using reference data for future shipments. That is especially helpful where the same certificate details would otherwise need to be re-entered shipment after shipment.

What the CPSC Product Registry Is and When to Use It

The CPSC Product Registry is a secure online application where importers can store and manage their product certificate data. It is designed to support transmission of Reference PGA Message information, which can reduce repetitive entry of the same certificate data for the same products.

Think of the registry as an operational data tool, not a compliance substitute. It helps importers organize and transmit the information they already need for covered products, but it does not remove the need to have compliant certificate data in the first place.

When the registry is most useful

The registry is especially helpful when you:

• Import the same regulated product repeatedly.
• Need a consistent place to store certificate data.
• Want to reduce manual re-entry of the same information across multiple entries.
• Need to support a more structured ACE/PGA workflow.

If your operation only imports a covered product once in a while, you may still need eFiling, but the registry’s operational value is usually greater for recurring shipments and product lines that are stable over time.

When CPSC eFiling Became Mandatory

The main mandatory date for CPSC eFiling is July 8, 2026 for most regulated consumer product imports. That is the date when the program moved from voluntary readiness and self-registration into mandatory use for the covered import set.

There is also a separate timing rule for products imported into Foreign Trade Zones (FTZs). For consumer products imported into an FTZ and later entered for consumption or warehousing, the requirement takes effect on January 8, 2027.

Those dates should not be collapsed into a single universal deadline. The general import rollout and the FTZ applicability date are related, but they are not the same.

Was there a voluntary period first?

Yes. The supported sources indicate that CPSC opened self-registration and allowed a voluntary implementation period before the mandatory date. That voluntary period helped importers test systems and prepare for the transition to mandatory eFiling.

For importers, that matters because the deadline was not just a policy announcement. It was preceded by a period intended to support operational readiness, which is now especially important for businesses still adjusting their customs workflows.

What Information Is Filed in CPSC eFiling

At a practical level, CPSC eFiling is a data submission process. Certain data elements from a certificate of compliance are transmitted electronically to CBP through ACE via a PGA Message Set. The filing is tied to the certificate data for the regulated product, rather than being a generic product record.

The sources consistently describe the workflow in one of two ways:

• Submit the required certificate data directly with each entry.
• Store and manage the certificate data in the Product Registry and transmit reference information for later shipments.

What you should not assume is that eFiling is merely a document upload process. It is better understood as a structured data transmission that feeds customs and regulatory review.

Why this matters for import operations

Because the filing is data-driven, importers need their compliance and logistics processes to line up. That means the product classification, certificate status, entry timing, and filing workflow all need to be aligned before cargo arrives for entry.

In practice, many companies handle this through customs brokers, compliance teams, or integrated trade systems that can support ACE and PGA workflows. The important thing is that the business has a reliable process for getting correct data into the system on time.

CPSC eFiling Exceptions and Important Limits

One important limitation in the CPSC FAQ is the treatment of used products. The cited FAQ states that eFiling does not apply to used products that were manufactured before a CPSC rule, ban, or standard went into effect.

That is a meaningful exception, and it shows why importers should not assume eFiling is universal for every consumer product entry. Coverage depends on the product, its compliance status, and the applicable rule framework.

You should also be careful not to overstate the scope of any HTS-based list. Some goods may be screened through ACE by code, but the product still needs to fit the regulatory criteria for CPSC certification before eFiling obligations are triggered.

Likewise, timing can differ by entry type. The FTZ rule is an example of a separate applicability date rather than a simple extension of the general rollout.

How Importers Should Prepare

If you import regulated consumer products, the most practical way to prepare for CPSC eFiling is to treat it as an entry-process change, not merely a legal update. That means reviewing products, certificates, broker workflows, and internal ownership together.

• Check whether your products already require CPCs or GCCs.
• Confirm whether the product falls within CPSC certification scope.
• Map your entry workflow to ACE/PGA filing requirements.
• Decide whether you will file directly or use the Product Registry for repeated products.
• Make sure your compliance data is available before the shipment reaches entry.

For many importers, the biggest challenge is not understanding the basic rule. It is making sure the data exists in the right format, is accurate, and is available in time for the customs entry process.

Bottom Line

CPSC eFiling is the electronic filing of certain certificate-of-compliance data to CBP through ACE. It is used to support the CPSC’s safety mission by improving risk targeting while giving compliant importers a more structured way to submit required certificate data at entry.

The main mandatory date for most imports was July 8, 2026, with a later January 8, 2027 date for relevant FTZ entries. The system applies to regulated consumer products that already require CPSC certification, such as products covered by CPC or GCC obligations, and the Product Registry can help manage repeated filings for the same goods.

For official program details and current guidance, see the CPSC’s own eFiling program page, the CPSC Product Registry, and the CPSC’s mandatory eFiling news release. For an importer-focused explanation of the program and rollout, you can also review the practical summary from Anderinger.

---