CPSC eFiling means sending the data from a product's certificate to CPSC electronically when a regulated consumer product is imported. It became mandatory for most regulated products on July 8, 2026. It adds no new testing: the certificate behind it was already required.
Watch the question underneath eFiling answered in under a minute: does this product need a certificate?
Real footage of the live tool; the example product shown is illustrative. Watch on YouTube →
CPSC describes it as importers electronically filing the data elements from a certificate of compliance through a partner-agency message set at entry. In plain terms, the certificate's data now reaches CPSC when the goods arrive, instead of only being produced later if CPSC asks.
The key word is data. eFiling changes how a certificate's information reaches CPSC. It doesn't change whether a certificate is needed, what it must say, or the testing behind it.
The importer of a regulated consumer product. If CPSC requires a certificate for the product you import, the filing obligation sits with you as the importer. CPSC has said eFiling doesn't apply to domestic manufacturers, including small businesses making products in the U.S.
It became mandatory for most regulated consumer products on July 8, 2026. For regulated products entered into a foreign trade zone, it applies from January 8, 2027. Pilots ran from 2016 to 2024, then a voluntary stage, so importers could practice without delaying shipments.
From January 20, 2027, CPSC will also require an eFiled certificate for regulated products that come into the U.S. by mail. CPSC first gave October 22, 2026, then moved the date in its October 2026 guidance. Low-value parcels aren't exempt, and neither are sales between two people; only a true gift is. CPSC says the importer eFiles, and it names who that can be: the owner, the buyer, the consignee or an authorized customs broker.
CPSC has said eFiling creates no new testing, certification or compliance obligation. Say your product needed a GCC before July 8, 2026. It needs the same GCC, on the same testing, now. What's new is that its data goes to CPSC electronically at entry.
So the real question for most importers sits underneath eFiling: does this product need a certificate at all, and which kind?
First, "eFiling" names two things. One is certificate data sent in a message at entry. The other is certificate data stored in the CPSC Product Registry, an account in the certifier's own name, and referenced at entry. CPSC calls both eFiling, so the only reliable way to tell them apart is to name where the data goes.
Second, whether a product needs a certificate is a question about the product. A code on CPSC's flagged list means CPSC flags that code at the border, not that every product under it needs a certificate. Some do, some fall under no certificate rule, and CPSC lets some regulated ones go without one. The list isn't complete either. The answer comes from the product's own details.
The free certificate check answers the question underneath eFiling — whether your product needs a CPSC certificate, and which kind — from the product's own attributes, not just its HTS code.
Check which certificate you need — free →Want to see what a certificate draft and its Product Registry data actually look like? See a sample →
The plan puts it in order for your product: which certificate it needs, what to ask the supplier for, and what a marketplace or customs may ask for. It's free, with no signup.
See the plan for your product →The rules on this page do change — an eFiling date, a list, a threshold. Leave an email and a short note goes out if one does: a few a year at most, one click to stop, and the address is used for nothing else. A summary of the guide and a link arrive now, as confirmation.
Information current as of 2026-10-21.
This report is an automated, informational screening tool only. Tiana & Co. is not a licensed customs broker and does not conduct customs business. This report does not constitute legal advice, a compliance determination, or a certification of admissibility for any supplier, product, or shipment.
Verdicts in this report are produced by deterministic code, not by a language model. The explanatory paragraph accompanying each check is model-generated and checked against the cited sources before delivery. No part of this report is reviewed by a person before it is issued, so every material finding and citation should be confirmed against the underlying government source before it is relied on.
This report reflects data available as of the report date. The OFAC SDN and Consolidated lists, the other U.S. Consolidated Screening List constituents, the UFLPA Entity List, CBP withhold release orders, CPSC's eFiling list, and regulatory guidance are updated frequently and without prior notice. Users should re-screen periodically and consult qualified counsel for compliance decisions.
Name-similarity results do not establish or rule out the identity of any company. Where multiple similarly named records exist, none should be treated as confirmed without independent verification against the primary government source.
This tool is not affiliated with, endorsed by, or a substitute for U.S. Customs and Border Protection, the U.S. Department of the Treasury, the Consumer Product Safety Commission, or any other government agency. No warranty is made as to the accuracy, completeness, or currency of any finding.
Use of this report for import, procurement, sanctions-compliance, or investment decisions is at the user's own risk. Anyone with compliance obligations under UFLPA, OFAC, or CPSC regulations should consult qualified legal counsel before making a transactional decision.
This report is an automated, informational screening tool only. Tiana & Co. is not a licensed customs broker and does not conduct customs business. This report does not constitute legal advice, a compliance determination, or a certification of admissibility for any supplier, product, or shipment.
Verdicts in this report are produced by deterministic code, not by a language model. The explanatory paragraph accompanying each check is model-generated and checked against the cited sources before delivery. No part of this report is reviewed by a person before it is issued, so every material finding and citation should be confirmed against the underlying government source before it is relied on.
This report reflects data available as of the report date. The OFAC SDN and Consolidated lists, the other U.S. Consolidated Screening List constituents, the UFLPA Entity List, CBP withhold release orders, CPSC's eFiling list, and regulatory guidance are updated frequently and without prior notice. Users should re-screen periodically and consult qualified counsel for compliance decisions.
Name-similarity results do not establish or rule out the identity of any company. Where multiple similarly named records exist, none should be treated as confirmed without independent verification against the primary government source.
This tool is not affiliated with, endorsed by, or a substitute for U.S. Customs and Border Protection, the U.S. Department of the Treasury, the Consumer Product Safety Commission, or any other government agency. No warranty is made as to the accuracy, completeness, or currency of any finding.
Use of this report for import, procurement, sanctions-compliance, or investment decisions is at the user's own risk. Anyone with compliance obligations under UFLPA, OFAC, or CPSC regulations should consult qualified legal counsel before making a transactional decision.