1. What CPSC eFiling is
CPSC eFiling is the requirement that importers of consumer products regulated under the Consumer Product Safety Improvement Act (CPSIA) transmit specific certificate-of-compliance data electronically to U.S. Customs and Border Protection (CBP) at the time of entry, using the Automated Commercial Environment (ACE). Before eFiling, a certificate of compliance was a document the importer had to hold and produce to CPSC or CBP on request. Under eFiling, a defined subset of that certificate's data — the certificate identifier, the applicable rule citations, the responsible-party identity, and (for children's products) the third-party lab identification — now transmits with every covered entry as a matter of course, whether or not CBP ever asks.
The certification requirement itself is older than eFiling and traces to the Consumer Product Safety Improvement Act of 2008, Public Law 110-314, which added Section 14 to the Consumer Product Safety Act, codified at 15 U.S.C. § 2063. CPSIA was Congress's response to a wave of 2007-2008 recalls involving lead paint and small magnets in imported toys, and it rebuilt the compliance architecture around mandatory written certification, third-party testing for children's products, and lower lead limits. The full text of the Act is archived at govinfo.gov (PLAW-110publ314). The implementing certificate regulations sit at 16 CFR Part 1110, which defines exactly what a certificate must contain, how it must be issued, and how long it must be retained.
The importer of record is the party CPSIA treats as the certifying "manufacturer" for an imported product — the importer, not the foreign factory, is the one legally required to issue the certificate, because the certification carries U.S. legal liability under 15 U.S.C. § 2069 that a foreign entity outside U.S. jurisdiction cannot bear. Two certificate types exist. A General Certificate of Conformity (GCC) covers non-children's products subject to a CPSC rule; it can be based on first-party testing under a documented reasonable testing program. A Children's Product Certificate (CPC) covers products designed or intended primarily for children 12 years of age or younger, as defined at 15 U.S.C. § 2052(a)(2), and requires mandatory third-party testing by a CPSC-accepted laboratory. Getting the GCC-versus-CPC fork wrong — issuing a self-tested GCC where a third-party-tested CPC was legally required — is one of the most common and most expensive certification mistakes an importer can make, because it usually means re-testing the product from scratch at an accepted lab before it can lawfully ship.
2. The July 8, 2026 mandate
CPSC eFiling of Certificates of Compliance moved from voluntary pilot to mandatory requirement on 2026-07-08. The final rule was published at Federal Register document 2024-10462 (89 FR 41250), "Electronic Filing of Consumer Product Safety Improvement Act Certificate Data for Imported Consumer Products," published May 14, 2024. The rule gave the trade community roughly fourteen months from publication to the mandatory date, after several years of a voluntary pilot in which importers and brokers could submit eFiling data through ACE on a test basis without it being a condition of entry.
Every covered import entry for a CPSIA-regulated consumer product filed on or after 2026-07-08 must include the associated eFiling data as part of the CBP entry filing. There is no dollar-value exemption comparable to a customs de minimis threshold — a $12 imported toy and a $12,000 container of the same toy face the identical certificate-data requirement per covered entry line. Foreign Trade Zones get a longer runway: goods held in FTZ status under deferred-duty treatment do not trigger the eFiling requirement until they are withdrawn for consumption into U.S. commerce, and that FTZ-specific deadline is 2027-01-08. An FTZ operator holding eligible inventory should treat that later date as a hard planning deadline, not a permanent exemption — every unit that eventually leaves the zone for U.S. commerce needs eFiling data at the moment it does.
The rule itself does not publish a blanket enforcement-discretion period, and CBP's general practice on new Partner Government Agency (PGA) data mandates has historically leaned toward holding and correcting incomplete entries rather than categorically refusing them in the opening months — but that pattern is not a guarantee, and EntryProof has not independently confirmed a formally published grace-period policy specific to this rule. Treat the mandate as fully live from day one: verify the current enforcement posture against the live CPSC eFiling program page and the applicable CBP CSMS bulletin before assuming a data gap will only draw a warning.
3. Products requiring certificates
Any consumer product subject to a CPSC consumer product safety rule, ban, standard, or regulation requires a certificate under 15 U.S.C. § 2063. A product subject to no CPSC rule requires no certificate at all — determining the applicable-rule set is the analytical first step, and it is exactly the gap the free EntryProof readiness checker at /cpsc-efile/checker is built to close by mapping HTS classification against 40 CPSC-regulated product categories.
The children's-product fork is the widest and most consequential category split. A children's product is one designed or intended primarily for children 12 years of age or younger under 15 U.S.C. § 2052(a)(2), evaluated against the four-factor test CPSC published at 16 CFR Part 1200: the manufacturer's stated intent, the packaging and labeling, common consumer perception, and the CPSC staff's own age-determination guidelines. Every children's product requires a Children's Product Certificate with mandatory third-party testing; every other regulated product requires a General Certificate of Conformity, which can rely on first-party testing under a documented reasonable testing program for most categories.
Below that top-level fork, several specific 16 CFR parts define the bulk of general-use category coverage a US importer will actually run into:
- 16 CFR Part 1303 — the lead-in-paint rule, capping lead in surface coatings (paint, lacquer, varnish, printing ink) on children's products and consumer furniture at 90 parts per million by weight of the dried film. See the eCFR text of Part 1303 and the EntryProof lead-in-children's-products guide.
- 16 CFR Part 1501 — the small parts rule, the standardized test-cylinder method CPSC uses to identify choking, aspiration, and ingestion hazards in products intended for children under 3. See the eCFR text of Part 1501 and the EntryProof small parts testing guide.
- 16 CFR Part 1120 (§ 1120.3) — the substantial product hazard list, a rule-defined set of product categories where a matching defect supports mandatory recall and reporting action without a fresh case-by-case substantiality finding. See the eCFR text of Part 1120.
- 16 CFR Part 1262 — the magnet rule, setting size and flux-index limits for magnets and magnet sets to address the internal-injury risk if two or more small, high-powered magnets are swallowed. See the eCFR text of Part 1262.
Beyond these four, textile products fall under 16 CFR Part 303 fiber-content and flammability labeling, and every children's product also carries the permanent tracking-label requirement at 15 U.S.C. § 2063(a)(5), covered in the EntryProof Section 102 tracking labels guide. Confirming which of these rules actually apply to a specific SKU — and therefore which data elements the eFiling manifest will require — is the necessary first step before drafting any certificate.
4. What a GCC/CPC contains
Under 16 CFR § 1110.11, every General Certificate of Conformity must include seven data elements, and every Children's Product Certificate must include those same seven plus two more specific to third-party testing. Missing any required element renders the certificate defective, which is treated the same as having no certificate at all for enforcement purposes.
- Product identification — sufficient description (name, model, SKU) to uniquely identify the certified product.
- Citation to each applicable rule — every consumer product safety rule the product is certified against, cited by its regulatory reference.
- Importer or manufacturer identity — legal-entity name, full U.S. physical mailing address, and a direct telephone number. P.O. boxes are not acceptable.
- Records-custodian contact — the specific individual maintaining the underlying test records, with mailing address, email, and phone.
- Date and place of manufacture — month and year, plus city and country.
- Date and place of testing — month and year, plus city and country, for the testing that supports each cited rule.
- Third-party laboratory identification (if applicable) — name, mailing address, and telephone of any lab whose testing the certificate depends on.
For a Children's Product Certificate specifically, two additional elements are mandatory rather than conditional: identification of the CPSC-accepted third-party laboratory that performed the testing (not optional the way element 7 can be for a GCC based on first-party testing), and the date and place that third-party testing occurred. A CPC that omits either is defective even if every GCC-level element is present and accurate. The full element-by-element breakdown, including common drafting mistakes on each one, is at the EntryProof General Certificate of Conformity guide.
These same nine (or seven) data elements are the raw material the eFiling PGA message set draws from. The full certificate is not transmitted at entry — only a defined subset (certificate identifier, rule citations, responsible-party identity, and lab identification for children's products) travels with the ACE filing. The complete certificate has to exist, has to be Part-1110-compliant, and has to be retained and producible on request; eFiling is an additional transmission obligation layered on top of the certification obligation, not a replacement for it.
5. CPSC-accepted testing labs
Mandatory third-party testing on children's products, and on the specific non-children's categories enumerated at 16 CFR § 1107.2 (fireworks, cigarette lighters, and a short additional list), has to be performed at a laboratory CPSC has formally accepted — not merely accredited by a third party, but specifically accepted by CPSC for the exact test method and product scope in question. CPSC publishes and maintains the current accepted-lab list, searchable by test method and scope, at its accepted-lab search tool. Lab acceptance is not a blanket credential: a lab accepted for lead-in-substrate testing is not automatically accepted for flammability or small-parts testing, and acceptance can lapse or be scope-narrowed at CPSC's periodic reassessment. The full mechanics of lab acceptance, renewal, and how it differs from a certifying body's role are in the EntryProof CPSC-accepted testing lab reference and the companion certifying body vs testing lab guide.
The consequence of using a non-accepted lab on a children's product is severe and mechanical: the certificate is defective regardless of how rigorous the actual testing was, because the third-party testing requirement itself was not satisfied by an unaccepted lab's results. A defective CPC triggers the same prohibited-acts exposure under 15 U.S.C. § 2068 as having no certificate at all, and in practice usually forces a full re-testing cycle at a properly accepted lab before the product can lawfully be distributed — an expensive and time-consuming do-over that a five-minute lab-status check before commissioning testing would have prevented. Always verify current, scope-specific accepted status at the point testing is commissioned, not from a prior shipment's paperwork.
6. How to file via CBP ACE
The Automated Commercial Environment (ACE) is CBP's system of record for import processing — every entry summary, and every Partner Government Agency (PGA) message set riding along with it, is filed through ACE. CPSC eFiling data reaches CBP as a CPSC-specific PGA message set attached to the standard ACE entry filing. See the current CBP ACE overview and the CBP ACE PGA message-set documentation for the current technical field specification.
There are two paths for getting certificate data into that PGA message set. Certificate registry filing means the certificate has already been registered in the CPSC Product Registry system and is referenced on the entry line by its registry identifier — a short, reusable reference well suited to high-volume importers with stable, repeat SKUs. Full-data filing means the complete certificate data elements are transmitted directly on the entry line for a certificate that has not been pre-registered — the practical default for a new product, a low-volume SKU, or a one-off import where registering the certificate in advance is not worth the setup step. Both paths satisfy the eFiling requirement equally; the choice is purely an operational one about volume and SKU stability.
The step-by-step filing sequence a US importer of record actually follows looks like this. First, confirm which CPSC rules apply and which certificate type is required — the free EntryProof readiness checker does this from an HTS code and product URL in under a minute. Second, issue the certificate itself, containing every 16 CFR § 1110.11 data element, backed by first-party or CPSC-accepted third-party testing as the product category requires. Third, decide between registry filing (for a certificate you expect to reuse across repeat entries) or full-data filing (for a one-off or new SKU). Fourth, your customs broker — or your own ACE filer credentials, if you self-file — transmits the CPSC PGA message set as part of the standard entry summary submission, typically timed at or shortly before the shipment's arrival consistent with standard entry-filing timing under 19 CFR Part 141. Fifth, if CBP flags the entry for a missing or invalid element, resubmit the corrected message set promptly — see Section 7 below for what that process actually looks like. Sixth, retain the underlying certificate and testing records for a minimum of five years, because the full certificate (not just the transmitted subset) has to be producible to CPSC or CBP on request even after the entry clears.
Preparing and staging the certificate data well before the physical shipment arrives — rather than scrambling to assemble it once the container is already at port — is the single highest-leverage operational habit in this entire process. A certificate that already exists and already passed a readiness check has essentially zero incremental filing risk; a certificate assembled under time pressure at the port is where data-entry mistakes concentrate.
7. What happens after you file
A PGA message set that validates cleanly against every required field generally lets the entry proceed through ACE without manual intervention. The more instructive case — the one every importer should plan for — is what happens when it does not validate cleanly, or when CBP's own targeting flags the entry for review regardless of a clean submission.
A missing or invalid required data element is the most common trigger for a hold. In practice that surfaces as the entry being flagged for correction: the broker or self-filer resubmits a corrected PGA message set, and the entry proceeds once the resubmission validates. If the issue is identified during a physical or documentary examination rather than caught at initial submission, CBP has a statutory clock: a Notice of Detention under 19 U.S.C. § 1499(c) must issue within five business days of the examination. From that notice, the importer has 30 days to respond with evidence resolving the issue — a corrected certificate, a corrected PGA resubmission, or documentation the original filing was in fact accurate. No satisfactory response within 30 days means the shipment is deemed excluded and treated as if formally refused admission.
Clearance is not necessarily the end of the story. CBP retains post-release audit authority, and a compliance issue — including a certificate or eFiling defect — discovered after a shipment has already left CBP custody can trigger a Redelivery Notice (CBP Form 4647), demanding the importer return the merchandise. Failure to redeliver triggers liquidated damages under the importer's continuous bond, typically assessed at three times the entered value plus duty. The full mechanics of detention, redelivery, and the broader hold-to-refusal timeline — including the financial exposure of port dwell time and bonded-warehouse alternatives — are in the EntryProof CPSC import alerts & CBP hold guide.
A pattern of repeated data-quality failures across an importer's entries can also affect CBP's targeting posture on that importer's future shipments — a consequence that does not show up on any single entry's outcome but compounds over a filing history. That compounding effect is the practical argument for a pre-submission readiness check on every new SKU rather than treating ACE validation as the first and only quality gate.
8. Recall response
Filing a clean eFiling packet at entry does not end an importer's obligations on that product. Under 15 U.S.C. § 2064 (CPSA Section 15), a manufacturer, importer, distributor, or retailer that obtains information reasonably supporting the conclusion that a product contains a defect creating a substantial risk of injury, creates an unreasonable risk of serious injury or death, or fails to comply with an applicable consumer product safety rule, must immediately notify CPSC. CPSC's stated compliance benchmark for "immediately" is within 24 hours of obtaining the reportable information.
Reportable information does not require certainty, a confirmed root cause, or a completed internal investigation — it requires only that the information, viewed objectively, supports a reasonable conclusion that one of the statutory triggers is met. A single credible consumer complaint alleging an injury pattern consistent with a known defect theory, a lab result showing non-compliance, or even a competitor's recall on a functionally identical product can each independently start the 24-hour clock. The most common and most costly mistake companies make is delaying the report while an internal investigation runs to completion — CPSC's consistent enforcement position is that the investigation can continue after the report is filed, not instead of filing it.
Once a reportable event is confirmed, the corrective-action process typically runs through a negotiated corrective action plan (recall scope, remedy, and public notice terms) between the company and CPSC staff. A product in one of the enumerated 16 CFR Part 1120 substantial-product-hazard categories is presumptively reportable when it exhibits the described defect pattern, which shortens the internal debate over whether a given issue clears the reporting threshold. The full penalty exposure for getting recall response wrong — late reporting, an incomplete corrective action, or a defective underlying certificate discovered during the recall investigation — is covered in the EntryProof Section 15 penalty guide.
9. Enforcement and penalties
CPSC civil penalties are capped by statute at 15 U.S.C. § 2069(a): $120,000 for a single knowing violation and $17,150,000 for a related series of violations. Both figures were set by the Federal Register inflation adjustment at 86 FR 68244 (document 2021-26082), published December 1, 2021 and effective January 1, 2022, under the mandatory five-year adjustment schedule at 15 U.S.C. § 2069(a)(3). The next statutory adjustment is due on or before December 1, 2026 — verify the live figures before relying on these numbers for a specific exposure calculation, and see the free EntryProof penalty calculator for an interactive aggregate estimate across your product line.
These are the caps that actually apply — not a $16.875 million cap. That $16.875 million figure that circulates in some secondary compliance content is the settlement amount in the Johnson Health Tech civil-penalty case, one of the largest CPSC enforcement settlements of the last five years, not a statutory ceiling. It is real and instructive as an enforcement example (alongside Peloton's $19.065 million settlement, Clorox's $14.15 million, Shimano's $11.5 million, and Daikin's $8.5 million, all publicly reported in the Federal Register) but it should never be cited as "the cap" — the statutory ceiling is $17,150,000 per related series, and a large settlement figure like Johnson Health Tech's reflects a case CPSC treated as multiple related violations aggregated up toward, not past, that ceiling.
Every one of those largest recent settlements centered on a failure to timely report a known hazard under Section 15(b) — not a labeling or eFiling paperwork gap standing alone. That pattern matters operationally: a clean eFiling packet and a complete certificate meaningfully reduce entry-level risk, but the largest dollar exposure in this framework comes from what happens after a product is already in the field and a hazard becomes known, which is why Section 8 above is not an afterthought.
Beyond civil exposure, 15 U.S.C. § 2070 provides criminal penalties — fines and imprisonment up to five years — for a knowing and willful violation committed after the violator has received notice from CPSC of noncompliance, including knowingly certifying a product as compliant when it is not. Criminal referral is reserved for the most serious, willful cases; the overwhelming majority of certificate and eFiling defects are resolved through the civil-penalty and corrective-action framework described above, but a documented pattern of knowing false certification sits squarely inside what the criminal provision was written to reach.
10. Multi-channel filing
Every certificate and eFiling obligation in this guide attaches to whoever holds importer-of-record status on the specific customs entry — and that status shifts across sales channels in ways many sellers do not track carefully. Getting this wrong is arguably the single most common and most expensive category of mistake covered anywhere in this guide, because it means a seller can be fully compliant with a marketplace's own internal rules while every inbound shipment is exposed at the border.
Amazon FBA. On a standard Fulfilled-by-Amazon arrangement, the seller who owns the goods and initiates the import remains importer of record. Amazon Seller Central's compliance document upload is a listing-activation gate on Amazon's own platform, entirely separate from the federal customs entry — passing it does not mean a compliant eFiling packet was ever transmitted to CBP. FBA inbound shipments cross the border like any other import and can be held regardless of listing status.
Shopify DTC. A merchant importing inventory in bulk and holding it domestically before shipping to consumers is importer of record on that bulk entry. Shopify is a storefront platform with no compliance-document infrastructure comparable to Amazon's gate — the entire eFiling burden sits on the merchant with zero platform-side backstop or even a reminder.
TikTok Shop, Shein, and Temu. These marketplace-of-record models vary by fulfillment path and are the least settled area in this whole guide. Where a marketplace ships an individual parcel directly from an overseas facility to a US consumer, the marketplace or its designated logistics partner may act as importer of record for that entry. Where a seller instead uses a domestic fulfillment center — increasingly common as these platforms localize US inventory — the seller or the marketplace's domestic fulfillment entity may hold that role instead. Do not assume; confirm in writing which party is importer of record for your specific fulfillment path on each platform. The full platform-by-platform breakdown is in the EntryProof Shein, Temu & TikTok Shop CPSC compliance guide, with platform-specific detail also at /cpsc-efile/amazon, /cpsc-efile/shopify, /cpsc-efile/tiktok-shop, and /cpsc-efile/shein.
Consolidation strategy. A seller running the same product line across three or four of these channels simultaneously should not treat each channel's compliance posture independently. Issue one certificate family per genuinely identical product configuration, keep the importer-of-record determination documented per channel and per fulfillment path, and re-verify that determination whenever a platform changes its fulfillment model — which these platforms have done repeatedly as they build out domestic warehousing. The operational goal is a single source of truth for "who certifies this SKU and who is importer of record when it ships through channel X" that does not have to be reconstructed from memory every time a new channel is added.
11. Top 20 filing mistakes
Twenty mistakes we see most often across certificate, testing, and eFiling workflows, each with the fix.
- Treating a marketplace document gate as the federal filing. Fix: confirm the actual ACE PGA message set was transmitted on every entry, independent of any platform upload.
- Issuing a GCC where a CPC was required. Fix: run the 16 CFR Part 1200 four-factor children's-product test before drafting any certificate.
- Using a lab not CPSC-accepted for the specific test method. Fix: check current scope-specific acceptance at cpsc.gov/cgi-bin/labsearch before commissioning testing, not after.
- Missing rule citations on the certificate. Fix: map every applicable rule to the product before drafting, not just the most obvious one.
- Naming a records custodian who no longer works there. Fix: review and update the records-contact field on a quarterly cadence.
- Vague testing dates (a year instead of a specific month). Fix: cite the exact month and year from the underlying test report, not an approximation.
- Assuming FTZ status is a permanent eFiling exemption. Fix: track the 2027-01-08 withdrawal-for-consumption deadline explicitly.
- Filing certificate data for the first time at the port under time pressure. Fix: stage and readiness-check certificate data well before the shipment departs origin.
- Choosing full-data filing for high-volume repeat SKUs. Fix: register stable, repeat certificates in the CPSC Product Registry to cut per-entry filing friction.
- Ignoring a Notice of Detention until late in the 30-day window. Fix: respond as soon as the corrected certificate or PGA resubmission is ready, not at day 29.
- Assuming a released shipment is permanently clear. Fix: retain full certificate and testing records for at least five years in case of a post-release Redelivery Notice.
- Delaying a Section 15(b) report to finish an internal investigation first. Fix: report within 24 hours of obtaining reportable information; keep investigating after filing.
- Under-scoping what counts as "reportable information." Fix: treat a single credible complaint or a competitor recall on an identical product as a reporting trigger, not proof required.
- Grouping unrelated SKUs under one certificate to save issuance time. Fix: certify genuinely identical product families together; keep dissimilar SKUs on separate certificates.
- Not knowing who is importer of record on a given marketplace fulfillment path. Fix: get it in writing per channel, and re-verify whenever a platform changes its fulfillment model.
- Skipping third-party testing on an enumerated non-children's category. Fix: check 16 CFR § 1107.2 before assuming first-party testing is sufficient.
- Assuming a magnet or small-parts product is exempt because it's marketed to older kids. Fix: verify actual age-appropriateness in fact, not just the label, against CPSC's four-factor guidance.
- Letting lab acceptance lapse without noticing. Fix: re-verify accepted status at every re-certification cycle, not just once at onboarding.
- No documented reasonable-testing-program plan behind a first-party GCC. Fix: write and retain an actual testing plan (methods, sampling, acceptance criteria) an auditor could follow.
- Assuming EntryProof or any readiness tool guarantees CBP or CPSC acceptance. Fix: use readiness tooling to catch gaps before filing, and confirm final questions with a licensed customs broker or attorney.
12. Frequently asked questions (30+)
The following 38 questions cover what we hear most often from importers navigating CPSC eFiling. Each answer cites the primary source behind the underlying rule. If your question is not covered here, the EntryProof glossary and the methodology page cover most of the remaining vocabulary and mechanics; contact us directly for edge cases.
1. What is CPSC eFiling?
CPSC eFiling is the requirement that importers of consumer products regulated under a Consumer Product Safety Improvement Act (CPSIA) rule transmit specific certificate-of-compliance data elements electronically to U.S. Customs and Border Protection (CBP) through the Automated Commercial Environment (ACE) at the time of entry. It replaces a paper-and-on-request certificate regime with a data-at-entry regime: the certificate identifier, the applicable rule citations, the responsible-party identity, and (for children's products) the third-party lab identifier now travel with the electronic entry filing itself rather than sitting in a file cabinet until CBP asks for them. The requirement is set out in the final rule at Federal Register 2024-10462 (89 FR 41250, May 14, 2024) and became mandatory on July 8, 2026.
2. What is 16 CFR Part 1110 and how does it relate to eFiling?
16 CFR Part 1110 is the CPSC regulation that defines what a certificate of compliance (a General Certificate of Conformity or a Children's Product Certificate) must contain and how it must be issued, referenced, and retained. Section 1110.11 lists the required data elements. The eFiling mandate does not replace Part 1110 -- it adds a new transmission channel for a subset of the Part 1110 data. The underlying certificate still has to exist, still has to be complete under Part 1110, and still has to be produced to CPSC or CBP on request; eFiling is how a defined slice of that certificate's data now reaches CBP automatically at entry instead of only on demand.
3. What is the Consumer Product Safety Improvement Act (CPSIA) and why does it matter here?
The Consumer Product Safety Improvement Act of 2008, Public Law 110-314, is the statute that created the modern certification regime this guide covers. CPSIA amended the Consumer Product Safety Act to require written certificates of compliance for every regulated consumer product (Section 14, codified at 15 U.S.C. § 2063), mandated third-party testing by CPSC-accepted laboratories for children's products, lowered the lead limits that became 16 CFR Part 1303 and 15 U.S.C. § 1278a, and set the civil-penalty framework at 15 U.S.C. § 2069 that this guide's enforcement section covers. Every certificate an importer issues today, and every eFiling data element that flows from it, traces back to a CPSIA requirement.
4. What is a General Certificate of Conformity (GCC)?
A General Certificate of Conformity is the certificate a domestic manufacturer or importer issues for a non-children's consumer product to attest the product complies with every applicable CPSC consumer product safety rule. It is required under 15 U.S.C. § 2063(a)(1) and must contain the seven data elements at 16 CFR § 1110.11: product identification, the rules the product complies with, the certifying importer or manufacturer's identity and contact information, the records-custodian contact, the date and place of manufacture, the date and place of testing, and (if applicable) the third-party lab identification. See the full breakdown at the EntryProof GCC guide.
5. What is a Children's Product Certificate (CPC) and how does it differ from a GCC?
A Children's Product Certificate covers products designed or intended primarily for children 12 years of age or younger, as defined at 15 U.S.C. § 2052(a)(2). A CPC requires everything a GCC requires plus two additional elements: mandatory third-party testing by a CPSC-accepted laboratory (not the first-party reasonable-testing-program option a GCC can use) and identification of that accepted laboratory's accreditation on the certificate. The GCC-vs-CPC fork is the first analytical question every certificate program has to answer correctly, because issuing the wrong certificate type -- a self-tested GCC for a product that legally required third-party-tested CPC -- is a defective-certificate finding that can require a full re-testing cycle.
6. Who is the "importer of record" and why does that designation matter for eFiling?
The importer of record is the party responsible for the customs entry -- the one whose name appears on the CBP entry summary and who bears legal responsibility for the accuracy of the entry, including the eFiling data attached to it. Under 15 U.S.C. § 2063(a)(1), an importer of a covered product is treated as the certifying "manufacturer" for GCC and CPC purposes, meaning the importer of record (not the foreign factory) is the party legally required to issue the certificate the eFiling data is drawn from. Correctly identifying who holds importer-of-record status on a given transaction -- which gets complicated across marketplace, dropship, and platform-fulfilled sales -- is covered in Section 10 of this guide.
7. When did CPSC eFiling become mandatory?
CPSC eFiling of Certificates of Compliance became mandatory on July 8, 2026, following a multi-year voluntary pilot period and the final rule published at Federal Register 2024-10462 (89 FR 41250, May 14, 2024). Before that date, importers could submit eFiling data voluntarily through the pilot; as of that date, every covered import entry for a CPSIA-regulated consumer product must include the eFiling data as part of the CBP entry filing or the entry is subject to CBP hold and CPSC review before release.
8. What is the Foreign Trade Zone (FTZ) eFiling deadline?
Products entering U.S. commerce through a Foreign Trade Zone have a separate, later compliance deadline of January 8, 2027 for CPSC eFiling data on withdrawal from FTZ status for consumption. Goods can sit in FTZ status under deferred-duty treatment, but the eFiling data requirement attaches at the point of withdrawal into U.S. commerce, and FTZ operators and importers using zone status should treat the January 8, 2027 date as a hard planning deadline distinct from the July 8, 2026 general mandate.
9. Is CPSC eFiling currently being strictly enforced, or is there a grace period?
The July 8, 2026 mandate carries no published blanket exemption or formal enforcement-discretion window in the final rule itself, and CBP's general practice on new Partner Government Agency (PGA) data requirements has historically included an initial period where entries with data gaps are more often held for correction than categorically refused. That said, EntryProof has not independently confirmed a specific published "warning-only" enforcement posture for this rule, and CBP's day-to-day practice can and does tighten without a formal notice. Do not assume leniency: verify current enforcement posture against the live CPSC eFiling program page and the most recent CBP CSMS bulletin before shipping on the assumption that a gap will only draw a warning.
10. Which products require a certificate at all?
Any consumer product subject to a CPSC consumer product safety rule, ban, standard, or regulation requires a certificate under 15 U.S.C. § 2063. That sweeps in toys and juvenile products (16 CFR Part 1200 children's-product rules, ASTM F963 toy standard), any product with painted or coated surfaces (16 CFR Part 1303 lead-in-paint), any product with small detachable parts marketed to young children (16 CFR Part 1501 small parts / choking hazard), products containing high-powered magnets (16 CFR Part 1262), textiles (16 CFR Part 303 flammability and fiber content), and the broader substantial-product-hazard category list at 16 CFR Part 1120. A product subject to no CPSC rule at all requires no certificate -- but confirming that negative is itself the first compliance step, and the free EntryProof readiness checker maps HTS classification to the applicable rule set for exactly this purpose.
11. What is 16 CFR Part 1303 and does it apply to my product?
16 CFR Part 1303 is the CPSC ban on lead-containing paint and similar surface coatings. It caps lead content in any surface coating -- paint, lacquer, varnish, printing ink, enamel -- at 0.009 percent (90 parts per million) by weight of the dried coating. It applies to any surface coating on a children's product and to surface coatings on furniture articles for consumer use, and separately to paint products themselves sold to consumers. It is distinct from the 100 ppm total-lead-content substrate limit at 15 U.S.C. § 1278a, which covers the underlying material rather than the coating; a painted children's product generally has to pass both limits.
12. What is 16 CFR Part 1501 (the small parts rule)?
16 CFR Part 1501 sets the small parts test method CPSC uses to identify choking, aspiration, and ingestion hazards in toys and other articles intended for children under 3 years of age. A component that fits entirely within the standardized small-parts test cylinder is a regulated small part, and products intended for the under-3 age range generally cannot include small parts that could detach during normal use and abuse testing. Products correctly labeled and marketed for children 3 and older are not covered by the same restriction, which is why accurate age-grading is a load-bearing compliance decision, not a marketing afterthought.
13. What is the 16 CFR Part 1120 substantial product hazard list?
16 CFR Part 1120 (in particular § 1120.3) lists specific categories of consumer products that CPSC has determined, by rule, present a substantial product hazard when they contain specific defects -- meaning a defect in one of the listed categories can support a mandatory recall and reporting action without CPSC having to prove the substantial-hazard finding from scratch on a case-by-case basis. Importers of products in a listed category should treat any defect matching the rule's described hazard pattern as presumptively reportable under the 24-hour Section 15(b) duty covered in Section 8 of this guide, rather than waiting to independently evaluate substantiality.
14. What is 16 CFR Part 1262 (the magnet rule)?
16 CFR Part 1262 is the CPSC safety standard for magnets and magnet sets, addressing the ingestion-hazard risk of small, high-flux magnets that can cause serious internal injury if two or more are swallowed. The rule sets size and flux-index limits and, for certain products, requires warning labeling. Importers of any product containing loose or separable small magnets -- building-set toys, fidget products, jewelry with magnetic clasps -- should confirm applicability against the current rule text at eCFR before finalizing a GCC or CPC, because the flux-index calculation is technical and a lab-run test is the reliable way to confirm compliance.
15. What is CPSC-accepted third-party testing and when is it required?
Third-party testing means the compliance test underlying a certificate is performed by an independent laboratory that CPSC has formally accepted for the specific test method and product category, rather than by the manufacturer or importer itself. It is mandatory for all children's products (which require a CPC) and for a defined list of non-children's-product categories enumerated at 16 CFR § 1107.2 (including fireworks and cigarette lighters). For every other non-children's category, a documented first-party reasonable testing program under 16 CFR § 1107.10 is an acceptable alternative basis for a GCC.
16. Where do I find the current list of CPSC-accepted testing labs?
CPSC publishes and maintains the current list of accepted third-party laboratories, searchable by test method and product scope, through the accepted-lab search tool at cpsc.gov/cgi-bin/labsearch. Lab acceptance is method-specific and scope-specific -- a lab accepted for lead-in-substrate testing is not automatically accepted for flammability testing -- so verify the specific accepted scope for the specific test your product needs, not just that the lab appears on the list at all.
17. What happens if I use a lab that is not CPSC-accepted for a children's product?
A children's-product certificate that relies on testing from a laboratory not CPSC-accepted for the specific test method and scope is a defective certificate -- the third-party testing requirement is not satisfied, regardless of how rigorous the actual testing was. A defective CPC exposes the importer to the same prohibited-acts and civil-penalty framework as a missing certificate under 15 U.S.C. §§ 2068 and 2069, and typically triggers a full re-testing requirement at a properly accepted lab before the product can lawfully be distributed. Always confirm current accepted status -- not historical status -- at the point testing is commissioned, because lab acceptance can lapse or be scope-narrowed.
18. What is the CPSC-accepted-lab renewal cycle?
CPSC lab acceptance is not indefinite; accepted laboratories undergo periodic reassessment and their accepted scope (which test methods, which product categories) can change over the acceptance period. An importer relying on a specific lab's accepted status for a recurring testing relationship should re-verify that status on a regular cadence -- at minimum before every re-certification cycle -- rather than assuming a lab's acceptance from an earlier shipment still covers the current one.
19. What is the CBP Automated Commercial Environment (ACE) and how does eFiling data reach it?
ACE is the CBP system of record for import and export processing -- the platform through which every entry summary, and every Partner Government Agency (PGA) message set attached to an entry, is filed. CPSC eFiling data travels to CBP as a CPSC-specific PGA message set within the ACE entry filing, submitted by the filer (customs broker or self-filing importer) alongside the standard entry-summary data. See the current CBP ACE PGA message-set documentation for the technical field specification.
20. What is the difference between certificate registry filing and full-data filing in the ACE PGA message set?
The CPSC PGA message set supports referencing a certificate that has already been registered in the CPSC Product Registry system by its registry identifier (a shorter, reusable reference for repeat SKUs), or transmitting the full certificate data elements directly on the entry line for a certificate not yet registered. Registry-based filing is more efficient for high-volume repeat importers with stable SKUs; full-data filing is the fallback path for a new or low-volume product where registering the certificate in advance is not worth the setup step. Both paths satisfy the eFiling requirement; the choice is an operational one about volume and repeat-SKU stability.
21. Do I have to eFile before the shipment arrives, or can I file with the entry?
The eFiling data is submitted as part of the entry filing process itself -- it can be prepared and staged in advance (which is the recommended practice, since it lets a customs broker or self-filer catch a missing data element before the shipment is at the port) but the operative filing event is the entry submission through ACE, which typically happens at or shortly before arrival, consistent with standard entry-filing timing under 19 CFR Part 141. Filing the certificate data days or weeks in advance of the physical shipment, where the underlying certificate already exists, materially reduces the risk of a last-minute hold.
22. What happens if my eFiling submission is missing a required data element?
A PGA message set with a missing or invalid required data element is the most common trigger for an entry to be flagged for CPSC or CBP review rather than releasing automatically. In practice this surfaces as an entry hold pending correction: the filer resubmits the corrected PGA message set, and the entry proceeds once the resubmission passes validation. A pattern of repeated data-quality failures on the same importer's entries can escalate CBP's targeting scrutiny on that importer's future shipments, which is the operational reason to run a pre-submission readiness check rather than relying on ACE's validation to catch problems after the fact.
23. What is a CBP Notice of Detention and how does it interact with an eFiling gap?
A Notice of Detention under 19 U.S.C. § 1499(c) is a formal CBP notice that must issue within five business days of an examination that identifies a compliance problem, including an eFiling or certificate defect. The importer then has 30 days from the detention notice to respond with evidence resolving the issue -- typically a corrected certificate, a corrected PGA resubmission, or documentation the original data was in fact correct. If no satisfactory response arrives within 30 days, the shipment is deemed excluded and treated as if formally refused admission.
24. What is a CBP Redelivery Notice and how could it apply to a CPSC issue?
A Redelivery Notice (CBP Form 4647) is issued after cargo has already cleared and left CBP custody, demanding the importer return the merchandise because a compliance problem -- including a certificate or eFiling defect discovered after release -- was identified post-entry. Failure to redeliver triggers liquidated damages under the importer's continuous bond, typically assessed at three times the entered value plus duty. A Redelivery Notice is the reason a clean initial entry does not fully retire eFiling and certificate risk on a shipment; CPSC and CBP retain post-release audit authority.
25. What are my duties if a product I already filed on is later recalled?
Under 15 U.S.C. § 2064, a manufacturer, importer, distributor, or retailer that obtains information reasonably supporting the conclusion that a product contains a defect creating a substantial risk of injury, creates an unreasonable risk of serious injury or death, or fails to comply with an applicable consumer product safety rule, must immediately notify CPSC. CPSC's stated compliance benchmark for "immediately" is within 24 hours of obtaining the reportable information -- delay materially undermines the good-faith case for any subsequent penalty mitigation. See the EntryProof Section 15 penalty guide for the full reporting and corrective-action framework.
26. What counts as "reportable information" that starts the 24-hour clock?
Reportable information is information that, viewed objectively, supports a reasonable conclusion that one of the four statutory triggers under 15 U.S.C. § 2064(b) is met -- it does not require certainty, a confirmed root cause, or a completed internal investigation. A single credible consumer complaint alleging an injury pattern consistent with a known defect theory, a lab test result showing non-compliance, or a competitor recall on a functionally identical product can each independently start the clock. Companies frequently over-delay reporting while completing an internal investigation; CPSC's consistent enforcement position is that investigation can continue after the report is filed, not instead of filing it.
27. What are the current CPSC civil penalty caps?
Under 15 U.S.C. § 2069(a), CPSC civil penalties are capped at $120,000 per single knowing violation and $17,150,000 for any related series of violations. Both figures were set by the Federal Register inflation adjustment at 86 FR 68244 (document 2021-26082), published December 1, 2021 and effective January 1, 2022, pursuant to the mandatory five-year adjustment schedule at 15 U.S.C. § 2069(a)(3). The next statutory adjustment is due on or before December 1, 2026 -- verify the current figures against the live CPSC or Federal Register posting before relying on these numbers for a specific exposure calculation, and see the free EntryProof penalty calculator for an interactive aggregate-exposure estimate.
28. Is there criminal exposure for a knowing eFiling or certificate violation?
Yes. 15 U.S.C. § 2070 provides criminal penalties -- fines and imprisonment of up to five years -- for a knowing and willful violation of the Consumer Product Safety Act after having received notice from CPSC of noncompliance, including knowingly certifying a product as compliant when it is not. Criminal referral is reserved for the most serious, willful cases; the large majority of eFiling and certificate defects are handled through the civil-penalty and corrective-action framework, but a pattern of knowing false certification is squarely inside the criminal exposure the statute was written to reach.
29. Who is the importer of record on an Amazon FBA shipment?
On a standard Amazon FBA (Fulfilled by Amazon) arrangement, the seller who owns the goods and initiates the import remains the importer of record for CBP purposes -- Amazon's Seller Central compliance-document upload gate is a separate listing requirement from the federal customs entry, and passing it does not substitute for a properly eFiled certificate on the actual CBP entry. FBA inbound shipments cross the border like any other import and can be held at port regardless of Amazon listing status if the eFiling data is missing or defective.
30. Who is the importer of record on a Shopify direct-to-consumer (DTC) shipment?
On a typical Shopify DTC model where the merchant imports inventory in bulk and holds it domestically before shipping to consumers, the merchant is the importer of record on the bulk import entry, and the certificate and eFiling obligations attach there. Shopify itself is a storefront platform, not an importer or a customs filer, and provides no compliance-document infrastructure comparable to Amazon's Seller Central gate -- the full weight of eFiling readiness sits on the merchant with no platform-side backstop.
31. Who is the importer of record on TikTok Shop, Shein, and Temu transactions?
This varies by fulfillment model and is one of the most consequential compliance questions in cross-border e-commerce today. Where a marketplace ships an individual parcel directly from an overseas warehouse to a U.S. consumer under a low-value or de minimis-adjacent entry process, the marketplace or its designated logistics partner may act as importer of record for that specific entry. Where a seller uses a domestic fulfillment center (increasingly common as marketplaces localize U.S. inventory), the seller or the marketplace's domestic fulfillment entity may hold that role instead. The practical rule: do not assume the platform's import process handles your CPSC certificate obligation -- confirm, in writing, which party is importer of record for your specific fulfillment path, and see the EntryProof Shein/Temu/TikTok Shop compliance guide for the platform-by-platform breakdown.
32. What is the single most consequential filing mistake importers make?
Treating a marketplace's internal compliance-document upload (Amazon Seller Central, or an equivalent gate on another platform) as equivalent to a completed CPSC eFiling obligation. The two systems are unconnected: one governs whether a listing can go live on that specific marketplace, the other governs whether a specific customs entry clears CBP. A seller can be fully compliant with a marketplace's upload gate and still have every inbound shipment held at port because the actual ACE PGA message set was never transmitted or was incomplete.
33. Do I need a licensed customs broker to eFile CPSC certificate data?
Most importers use a licensed customs broker to prepare and transmit the ACE entry filing, including the CPSC PGA message set, because filing a customs entry is "transacting customs business" under 19 CFR Part 111 and brokers carry the ACE-filer credentials and workflow tooling most importers do not maintain in-house. Self-filing is legally available to an importer of record for its own entries without a broker license, but is operationally rare below a certain shipment volume given the ACE technical integration required.
34. How much does EntryProof cost and what does it actually do?
EntryProof Solo is $79/month (14-day trial, up to 25 SKUs) and EntryProof Growth is $199/month (unlimited SKUs, weekly monitoring). EntryProof Founding is a $499/year rate limited to the first five founding customers, held for as long as membership stays continuous. EntryProof is a data preparation and readiness-assessment tool: it maps your HTS classification to the applicable CPSC rule set, checks your certificate and eFiling data for the required elements before you submit, and flags gaps -- missing lab accreditation, missing rule citations, incomplete data fields -- while there is still time to fix them before a container is held.
35. Is EntryProof a licensed customs broker or a substitute for legal advice?
No. EntryProof is a data preparation and readiness-assessment tool for the CPSC Product Registry. It is not a licensed customs broker under 19 CFR Part 111, not a testing laboratory, not a filer of record, and not a legal-advice service. EntryProof does not guarantee that any classification, packet, or filing will be accepted by CPSC or CBP. Compliance decisions remain the importer's responsibility; consult a licensed customs broker or an attorney experienced in Consumer Product Safety Act compliance for a specific product or entry.
36. How long must I retain GCC/CPC and eFiling records?
CPSC recommends, and enforcement practice supports, retaining certificates and the underlying test records for a minimum of five years from the last date of manufacture or importation of the covered product. There is no shorter statutory floor; the five-year period accommodates the typical enforcement lookback window. Products with a long expected field life -- durable goods, juvenile hardware -- are more defensibly retained for the product's field life plus a margin, given the low incremental storage cost against the reconstruction cost of answering a records request years later.
37. Can one certificate and one eFiling record cover multiple SKUs?
Yes, provided every covered SKU is subject to the identical set of applicable rules and was tested under a program that supports the certification for each one. Grouping unrelated SKUs under one certificate to save issuance effort creates a shared-fate risk: if one SKU in the group is later found non-compliant, the certification basis for the entire group is called into question, which is a worse outcome than the modest added effort of issuing certificates along genuinely identical product-family lines.
38. What is the fastest way to check whether my products are eFiling-ready today?
Run your product URL and HTS code through the free EntryProof readiness checker at /cpsc-efile, which scans the live product listing for the signals CPSC and CBP look for (age-grading language, lab accreditation reference, manufacturer information, certificate or CFR reference, applicable warning language) and cross-references your HTS code against the applicable CPSIA rule set to produce a specific gap list -- not a generic compliance lecture.
13. Related EntryProof resources
The following 32 spokes cover every adjacent workflow, tool, and reference this pillar touches. Every link is a live /cpsc-efile/* route, maintained against the same primary-source standard as this pillar.
14. Get expert help
Three ways EntryProof can help you close the readiness gap and manage ongoing eFiling risk. All three are priced transparently and none require a sales call.
Paste your product URL and HTS code; see the specific eFiling gap list against your applicable CPSC rules.
Open the readiness checker →14-day trial, up to 25 SKUs. Certificate and eFiling-data readiness checks before you ship.
Unlimited SKUs, weekly monitoring, 60-second scan SLA for higher-volume importers.
Founding rate held for as long as membership stays continuous, limited to the first 5 customers.
Primary sources and references
Every substantive claim in this pillar is verifiable against a primary source. The core citations are as follows.
- Consumer Product Safety Improvement Act of 2008, Public Law 110-314, full text at govinfo.gov.
- Certificate-of-conformity requirement at 15 U.S.C. § 2063.
- Children's-product definition at 15 U.S.C. § 2052.
- Section 15(b) hazard-reporting duty at 15 U.S.C. § 2064.
- Prohibited acts at 15 U.S.C. § 2068 and civil-penalty framework at 15 U.S.C. § 2069.
- Criminal-penalty provision at 15 U.S.C. § 2070.
- Certificate content and retention requirements at 16 CFR Part 1110, including the seven required data elements at § 1110.11.
- Third-party testing categories and reasonable-testing-program requirements at 16 CFR Part 1107.
- Children's-product four-factor determination guidance at 16 CFR Part 1200.
- Lead-in-paint surface-coating rule at 16 CFR Part 1303.
- Small parts test method at 16 CFR Part 1501.
- Substantial product hazard list at 16 CFR Part 1120.
- Magnet safety standard at 16 CFR Part 1262.
- CPSC eFiling final rule, Federal Register 2024-10462 (89 FR 41250, May 14, 2024).
- CPSC eFiling program page at cpsc.gov/eFiling.
- CPSC-accepted third-party laboratory search at cpsc.gov/cgi-bin/labsearch.
- CBP Automated Commercial Environment overview at cbp.gov/trade/ace and PGA message-set documentation at cbp.gov/trade/ace/pga-message-set.
- Entry-filing procedures at 19 CFR Part 141.
- Notice of Detention statute at 19 U.S.C. § 1499.
- Civil-penalty inflation adjustment, Federal Register document 2021-26082 (86 FR 68244, December 1, 2021).
Editorial notes and citation policy
This pillar is maintained by the Digital Empire Regulatory Research Team, published by Digital Empire Holdings LLC, and covers the current US CPSC eFiling framework as of the publication date. State consumer-protection channels, non-US import compliance frameworks, and tariff or duty questions (covered separately at TariffWatch) are out of scope except where specifically noted. Every claim is cited to a primary source. Corrections are posted to /corrections within one business day of confirmation.
Nothing on this page is legal advice or customs classification advice under 19 CFR Part 111. EntryProof is a data preparation and readiness-assessment tool, not a licensed customs broker, not a testing laboratory, and not a filer of record. EntryProof is a data preparation and readiness-assessment tool for the CPSC Product Registry. EntryProof is NOT a customs broker, NOT a testing laboratory, and NOT a legal-advice service. Compliance decisions remain the responsibility of the importer. EntryProof does not guarantee that any classification, packet, or filing will be accepted by CPSC or CBP. Verify every regulatory citation against the linked primary source and consult your customs broker or trade attorney before making import decisions on the basis of any content in this guide. Attorney review of this pillar is pending as of publication; this guide is a v0 disclosure.