July 8 changes the import workflow for regulated consumer products.

The U.S. Consumer Product Safety Commission says importers of most regulated consumer products will need to electronically file certificate data with U.S. Customs and Border Protection through a Partner Government Agency message set. Products entered from a Foreign Trade Zone follow a later January 8, 2027 date.

For Amazon sellers, the practical change is not that safety standards suddenly appeared. It is that certificate information must become structured, accurate entry data before goods enter U.S. commerce.

This is an operating-system change, not a document-upload task.

Start with product classification

Do not begin by asking a forwarder whether it can “handle eFiling.”

Begin with the finished product. Determine which CPSC rules, bans, standards, or regulations apply; whether a Children’s Product Certificate or General Certificate of Conformity is required; what testing supports it; and whether a legitimate exclusion applies.

Build the analysis by SKU or clearly controlled product family. Small differences in age grading, material, component, power source, or intended use can change the requirement. A certificate copied from a similar product is not a shortcut if the products are not actually covered by the same evidence.

Compliance counsel or a qualified specialist should resolve ambiguous classifications. Logistics should not make legal-product determinations at the port.

Separate reports, certificates, and filings

These artifacts support one another, but they are not interchangeable.

A laboratory report records testing. A certificate affirms that a specific finished product complies with the applicable requirements and identifies the rules, dates, laboratories, manufacturer or importer, and responsible record keeper. eFiling transmits the required certificate data in the import process.

The CPSC Product Registry can store certificates that are referenced during entry. The chosen product identifier must reliably match the goods and commercial paperwork. CPSC guidance allows several identifier types, including GTIN, SKU, UPC, model number, serial number, registered number, and an alternate ID.

Choose identifiers the warehouse, broker, and compliance team can all recognize. A technically valid identifier that no one can map to the carton creates operational risk.

Separate the IOR, certifier, and transmitter

The importer of record is not a name to borrow for a shipment. It is a party eligible to make entry, but the eFiling role map can be more specific than a single label.

CPSC guidance treats the IOR as the importer for eFiling. When an authorized customs broker acts as IOR but lacks enough product knowledge to take responsibility for testing and certification, that broker may identify the owner, purchaser, or consignee that authorized the entry as the certifying party. That exception is precisely why teams should not collapse IOR, certifier, and data transmitter into one spreadsheet cell.

A foreign company may be able to act as a nonresident importer under the appropriate structure, but feasibility depends on customs, bonding, tax, agency, and business facts. Document who is the IOR, who is responsible for the CPSC certificate, whose bond is used, who transmits the PGA message set, who controls the broker power of attorney, who maintains Product Registry access, and who answers a CPSC or CBP question.

Have qualified customs and legal advisors confirm the role design rather than accepting a sales promise from a logistics vendor. Operational work can move between parties; accountability should remain explicit.

Build the SKU-to-entry map

Create one control sheet or governed system that connects each SKU with its product identifier, classification, applicable rules, certificate, supporting reports, lab scope, manufacturer, IOR, certifying party, bond, data transmitter, and filing status.

Add version control. A material, factory, component, or design change may require new testing or a revised certificate. The team needs to know which certificate applies to which production lot.

Restrict approval rights but make status visible to sourcing, compliance, and logistics. A shipment should not be released because someone found a PDF with a familiar product name. It should be released because the mapped evidence is current and the filing path has been checked.

Use a red-amber-green status. Red means the product cannot ship. Amber means a named dependency and deadline remain. Green means evidence, roles, and data are ready.

Test the handoff before volume

The best time to discover a product-ID mismatch is during a controlled test, not when a container is waiting.

Walk one representative SKU through the complete handoff. Confirm Product Registry access, certificate identifiers, broker mapping, message-set fields, manufacturer and lab data, and response handling. Rehearse who acts if CBP or CPSC rejects or questions the filing.

Retain the transmission record and supporting evidence with the entry. Review permissions too: the person who built the original registry account should not be the only person able to operate it.

After launch, monitor rejects, holds, broker questions, certificate changes, and SKUs added without classification. Treat every exception as feedback on the control design.

The Operator Read

CPSC eFiling makes product compliance more operationally visible.

Sellers that relied on a folder of test reports and a forwarder’s reassurance now need a governed path from finished product to certificate data and customs entry. The work is precise: classify the SKU, validate the certificate, distinguish the IOR, certifier, and transmitter, test the handoff, and retain the evidence.

Do not outsource the understanding. A good broker can transmit clean data. Only the business can ensure that the data describes the product it actually made and shipped.

CPSC eFiling goes live July 8. Map the certificate before the shipment