Factory-direct GaN & wireless chargers · MOQ from 200 pcs

Talk · Compliance · Test reports, labels & documents

What should a recall-ready traceability file contain for a charger?

It should let you answer quickly which units are affected, where they are and who has them.

Updated 3 min read

What should a recall-ready traceability file contain for a charger?
The question

We want to be ready if we ever have to recall a charger. What should our traceability file contain?

Main answer · Wecent Editorial Team

Short answer: It should let you answer quickly which units are affected, where they are and who has them. Include model and batch codes, production dates, component lots, test records, shipments and customer lists, complaint records, and contact details for the factory and authorities. Run a mock recall to check that the file works.

Why prepare

In the US, companies that make, import, distribute or sell consumer products have to report certain safety information to the Consumer Product Safety Commission promptly. The CPSC’s guidance also says to identify affected models, date codes and units, stop shipping, isolate inventory, notify distributors and set the remedy. Having a file ready makes each of these steps faster.

What to include

  1. Product identification. Model numbers, variants, UPC or barcodes, photos and labels.
  2. Batch and date codes. How each unit or carton is coded, and what the code means.
  3. Production records. Dates, quantities, factory, line, and test and inspection results for each batch.
  4. Component traceability. Which lots of critical components went into which batch, such as battery cells in power banks, transformers and controllers.
  5. Design and change records. Specification versions, approved changes and the dates they took effect.
  6. Certification documents. Reports, certificates and declarations for each model.
  7. Shipment records. Which batches were shipped to whom, on what dates, with invoices and packing lists.
  8. Customer and channel list. Distributors, retailers and marketplaces, with contacts.
  9. Stock records. What remains in each warehouse, by batch.
  10. Complaint and incident records. With batch codes, photos and outcomes.
  11. Communication plan. Who decides, who contacts the authorities, customers and the press, and the templates.
  12. Remedy options. Refund, replacement or repair, and how returns will be handled.
  13. Contacts. The factory, the lab, the broker, legal advisers and the insurer.

How to test it

Run a mock recall once a year. Pick a batch, and measure how long it takes to find all units, quantities and customers. Fix the gaps that appear.

Keep it current

Update the file as production and sales continue, and keep records for the period required by the rules and by your own policy.

Canada

Canadian rules have their own reporting duties for consumer products. Check the official guidance from Health Canada as well.

Quick summary

Be able to answer: what, how many, where, who. Test the file with a mock recall.

Sources checked on 24 Oct 2026: CPSC: Recall Guidance; CPSC: Duty to Report; CPSC: Recall Checklist.

Where this answer says to confirm with Wecent, the detail is not published on the product page and has to come from the datasheet or the factory. General facts come from the regulators, standards bodies or device makers named in the text.

Three more perspectives

Wecent Editorial Team · Compliance/QC perspective

Keep batch, component-lot and shipment records linked, and test the file with a mock recall each year.

Wecent Editorial Team · Purchasing perspective

Require factory traceability from component lot to carton label in the purchase agreement.

Wecent Editorial Team · After-sales perspective

Record every complaint with batch code and photos so that patterns are visible early.

Products discussed in this thread

Related articles & topics

Have a sourcing question about your own programme?

Ask our team More Test reports, labels & documents questions