United States · CPSC buyer brief

CPSC eFiling Effective July 2026: Buyer Brief

eFiling changes how covered certificate data reaches CPSC and CBP; it does not turn every product into a certified product. Start with exact SKU scope, then build certificate data that can survive model, factory, laboratory, and shipment matching.

Effective
July 8, 2026 for covered imported products generally; January 8, 2027 for covered products entered from an FTZ for consumption or warehousing.
Current
As of July 14, 2026, mandatory eFiling is active for importers of finished consumer products already subject to CPSC certification requirements.
Date-sensitive
CPSC implementation documents and code lists can change. Track the January 8, 2027 FTZ phase and recheck the current Document Library before filing.

Review control: this brief can become stale when an agency changes guidance, implementation, or tariff treatment.

Last reviewed
Next review
October 8, 2026 — 90-day implementation check; earlier if CPSC updates filing guidance

What changed

General implementation is active
CPSC states that, beginning July 8, 2026, importers of consumer products subject to CPSC certification requirements must electronically file certificate data with CBP through a Partner Government Agency Message Set.
It does not create universal certification
The filing rule does not make every consumer product certifiable and does not create a new testing obligation by itself. First determine whether the exact finished product is subject to a CPSC rule, ban, standard, or regulation requiring certification.
Two filing workflows are available
CPSC describes a Full PGA Message Set containing the required certificate fields and a Reference PGA Message Set that points to a certificate already stored in the Product Registry using Certifier ID, Product ID, and Version ID.
FTZ entries have a later date
For covered products entered from a Foreign Trade Zone for consumption or warehousing, the final rule is effective January 8, 2027. That phased date should be tracked separately from the general July 8, 2026 implementation.

When this brief applies

  • Imported finished consumer products that are already required to carry a General Certificate of Conformity or Children's Product Certificate under CPSC-administered requirements.
  • U.S. importers and their brokers preparing Full or Reference PGA Message Sets at entry.
  • Private-label and repeat-import programs that need stable model, factory, laboratory, certificate, and version control.
  • Covered products imported by mail, for which the final rule directs certificate data into the Product Registry before arrival.

What this brief cannot answer

  • Whether the exact SKU is regulated or which CPSC citation codes apply; product type, age grading, materials, use, and construction must be reviewed.
  • Whether a certificate or test report is valid, current, authentic, or scoped to the imported model and production lot.
  • Whether a laboratory is accepted for every cited rule or whether a statutory or regulatory testing exclusion applies.
  • The correct CBP filing, admissibility outcome, or enforcement response for a specific shipment.

Buyer data checklist

Collect these fields before asking a broker, laboratory, compliance specialist, or customs representative for a product-specific determination.

  1. 01

    Product ID and description

    A unique product identifier and a description specific enough to match the finished product to its certificate and shipment.

  2. 02

    Citation codes

    Every applicable CPSC rule, ban, standard, or regulation for which the finished product is being certified.

  3. 03

    Manufacture date

    The applicable production date or initial date of a production series, tied to the batch or lots covered by the evidence.

  4. 04

    Manufacture place

    The actual production or assembly location with sufficient address detail—not merely a trading company's office.

  5. 05

    Most recent test date

    The latest compliance testing date supporting the certificate, connected to the cited requirements and current product construction.

  6. 06

    Testing parties

    Each laboratory or other testing party relied upon, with contact and location data and the rules covered by that testing.

  7. 07

    Point of contact

    The person or continuously staffed function responsible for maintaining supporting test and certification records.

  8. 08

    Certifier and importer

    The responsible finished-product certifier, importer, broker, ACE filing route, and accountable Product Registry administrator where used.

  9. 09

    Exclusions and version control

    Any claimed statutory or regulatory testing exclusion, material-change review, certificate version, and the three Reference IDs if using the Product Registry route.

Official sources

These links point to the agency guidance or legal text used for this brief. Check the source again before making a time-sensitive entry or compliance decision.

  • CPSC Implements Mandatory eFiling for Certificates of Compliance

    U.S. Consumer Product Safety Commission · July 8, 2026

    Current agency announcement confirming implementation, the covered importer workflow, and the January 8, 2027 FTZ date.

  • Update: Certificates of Compliance and eFiling

    U.S. Consumer Product Safety Commission

    Agency guidance distinguishing imported products, domestic certificate-content updates, and the two effective-date scenarios.

  • eFiling Frequently Asked Questions

    U.S. Consumer Product Safety Commission

    Official explanation of the seven core certificate data elements, Full and Reference PGA Message Sets, Product Registry identifiers, exclusions, and repeat-use workflow.

  • Certificates of Compliance — Final Rule, 90 FR 1800

    GovInfo · official Federal Register PDF · January 8, 2025

    Legal text for 16 CFR part 1110, certificate content, responsibility, availability, recordkeeping, eFiling, and effective dates.

  • eFiling Document Library

    U.S. Consumer Product Safety Commission

    Current implementation guide, HTS guidance, citation and testing-exclusion resources, Product Registry documentation, CSV template, and API specifications.

Boundary: this is operational decision support based on named official sources as of the review date. It is not legal, tax, customs-broker, laboratory, or product-certification advice, and it does not calculate a product-specific duty or compliance outcome.