Data check date: July 6, 2026. This article is based on the CPSC eFiling FAQ, CPSC certificate and eFiling guidance, Federal Register 90 FR 1800, and public information reviewed by Greenark (Shenzhen) Certification Co., Ltd. It does not promise release, clearance timing, platform review, test results, certification results or commercial outcomes.

Why this final check matters

CPSC states that eFiling requirements for most imported consumer products take effect on July 8, 2026. For products entered from a Foreign Trade Zone for consumption or warehousing, the effective date is January 8, 2027.

The practical question is no longer only whether a CPC or GCC document exists. Importers, sellers, factories and brands need certificate information that can be mapped into entry filing data and reconciled with SKUs, product descriptions, test reports and applicable safety citations.

The seven data elements to align first

For the Full PGA Message Set, CPSC identifies seven certificate data elements that must be available for regulated products: Product ID, citation codes, manufacture date, manufacture place, product test date, testing laboratory and point of contact.

For the Reference PGA Message Set, certificate data should be preloaded in the CPSC Product Registry. At entry, the broker can reference the Certifier ID, Product ID and Version ID instead of transmitting every data element again.

Common mistakes before entry filing

  • SKU and Product ID mismatch: internal SKU, platform SKU, factory model and certificate description should not point to different products.
  • Overly broad citation codes: avoid generic statements such as "CPSC compliant" when the specific rule, ban, standard or regulation has not been identified.
  • Date conflicts: manufacture date, sample test date and report issue date should be kept distinct and consistent across files.
  • Incomplete lab or contact details: testing laboratory information and records contacts should be traceable by the importer, broker and customer.

What each team can do now

Cross-border sellers should start with a SKU list for US listings, inventory in transit, upcoming shipments and repeat-purchase products. Mark which products may require a CPC or GCC, then connect each item to a Product ID and certificate version.

Factories and suppliers should organize test reports by product, model, batch, factory address, production date, test date, lab name, report number and certificate file.

Importers and customs coordination teams should confirm whether the Full PGA Message Set or Reference PGA Message Set is more appropriate for each product group. The filing path affects how data must be prepared and handed over internally.

Safer wording for customer-facing claims

Avoid saying that eFiling is "completed" unless the specific entry process and registry status have been confirmed by the responsible importer and broker. A safer wording is: "Certificate data for the relevant SKUs has been reviewed against CPSC eFiling data fields; the final filing path should be confirmed with the importer and customs broker."

Avoid saying that complete certificates guarantee clearance. A safer wording is: "Certificate data, applicable citations, test reports and entry fields should remain consistent; final requirements are subject to CPSC, CBP, importer and broker procedures."

How Greenark can support the preparation

Greenark (Shenzhen) Certification Co., Ltd. can support CPSC eFiling field mapping, CPC/GCC document checks, test report organization, SKU ledger preparation, Product ID and certificate version mapping, and claim-boundary review for US-market product pages and customer questionnaires.

This support is document organization, route screening and consulting. It does not replace decisions by CPSC, CBP, importers, customs brokers, testing laboratories or customers, and it does not promise clearance timing, test results, certification results, platform review or commercial outcomes.