Product safety standard
Portable secondary battery safety
IEC 62133 series
Read portable rechargeable battery evidence by cell and pack configuration, chemistry, protective arrangements and transport boundaries.
Read the referenceComparative study
A battery test record answers a defined question about an identified design. It does not establish every aspect of product safety or authorize every shipment. This study compares the evidence needed for battery type testing, finished-product controls and transport decisions.
What does a successful battery test establish, and what remains to be decided before a product is supplied or a shipment is offered? This question arises when a purchaser receives one document described loosely as a battery certificate and assumes it covers the finished device, replacement packs and international delivery.
The analysis separates three objects: a cell or battery type, the product in which it is used, and the consignment being transported. Each has a different identity and decision context. Evidence can connect those objects, but the connection must be demonstrated rather than inferred from a common model name or supplier logo.
The legal examples are U.S. lithium battery transport provisions in 49 CFR 173.185 and consumer product provisions in 16 CFR Part 1263. The latter concerns button cell or coin battery hazards and is not a universal safety code for every rechargeable battery.
For the transport reference, the checked text of 49 CFR 171.7 lists the UN Manual of Tests and Criteria, seventh revised edition (2019), with Amendment 1 (2021). That is a legal incorporation fact, not a statement that no later international publication exists. Nor does it remove the specific transition provisions in the operative transport rule.
The method traces the claimed conclusion back to its object and source. A transport test report, a test summary and evidence about the finished consumer product are treated as different records. The review then asks whether the design described in each record matches the item under assessment.
No test procedure from a restricted battery standard is reproduced. There is no comparison of confidential laboratory results or claim that one battery chemistry is safer than another. The comparison concerns the decisions a quality function must keep separate when compiling supplier, design and logistics evidence.
Scroll horizontally to view all columns.
| Evidence or decision | Object addressed | What to examine | Limit of the conclusion |
|---|---|---|---|
| Transport type test record | Identified cell or battery design | Design identity and applicable testing basis | Does not establish all finished-device safety characteristics. 49 CFR 173.185 |
| Test summary | Specified battery or product models | Connection to the underlying report and edition | A summary is not a shipment authorization. 49 CFR 173.185 |
| Button battery product evidence | Covered consumer product or battery category | Applicable performance, warning and packaging provisions | Product scope and exceptions still matter. CPSC guidance |
| Shipment assessment | Actual consignment and configuration | Applicable packaging and transport conditions | Previous delivery does not determine the next shipment. 49 CFR 173.185 |
The principal finding is that evidence becomes unreliable when its identity or purpose changes silently. A report about one pack cannot simply be assigned to a revised assembly because the enclosure looks similar. Equally, a product safety file cannot answer a logistics question merely because it includes battery information.
One legal detail illustrates why scope must remain visible: the test summary requirement in 49 CFR 173.185(a)(3) addresses cells or batteries manufactured on or after 1 January 2008, with an exception for button cells installed in equipment, including circuit boards. A general purchasing checklist that removes this distinction can demand the wrong evidence or overlook the applicable obligation.
CPSC's guidance addresses a different product safety concern. Keeping those purposes separate improves both the request and the interpretation of the response.
Create a battery identity record before requesting documents. Record the cell and pack designations, product model, supplier and controlled design revision. Use it to reconcile the report, summary, bill of materials and finished-product documentation. Where the identifiers differ, record the technical explanation and who evaluated it.
An illustrative replacement-pack change shows the value of this discipline. Procurement may see an equivalent capacity and connector, while engineering needs to examine the changed design and logistics needs to review the intended shipping configuration. Those are separate approvals within the organization; one function's acceptance should not close the others by default.
Keep transport planning connected to returns and damaged goods as well as ordinary outbound supply. A routine dispatch instruction should not be reused for an exceptional condition without review.
The control objective is a traceable decision for the actual item and journey. It is not a larger folder of documents bearing similar product names.
This study does not classify a particular consignment, determine an air carrier's acceptance conditions or select packaging for damaged, defective, prototype or waste batteries. Those cases require their applicable rules and facts. A U.S. legal example also does not establish the requirements of every departure, transit or destination jurisdiction.
Product safety requirements can extend beyond the button battery example. Applicable electrical, mechanical, charging, thermal and end-use requirements must be identified separately. The reference family pages help locate those questions; neither this study nor the Center for International Standards Study provides a transport approval, product certification or laboratory determination.
The sources identify the U.S. regulatory basis used in this comparison. The UN edition statement comes from the incorporation provision, without relying on a publisher's latest-edition label. An implementation review should read both that provision and the operative battery requirements.
The evidence boundary is deliberate: an article explaining document roles cannot validate a report's authenticity or establish that a changed design remains covered. Those questions require the underlying technical record and the relevant decision maker.
Sources checked: 19 October 2026. Published: 19 October 2026.
Read the battery safety and transport reference families together, while retaining a separate conclusion for each. A transport-related reference should not be filed as evidence of all consumer safety requirements.
Use the supplier evidence matrix to connect each supplier record to its intended decision. The product applicability record can capture the product and market context before the technical evidence is evaluated. Revisit both records when the pack, product configuration or delivery route changes.
Portable secondary battery safety · Lithium battery transport tests · All studies.
Source record
Sources checked 2026-10-19. This date records preparation of this resource; publication, legal and transition dates are identified separately.
U.S. lithium battery transport requirements and test summary conditions
49 CFR 173.185: Lithium cells and batteries www.ecfr.govSpecific UN Manual editions incorporated in U.S. hazardous materials regulations
49 CFR 171.7: Reference material www.ecfr.govU.S. consumer product and button or coin battery requirements within the rule scope
16 CFR Part 1263 www.ecfr.govPublic explanation of product safety requirements and the distinction between product categories
CPSC: Button Cell and Coin Battery Business Guidance www.cpsc.gov