CPSC eFiling, explained:
the complete guide for importers.

What is CPSC eFiling?

CPSC eFiling — commonly searched as "CPSC eFile" or "CPSC e-filing" — is the U.S. Consumer Product Safety Commission's program for filing certificate data electronically. Instead of holding a paper Certificate of Compliance and producing it on demand, importers file the certificate's data elements into the CPSC Product Registry, where the certificate is certified and issued three Certificate Identifiers. Those identifiers are then referenced at the border every time a covered shipment enters the United States.

The requirement took effect on July 8, 2026. Since that date, importers of regulated consumer products file certificate data electronically with the CPSC rather than relying on paper certificates alone.

Who has to eFile?

The requirement applies to importers of regulated consumer products — products that must be certified under CPSC rules:

• Children's products certified with a Children's Product Certificate (CPC), backed by testing at a CPSC-accepted laboratory.
• General-use products certified with a General Certificate of Conformity (GCC).

Not every shipment files, though. Shipments to non-U.S. destinations never enter U.S. commerce, and on LDP/DDP terms the factory — not you — can be the importer of record. Trackports models both: those shipments are approved without filing, with every record kept, and no notice is ever sent claiming a CPSC filing that didn't happen.

What goes in a Certificate of Compliance (16 CFR 1110)

An eFiled certificate captures the seven data elements required under 16 CFR 1110:

• Identification of the product covered by the certificate.
• Each rule or citation the product is certified to (for example, 16 CFR 1610 for flammability of clothing textiles).
• The date and place of manufacture.
• The date of testing.
• The testing laboratory — for children's products, a CPSC-accepted lab.
• A point of contact for the records supporting the certificate.
• The certifier — the party legally responsible for the certification.

Miss any one of these and a filing isn't valid. That's why Trackports enforces readiness gates that block a shipment from being submitted until every style has a manufacturer, citations, a linked lab report (or a valid exemption), and the rest of the required data.

How an eFiled certificate reaches the border

This is the part that confuses most teams, so here is the whole path in order:

1. File & certify. The certificate's data elements are filed into the CPSC Product Registry. Trackports does this through the Product Registry V4 API — it builds the filing from your shipment data, submits it, polls status until the upload completes, and records the result.
2. Get the Certificate Identifiers. The Registry issues three identifiers for the certified certificate: your Certifier ID, Product ID, and Version ID.
3. Hand off to your broker. At time of entry, your customs broker references those identifiers in the Reference PGA Message Set they file into CBP's ACE. The certificate is entered once and referenced on every shipment — never re-keyed.

Trackports automates the first two steps behind a single reviewer attestation and gives your broker a locked-down export surface for the third — so nobody transcribes identifiers by hand.

How to get compliant, step by step

1. Inventory what you certify. Which products need a CPC, which need a GCC, and which citations apply to each.
2. Collect your test reports. Every certified style needs current lab testing behind it — or a valid exemption. In Trackports, reports live in a reusable vault, styles can carry multiple reports and exemptions side by side, and an AI reviewer checks every PDF against what the factory claimed before you certify.
3. Set up your Product Registry account. Register as a certifier and get API credentials. Trackports connects with your certifier ID and token, auto-detects your collection, and the pipeline is live the moment credentials are in — no redeploy.
4. File, then hand your broker the identifiers. From there it's per-shipment routine: factory drafts, AI pre-checks, reviewer attests, Trackports files and tracks it, broker exports the identifiers.

Trackports integrates with most ERPs, so teams that bring their existing order file are typically live in days — with no new data format to adopt.

Common pitfalls that stall filings

• Missing manufacturer details. A CPSC filing needs a complete manufacturer record — Trackports validates emails and phone numbers on entry, because malformed contact data is a classic import failure.
• Lab mismatches. The report says one laboratory branch, the claim says another. The AI reviewer checks the issuing lab down to the exact branch.
• Citation gaps. The certificate claims 16 CFR 1610 but the report doesn't cover it. Caught automatically, before submission.
• Styles missing from reports. A report that covers the base style but not the colorway you're shipping. The reviewer understands base-style mapping and flags real gaps.
• Silent failures. A filing that errors out and nobody notices. Trackports is queue-driven with a clear failed state, the exact CPSC reason, and a one-click retry.

Paper certificates vs. eFiling at a glance

Under the paper model, the certificate is a PDF someone maintains, and every entry is a chance for stale data, missing test reports, and manual re-keying. Under eFiling, the certificate is structured data, certified once in the Product Registry, referenced by identifier at every entry — and everything about it is checkable by software before it's filed. That's the shift Trackports is built around: the filing pipeline, AI-checked evidence, and an audit trail for every change.