ComplyMyImport

ComplyMyImport guide

CPSC eFiling readiness audit for consumer product importers

CPSC eFiling is now part of the import process for most covered consumer products that require a certificate. The main effective date was July 8, 2026; covered products entered for consumption or warehousing from a Foreign Trade Zone follow on January 8, 2027.

Being "ready" means more than having a CPSC Product Registry account. An importer needs a repeatable way to decide which products require certification, maintain defensible certificate data, give the correct information to the customs broker, and respond when a filing is questioned.

Use this audit to find weak points before they become shipment problems.

1. Can you identify every product that needs a certificate?

Start with the product catalog rather than the next shipment. For each imported SKU, document whether the product requires a Children's Product Certificate, a General Certificate of Conformity, or no CPSC certificate.

For children's toys and accessories, that review should consider the product's intended age, play value, materials, coatings, dimensions, and foreseeable use. An HTS code may affect how an entry is screened, but it does not replace a product-specific applicability analysis. A product can still require certification even if its HTS code is not on a particular flagging list.

ComplyMyImport keeps the product facts, rule-pack version, cited requirements, rationale, evidence, and unresolved gaps together. Automated results remain preliminary until reviewed; they are not final legal determinations.

2. Does your primary Product ID survive the whole workflow?

CPSC permits seven Product ID types: GTIN, SKU, UPC, model number, serial number, registered number, and alternate ID. The best choice is not necessarily the identifier that is most convenient for one team. It should consistently identify the finished product across the certificate, packaging, commercial documents, broker instructions, and Product Registry record.

Audit a sample SKU from end to end:

Do not use one identifier to hide materially different products. A clean identifier strategy reduces duplicate records and lowers the chance that a valid certificate is attached to the wrong entry line.

3. Can each certificate field be traced to reviewed evidence?

The required filing data includes product identification, applicable citation codes, manufacture date and place, the most recent compliance test date, testing-party details, and the test-records contact. As of July 8, 2026, the revised rule also requires applicable testing-exclusion information.

Check more than whether each field is populated. Confirm where it came from, who reviewed it, and whether it still describes the imported product. Common warning signs include a factory address copied from an invoice, a testing date from an unrelated model, or citations inherited from an old certificate without current applicability review.

ComplyMyImport can organize source-linked evidence and prepare a draft certificate, but an authorized customer representative must approve the certificate. AI extraction may assist the review; it cannot issue the CPC or GCC.

4. Is Full or Reference filing assigned product by product?

A Full PGA Message Set sends the required certificate data with the entry through CBP's Automated Commercial Environment. A Reference PGA Message Set sends the Certifier ID, Product ID, and Version ID that point to certificate data stored in the CPSC Product Registry.

Reference filing can fit products imported repeatedly under unchanged certificate data. Full filing may be easier for a limited number of products or less repetitive imports. An importer can use different paths for different products; the important control is to record the chosen path and make sure the broker receives the corresponding package.

Ask your broker which path its system supports, how it wants data formatted, when it needs the information, and how corrections will be communicated. The importer owns the accuracy of the certificate information even when a broker transmits it.

5. Are Product Registry roles and privacy settings intentional?

Review who can administer the business account, manage product collections, enter data, and certify records. Remove access that is no longer needed and avoid shared credentials.

CPSC's Product Registry includes collection-level Trade Party Privacy settings. The choice affects how supplier, manufacturer, and laboratory information is visible to users, and the setting cannot be changed after the collection is created. Decide the collection and access model before loading a large catalog.

Within ComplyMyImport, product records and documents should also be limited by organization membership and product assignment. Supplier collaboration should expose only the requested evidence and assigned products, not the full compliance portfolio.

6. Can you distinguish registry, broker, and government status?

Three milestones must remain separate:

A Product Registry record is not an ACE submission. A broker-ready export is not proof of transmission. A transmission is not the same as final clearance. Combining these events into a single "filed" status makes it difficult to locate failures and can overstate what has occurred.

ComplyMyImport preserves this boundary by tracking certificate approval, registry references, broker-package activity, and reported filing status as distinct records. It does not represent an unverified customer or broker update as CBP acceptance.

7. Is there an exception owner and response procedure?

Document who receives broker or government messages, who can answer product questions, and who may authorize corrections. Keep the supporting certificate version and evidence available to the response team.

Your procedure should cover at least:

The response path should preserve the original submission, the reason for the correction, the person who approved it, and the updated version. Overwriting history may make a quick correction look easy while weakening the audit record.

8. Have you run a real product through the process?

Choose one active product and conduct a tabletop filing before the next shipment cutoff. Map the product to its entry line, validate every certificate field, confirm the filing path, create the broker handoff, and rehearse an exception. Include the compliance owner, operations team, supplier contact, and broker.

Score the exercise on evidence completeness, identifier consistency, approval readiness, handoff clarity, and exception ownership. Fix the first bottleneck before expanding to the rest of the catalog.

Turn the audit into a controlled product record

ComplyMyImport helps small importers move from disconnected spreadsheets, email attachments, and certificates to a product-centered compliance workflow. Start with the readiness check, identify missing evidence, and convert the result into a managed workspace when you are ready to resolve the gaps.

ComplyMyImport is not a law firm, customs broker, testing laboratory, or importer of record. This guide is general educational information, not legal or customs advice. Confirm current requirements and product-specific decisions with CPSC, CBP, your customs broker, and qualified counsel.

Official resources

Continue reading

CPSC eFiling Is in Effect: What Importers Need to KnowA practical CPSC eFiling playbook for small importers: organize certificate data, choose a filing path, prepare the broker handoff, and avoid preventable entry delays.CPSC eFiling Guide for ImportersUnderstand CPSC eFiling, Product Registry preparation, Full and Reference PGA Message Sets, and the importer-to-broker handoff for ACE entry.CPSC eFiling July 2026 Readiness ChecklistPrepare imported regulated products for the July 8, 2026 CPSC eFiling requirements with a product, certificate, registry, and broker checklist.
Browse all compliance guides →