CPSC eFiling is not simply a place to upload a supplier document. It is a structured way to organize certificate data for a specific product, including the certificate type, applicable rules, testing records, manufacturer and responsible parties. This reference page turns CPSC’s published Product Registry, certificate and eFiling materials into a practical human review sequence.

Scope note: The Product Registry is a tool for managing and transmitting certificate data. It is not an approval or safety outcome issued by CPSC for an individual product. Whether a certificate is required, and whether it is a GCC or CPC, must be determined from the product and the applicable CPSC requirements.

1. Confirm the role and certificate scope

For imported finished products, the eFiling record commonly needs to align with the Importer of Record (IOR) and with the party responsible for the certificate statement. CPSC’s importer guidance explains that the importer typically creates the Product Registry business account. In certain situations, an authorized customs broker may identify the owner, purchaser or consignee that is responsible for compliance. The upload user, certificate party, import record and product evidence should therefore be reconciled rather than treated as interchangeable.

Identify the certificate type for each product. A General Certificate of Conformity (GCC) is generally associated with applicable general-use product rules, while a Children’s Product Certificate (CPC) is used for applicable children’s product requirements. The choice should follow the product and the CPSC rules, not a retailer account or brand name.

2. Product identification fields

Build a traceable relationship between one product identifier, one certificate version and the supporting test records. Review the following fields:

  • Product Update: distinguish a new record from an update to existing data;
  • Version ID: assign a trackable alphanumeric identifier to the product certificate version;
  • Primary Product ID: record the actual GTIN, SKU, UPC, Model Number, Serial Number, Registered Number or Alternate ID, together with its selected type;
  • Product Name / Model: keep the name traceable to the specification, packaging and certificate;
  • Manufacturer information: provide a Manufacturer GLN or applicable alternate identification as required by the Product Registry;
  • Manufacture date: prepare the month and year in the format required by the system and protect it from spreadsheet reformatting.

A Product ID field should contain only the product identifier represented by the selected type. Do not combine several SKUs, marketing copy, certificate numbers or a paragraph of description in one ID field. An Alternate ID should still point to one identifiable product.

3. Certificate, applicable rules and test records

A certificate is not a generic document that can be detached from the product. CPSC’s eFiling FAQ explains that a certificate should identify the applicable rules, bans, standards or regulations, the most recent testing date and each laboratory that performed the testing. Testing on a component or finished product should remain traceable to the rule it supports.

  • Certificate Type: check whether GCC or CPC matches the product category;
  • Rules and citations: register the specific CPSC rules, bans, standards or regulations instead of using a broad “all-category compliance” label;
  • Laboratories: record the laboratory and the scope of testing it supports; CPSC-accepted third-party testing requirements apply to children’s products where required;
  • Test dates and reports: reconcile the date, report number, model, sample information and applicable rule; whether optional fields such as Test URL, Test Report Key and Test Report ID should be populated should be checked against the current CPSC form and the available evidence;
  • Testing exclusions: retain the basis for any testing exclusion code and confirm that it matches the product and rule;
  • Record custodian: identify whether test-result records are maintained by the importer, manufacturer, laboratory, broker or another party.

4. Human review before filing

  1. Place the physical product, model, SKU, packaging and import entry in one comparison table so the Product ID cannot drift between records;
  2. Determine the certificate type and applicable CPSC rules from the product. Do not automatically treat EU, state-level or retailer documents as CPSC certificate support;
  3. Reconcile the manufacturer, importer or responsible party, laboratory and test records;
  4. Review the Product Registry version, update indicator, date format and CSV fields, and preserve the pre-upload source file;
  5. Have an authorized business-account user confirm the data and preserve the links between the final certificate data, test support and import records.

5. Boundaries of the review

An eFiling data review does not replace product classification, applicable-rule analysis, laboratory testing, certificate issuance or import responsibility analysis. CPSC’s HTS assistance list is not a complete list of products requiring electronic certificates, so an HTS code alone should not be used to decide whether a certificate is required. New products, material changes, model changes and rule changes call for a fresh review of scope, testing basis and certificate data.

This page is a documentation and human-review framework. For a specific product, use the latest CPSC eFiling pages, Product Registry guides, FAQ, applicable rule text and the actual import responsibility chain. 绿色方舟（深圳）认证有限公司 can help map fields after complete product and evidence records are provided; this page does not promise approval, a certification outcome or import release.