CPSC eFiling Makes Certificate Ownership a Shipment Control

Certificate data, not PDF storage

Many importers keep certificates in supplier folders and call the job finished. CPSC eFiling changes that habit. A certificate must support filing data for a product entering the United States. That means the importer needs the exact model, product version, standard, lab, issue date and responsible party in a format a filing workflow can use.

The weak file often looks organized at first glance. It has reports, labels and supplier emails. The trouble starts when the broker asks which certificate covers the current version. If the certificate covers a similar model, an old material or a different accessory set, the importer owns the gap even when the supplier sent a real document.

SKU-level control

The safest record begins at SKU level. A product team should map each regulated SKU to one current certificate and one backup note that explains the scope. The note should say what changed since the last certificate: material, label, packaging, user instructions, accessory bundle or production site.

This work also protects sales teams. A marketplace listing may describe a product more broadly than the certificate allows. If the listing says a product suits children, outdoor use or a regulated function, the certificate and warning language must support that claim. eFiling does not fix unsupported marketing language.

Case pattern for version drift

A seller updates a product with a new charger, new packaging and a revised manual. The supplier says the certificate still applies. The importer forwards the same PDF to the broker. During a data review, the team cannot prove whether the new configuration falls within the certificate scope.

The importer can prevent that mess with a version log. The log does not need legal language. It needs dates, product changes, certificate decisions and the person who approved the file. If the team cannot explain the change, it should not ship under the old evidence.

Readiness checklist

Importers should test a sample filing before a deadline or route change creates pressure. Pick the top regulated products and ask whether a broker could file from the internal record alone. If the answer requires a supplier phone call, the file needs work.

The strongest control is boring: one owner, one SKU map, one version history. That structure lets teams answer a product question without hunting through email threads.

• Create a regulated SKU inventory.
• Attach the current certificate to each SKU and model.
• Mark superseded certificates as old, not current.
• Compare listing claims with certificate scope.
• Run a broker data test for high-volume products.

Thirty-day field test

A useful test is to put one live order, one active listing and one supplier file beside this briefing. The team should walk through the records as if a platform reviewer, customs officer or buyer asked for proof tomorrow morning. The exercise should produce a short gap list, not a presentation. Each missing record needs an owner, a due date and a business decision if the record cannot be obtained.

Do not wait for a perfect compliance system. Pick the highest-risk product in the category and test the file with the people who would answer the real request: sourcing, logistics, finance, marketplace operations and customer support. If those teams give different answers, the company has found the risk before an outside reviewer does. That is the value of the exercise.

Keep the record of the test in the same folder as the order or listing. A short note with the reviewer name, date, missing evidence and final decision gives the next reviewer a starting point. It also stops teams from repeating the same conversation after every customer question, route change or platform notice.

Set a review rhythm after the first pass. Thirty days is enough for an initial cleanup, but supplier changes, product edits and route changes should reopen the file. The rule is simple: when the commercial fact changes, the evidence file changes with it.

The team should keep a change log beside the evidence. It should say which document changed, who approved the change and which live product, route or supplier record was affected. That log turns a pile of files into a working control because later reviewers can see the decision path instead of guessing why an old record was replaced.

• Choose one product or shipment that is still active.
• Ask who owns each evidence item and where it is stored.
• Compare the public claim with the internal document.
• Record the business action if evidence is missing.
• Repeat the test after the next supplier, route or listing change.

Source links

• CPSC eFiling Program
• CPSC Import Safety