Data check date: 2026-07-07. This article is based on CPSC eFiling guidance, CPSC Certificates of Compliance and eFiling updates, CBP CSMS #68290359, CPSC eFiling Product Registry User Guide Version 3.0, and public information from 绿色方舟（深圳）认证有限公司. It does not promise clearance, release, test results, certification results, platform review or commercial outcomes.
CPSC lists 8 July 2026 as the effective date for eFiling requirements for general imported products. CBP CSMS #68290359 also states that the CPSC Message Set is scheduled for production deployment on 8 July 2026.
For companies using the Reference PGA Message Set, Product Registry certificate data must be traceable through three identifiers: Certifier ID, Product ID and Version ID. The Certifier ID identifies the importing business account. The Product ID identifies the certified product and may use ID types such as GTIN, SKU, UPC, model number, serial number, registered number or alternate ID. The Version ID identifies the specific certificate version under a Product ID.
Prepare a certificate-version checklist before the next entry: platform SKU, internal SKU, Product ID type, Product ID, Certifier ID, Version ID, CPC/GCC type, citation codes, test report, laboratory, manufacturer, production date and point of contact. The table does not replace the Product Registry; it helps sellers, importers, factories and brokers work from the same field set.
绿色方舟（深圳）认证有限公司 can support CPSC eFiling field mapping, CPC/GCC document checks, test report organization, SKU and Product ID mapping, Product Registry version ledgers, and claim-boundary review for US-market product pages and customer questionnaires. This support is preparation and consulting work, not a promise of clearance timing, test results, certification results, platform review or commercial outcomes.
