The 5-year paper trail behind every lithium battery pack entry
Clearance is not the finish line. What stays in a lithium battery pack entry file, who owns it, and how to answer a CBP form 28 without a scramble.
Maintaining the pack's certification dossier, test summaries, and revision control as designs, cells, and suppliers change.
Clearance is not the finish line. What stays in a lithium battery pack entry file, who owns it, and how to answer a CBP form 28 without a scramble.
A test report and a listing prove a design was tested, not what shipped this month. Why production records and change control decide a certification audit.
Before attaching a UN 38.3 test summary or UL listing to a pack PPAP, check the model list, cell model, and configuration against the part you are submitting.
A reviewer reads applicant, holder, and covered configuration before accepting any certificate. How to spot a document that doesn't cover your build.
One controlled index that maps every battery certificate and UN 38.3 test summary to the exact pack SKU and revision keeps carrier and customer audits short.
What US importers of lithium-ion battery packs must keep after entry, how long, and what to produce when CBP sends a request for information.
A UN 38.3 test report covers a cell model, not a shipment. How cell lot codes, work orders, and pack serials hold the compliance evidence chain together.
Filing certificates by document type breaks at the first pack revision change. How to run compliance evidence as a versioned, indexed, retained document set.
A UN 38.3 test summary and a UL file are only pointers. Here's the three-record bundle reviewers actually pull: pack serial, cell lot code, end-of-line data.
A custom battery pack file needs six evidence types tied to the exact part number, cell model, BMS revision, and site — plus a register that stays current.