This guide focuses on internal data control and eFiling readiness. Use current CPSC, CBP, broker, and qualified legal/compliance guidance for product applicability, certificate type, safety-rule citations, testing exceptions, HTS treatment, and filing decisions.
1. Confirm which imported products require certification
eFiling applies to imported consumer products that are subject to CPSC certification requirements. Do not treat an HTS flag or a product name as a substitute for the underlying certification analysis. Maintain an internal record showing how the requirement was confirmed and escalate unclear products to qualified guidance.
2. Identify the finished product consistently
Use product identifiers that can be reconciled to purchase orders, invoices, packing lists and internal SKU or model data. CPSC's Product Registry accepts several Product ID types, including SKU, UPC, GTIN and model number. Inconsistent identifiers create avoidable broker and shipment-level errors.
3. Assemble the certificate data before the shipment is urgent
CPSC's eFiling materials identify core information covering the finished product, certifying party, applicable safety rules, manufacture date and place, testing date and laboratory, and the person maintaining test records. Store the source for each field rather than treating the final filing value as self-explanatory.
4. Decide whether your process uses full data or Product Registry references
The Product Registry is not required for importers filing Full PGA Message Sets. If you use the Registry, the Reference PGA Message Set relies on the Certifier ID, Product ID and Version ID for the stored certificate. Confirm the filing path with your broker before designing the handoff.
5. Validate testing and exception records
Certificates must associate applicable rules with supporting testing, and CPSC's current eFiling requirements also address testing exclusions when relied upon. Keep lab names, test dates, reports and any supported exception codes traceable to the certificate record.
6. Create a broker handoff control
Do not rely on an informal email chain. Track the shipment or entry reference, broker, filing path, data or identifiers sent, deadline, confirmation and any unresolved issue. The goal is to know what the broker received before the entry is transmitted.
7. Review changes before reusing prior certificate data
Factory changes, new testing, product modifications and certificate updates can make prior information stale. If using the Product Registry, Version IDs are part of the certificate-identification structure, so version control belongs in the operating process.
8. Archive what was filed and what supported it
Retain the source records, the data package or Registry identifiers used, and broker confirmation. That makes the process reviewable when the same product returns in a later shipment.
Use the Syntera CPSC eFiling Readiness & Certificate Data Control Kit.
Certificate master, trade parties, testing evidence, rules and exceptions, broker handoff, version control, filing readiness and dashboard in one reusable Excel system.
Related CPSC eFiling guides
Official CPSC resources
Educational information and administrative readiness tools only; not legal advice, customs brokerage, filing services, or a certification of compliance.