Power Bank Product Liability File: Evidence an Importer Should Retain Before Launch
What records let a power bank importer identify the shipped version and respond to a later safety claim?
Keep a version-controlled file that connects the product identity, lot, supplier, test scope, approved claims, labeling, shipment and complaint process. The useful unit is the exact sellable configuration, not a generic product family. Record owners and retention rules for every market. For EU consumer products, Regulation 2023/988 includes technical-document and traceability duties; the applicable operator role and other battery rules need a separate review.
Decision framework for buyers and importers
1. Capture the release baseline
Keep the approved sample, drawings, BOM, firmware where relevant, battery details, risk assessment and tests with model and revision. Index what each report actually covers. A supplier declaration without scope cannot reconstruct the shipped unit.
2. Link each lot to market presentation
Retain serial or batch mapping, carton and label artwork, instruction language, product-page claim version, importer details where applicable, shipment destination and sales channel. Preserve superseded artwork with its effective date.
3. Prepare the incident path
Name who receives complaints, preserves products and records, evaluates hazards and contacts suppliers or authorities. EU GPSR Article 9 requires manufacturers to keep technical documentation available for 10 years after placement; apply obligations by role and market rather than copying that period to every record.
| File element | Owner | Milestone | Later use |
|---|---|---|---|
| Design and battery baseline | Engineering | Sample approval | Identify shipped build |
| Tests and risk analysis | Quality/compliance | Market release | Assess scope |
| Labels, instructions, listing | Product owner | Artwork approval | Reconstruct buyer information |
| Lot and shipment map | Operations | Dispatch | Bound affected units |
This original decision table is a working aid. Apply it to the exact SKU, market and signed agreement.
Evidence file, warning signals and scenario
Evidence checklist
- Model, revision, BOM, battery and approved sample references.
- Risk analysis, tests, declarations and scope index.
- Label, instructions and listing claims by market.
- Serial/lot, carton, shipment and distributor links.
- Record owner, retention basis, access and incident procedure.
Hypothetical buyer scenario
Hypothetical complaint: a customer reports a hot unit six months after launch. The importer has two label revisions and a mid-cycle battery change. Because the file records effective dates and lot mapping, the team identifies the exact configuration, compares its test scope and begins a safety assessment. Without that map, the investigation would be slower and broader.
Continue with the previous article in this commercial-risk series, review power bank platforms and factory and quality information, or use the engineering guides when preparing an exact-SKU RFQ.
Frequently asked questions
Is a test report enough?
No. It must be tied to the shipped model, revision, claims and market.
Should old artwork be deleted?
No. Keep effective dates to reconstruct what customers received.
What identifies an affected population?
A reliable serial, lot, carton and shipment link.
Who owns the file?
Assign an importer or brand owner and supplier contact for each record group.
Is one retention period right for every record?
No. Follow each market's law and contract; the EU GPSR has specific technical-document rules.
Does the file establish safety?
No. It supports risk review and traceability; underlying evidence must be sound.
What if a report covers an older revision?
Document the change assessment and obtain new evidence where needed before release.
Primary sources and scope
Send the product revision, destination, sales route and decision deadline. ZEROSET can review the requested OEM/ODM file and route questions to engineering and quality.
