Is Your Battery Pack Covered by UL 2054 or IEC 62133?

The pack you are sourcing is covered by UL 2054, by UL 62133-2, by IEC 62133-2, or by none of them, and the standard number printed on a certificate will not tell you which. UL 2054 is built around battery packs for household and commercial use. UL 62133-2 and IEC 62133-2 are built around secondary lithium cells and batteries for portable applications. Different scopes, different evidence. Which one your program actually needs turns on three things the pack itself cannot answer: what the pack powers, which certification path the OEM chose, and which market the finished product sells into. So the first thing to read on a supplier's safety document is not the standard number on the cover. It is the model designation field on an inside page.

Pull up a chair next to my desk for a few minutes. Left monitor has a quotation from a pack assembler. Right monitor has a PDF the salesperson attached after writing "UL certified" in the notes column. On the desk between them is a printed copy, because I mark these up by hand before I reply to anyone.

Page one looks reassuring. A mark, a company name, a standard in the header. If you stopped there, you would file it and move on to arguing about price.

Go to the field labeled Model, or Type, or Product Designation. The wording varies by issuing body. Read what is printed after it. If it says "Lithium-ion battery pack" or "Li-ion rechargeable battery," you are holding a document that says a category of product was evaluated. Your pack is a configuration: this cell, this BMS, this enclosure, this harness, this label. A category approval is not a model approval, and the gap between the two is where a lot of first shipments die.

If it does name a model, read the string character by character. Suffix letters and revision numbers matter. I have seen a certificate for ABC-4812 and a purchase order for ABC-4812B, and the supplier's position was that the B was just a packaging change. Maybe. But the certificate describes ABC-4812, so somebody has to say in writing what changed and whether the evaluating body was notified.

Then scroll to the factory. Every pack-level certificate I have worked with names the site where the article was built. If that address belongs to a different plant than the one that will produce your order, or if the supplier moved the line last quarter and never went back to the certification body, the paper still exists. It just stopped describing your supply chain somewhere along the way.

Two standards, two different questions

The way I hold these in my head is that UL 2054 asks a question about the pack as a finished article, and IEC 62133-2 asks a question about cells and about batteries made from those cells, in portable applications. UL 62133-2 is the US adoption of the IEC document with US national differences layered on.

That distinction is not academic. It is why two suppliers quoting the same 48 V pack can hand you two different certificates and both be telling the truth about what they hold. One built to a household or commercial pack scope. One built to a portable-application scope. Neither is lying. Neither document necessarily answers your question.

Which one your program needs is downstream of the end product. A lot of finished-product standards invoke the battery requirement rather than leaving it to the pack maker to choose, and those invoke different battery documents depending on what the product is and where it is sold. That is a decision your OEM's compliance path drives, not something a pack supplier should be picking for you. If a supplier tells you which standard you are "supposed" to use without asking what the pack goes into, that is a supplier selling paperwork, not a supplier managing risk.

UL 62133-2 is not a photocopy of IEC 62133-2

People treat these as interchangeable because the numbers match. They are not. A US adoption carries national differences, and those differences are exactly the kind of thing that gets caught in a review three weeks before a launch.

Practically, this means a report issued to IEC 62133-2 is not automatically usable evidence on a US path, and a UL 62133-2 certificate is not automatically what a reviewer in another market expects to see. If you sell into both, the honest answer is that you may need both documents, or a single evaluation scoped to cover both. That scoping conversation belongs with your testing body and your OEM, early, before the pack design freezes. Trying to bolt it on afterward is how you end up paying for the same testing twice.

A cell certificate does not cover the assembled pack

This is the one that costs the most money when it goes wrong.

A cell maker's certificate attached to a pack quote tells you something real about the cell. It tells you nothing about what happens after the cell is welded into a pack with a protection board, a thermal path, and an enclosure. Pack-level construction, protection behavior, and enclosure design all change the article under evaluation. The cell passed as a cell. The pack is a different thing.

So when a quote comes in with a cell certificate and no pack certificate, the correct move is not to reject it. It is to ask which pack-level certificate covers the assembly, and if the answer is "we're working on it," you now know where you are in that supplier's queue. Sometimes that is fine and the timing works. Sometimes it is a red flag about how they run change control. Either way you want to know now, not at the factory acceptance stage.

If they do send a pack certificate, check that the cell model named on it is the cell you are buying. Cells get replaced with a "same spec" part from another maker more often than anyone advertises, and that substitution can sit outside the basis of the original evaluation.

A test report is not a certificate

They arrive together often enough that buyers stop distinguishing them. They are not the same document and they do not do the same job.

The report is the record of what was tested, to which edition, and what happened. The certificate is the mark, the scope, the model, and the site. A report without a certificate can mean the testing passed but the mark was never issued, or that the file is still open, or that the certificate belongs to the OEM customer rather than the pack maker and cannot be released downstream. All of those are different situations with different risk.

A certificate without a report tells you the mark exists but gives you no window into what was actually evaluated. Both are usually obtainable. Ask for both in the same email. The suppliers who have done this before will send them without being asked twice.

The mark is maintained, not awarded once

A certification mark on a battery pack is not a diploma on a wall. Certifying bodies that issue it typically require periodic follow-up inspections at the manufacturing site to keep it valid. Which means the document has a maintenance history, and that history is part of what you are buying.

So I ask two things beyond the certificate itself: is this the current version, and when was the last factory inspection? Suppliers who live in this world have the answer ready in the same reply. Suppliers who go quiet for four days and come back with a scanned page from two years ago have told you something useful about how they will handle your next change order.

Change control is where coverage actually breaks

This is the part I care about more than the initial certificate.

A certificate covers a configuration. BMS firmware revisions usually are not the trigger, but the BMS board is: different protection IC, different layout, different cutoff behavior. So is the enclosure, if the material or the venting changes. So is the cell model, even a nominal drop-in from a different manufacturer. Any of those can move the pack outside the basis of the original evaluation and require re-evaluation against the standard the certificate was issued to.

What I put in the supply agreement is a line requiring written notice before any change to cell, BMS, or enclosure, plus a plan for re-evaluation before the changed pack ships. That clause is worth more than the certificate, because the certificate describes what was built and the clause governs what gets built next. Suppliers push back on it occasionally. The ones who push back hardest are usually the ones who have been substituting quietly.

The question that gets a real answer

"Are you UL certified?" produces a yes and nothing else. Ask this instead:

For this model number, under which standard and edition, issued to which legal entity, naming which assembly site, and can you send the certificate and the corresponding test report today?

Then read page two.

The standard number is the last thing you confirm, not the first. What you confirm first is whether the document names your pack, built where you are actually buying it, evaluated against a scope that matches what the pack does and where the finished product is sold. When those three line up, the number on the cover page stops being a claim and becomes a description.