Is That UL 2271 File Number Good for Your Robot Pack?

A UL 2271 file number is a claim about one specific pack construction, not a badge that belongs to a supplier, and it is worth exactly what your verification makes it worth. Before you accept it, get the file's product description page, put the model designation, cell part number, BMS part number, and enclosure material in writing beside the number, and then compare that list against the hardware that actually arrives. A file can be real, active, and honestly quoted and still not cover the pack you bought, because the pack you bought runs a second-source cell, a rev-two board, or a model number one digit off from the one that was evaluated. Nobody catches that at receiving. It surfaces eighteen months later in a customer's safety review, with your name on the purchase order.

I have been on the receiving end of that review, and I would rather walk you through the desk work now than talk you through the recovery later.

Start With the Words Above the Number

Open the submittal the way I open it. Skip the cover letter. Find the file number and read the sentence directly above it, because the sentence is doing more work than the number. In practice it says one of three things: "UL 2271 Recognized Component," "UL 2271 Listed," or "tested to UL 2271." Those are three different claims. Only the first two involve a UL file at all. The third usually means a competent lab ran the tests to a UL standard and wrote a report, which can be real and useful work and still will not satisfy a customer whose requirement reads "must be UL certified." I have watched a program lose six weeks to that one word.

Then I type the number into UL Product iQ, the public directory, and read the result screen before I read anything the supplier sent me. Four things on that screen.

The company. Whose file is it? Not the brand on the datasheet, the legal entity that holds the file. If your purchase order is with a trading company, a regional subsidiary, or a contract manufacturer, find out who holds the file and who has authority to authorize changes to it. A file held by an entity you have no contract with is a file you cannot control.

The category and the standard. The directory prints both. If one file number is offered as cover for a UL 2054 pack and a UL 2271 pack, slow down and ask for the category string on each, because those are different standards written for different things. UL 2054 was written for household and commercial batteries. UL 2271 was written for light electric vehicle applications. Neither was written with a warehouse robot in mind, and which one your customer's safety reviewer wants is a question for the customer. I have seen both accepted and I have seen both rejected, and the deciding voice was never mine.

The status. Active, or not. If it is not, stop there and ask why.

The model designations, if the directory shows them. Find yours. If you find a family name instead of a model, note the naming convention, because you will need it in the next step.

What the public screen will not show you is the construction. That lives in the Description of Product section of UL's Follow-Up Service procedure for that file, and it does not come out of a public database. You have to ask the supplier for it, which is exactly why it is the most useful thing you will ask for.

Recognized Component Is Not a Weaker Listing. It Is a Different One.

Recognition means the component was evaluated for use inside a finished product. The mark is the backward UR. For a pack that ships inside a robot, recognition is often the correct designation, because the pack was never going to be evaluated as a standalone consumer product.

What recognition does not do is authorize the pack to go into any machine you like. It authorizes it to go into a machine whose integrator has dealt with the conditions of acceptability. That is you, or your OEM customer.

Listing means the product was evaluated as a complete item. Different mark, different assumption about who owns the surrounding system.

The mismatch to watch for is a customer requirement that says listed when your supplier holds a recognized component file, or the reverse. That is a paperwork problem you can fix before the PO and cannot fix after the fleet is in service. Ask the customer's safety reviewer which designation their requirement actually intends, and get the answer in writing, because "UL 2271 required" on a spec sheet can mean either one depending on who typed it.

Attached to a recognized component file, and sometimes to a listed one, there is a page of conditions of acceptability. It is short, and it is the page everyone skips. It says things like: the pack is suitable for use only when installed in an enclosure acceptable to the end product; the pack was evaluated with the charger named in the report; the maximum ambient is 40 °C; the end product shall provide a means to limit charge current. Each of those sentences moves an obligation onto whoever builds the machine around the pack.

Some of them are benign. Some are job-stoppers. An ambient limit of 40 °C is fine on a datasheet and not fine in a warehouse aisle in July. And if the pack's evaluation assumes the charger that came in the box, the charger is no longer a commodity you can swap in year two to save forty dollars a unit. Read it line by line and write down who is on the hook for each line. If the answer is "the end customer," better to find that out now.

The Description Page Is the Only Place the Construction Lives

When the description page arrives, I do not read it. I check it against the pack. Three items carry most of the risk.

Cells. The page should name the cell manufacturer and model, not just chemistry and form factor. "18650, NMC, 3.5 Ah" is a category, not a construction. If the page names a specific cell, that cell is what was evaluated. Second-sourcing a cell for allocation reasons is the most common way a covered pack quietly becomes an uncovered pack, and it usually happens in year two, after your validation is a memory and the relationship is comfortable.

The BMS. It should be named, ideally by part number and revision. Boards get revised for reasons that have nothing to do with safety: a component goes end-of-life, a connector changes, someone fixes a CAN bug. A revision that moves the charge taper or the cutoff thresholds is not the same construction, and nobody in the supply chain will think to tell you.

The enclosure. The page typically names the material and its flame class, and UL 94 V-0 does not mean any V-0 resin is interchangeable. If the molder changed resin for availability, the new part may still be V-0 and still not be the material in the file.

So do the comparison physically. Put the pack on a bench, photograph the label, read the silkscreen on the board, look inside the housing for a material code. Then put the photo next to the description page and write down every difference, including the ones you think are trivial. The trivial ones are what a reviewer will ask about.

Same Line, Same Cells, Different Model

Certification attaches to a construction, not to a factory, a line, or a relationship. A 48 V 20 Ah pack and a 48 V 40 Ah pack built by the same people on the same equipment are covered by the same file only if the file says they are. Sometimes it does, as a family, and that is fine. Sometimes it does not, and the fact that the second one is "the same thing, bigger" is a manufacturing opinion, not a certification finding.

So the question is never "is your pack UL 2271?" The question is "is this part number, as built, covered by this file?" If the answer comes back as "they're all the same family," ask to see how the family is defined on the description page. If your designation is printed there, you are done. If it is not, you are buying an uncovered pack from a supplier with a covered pack in the catalog, and no amount of history between you closes that gap.

The Pack File Is Not the Robot's Certification

This one causes the most avoidable friction, because two companies each think the other one owns it.

The pack supplier holds the file on the pack. That file supports, and does not replace, whatever evaluation your robot's end product needs. If your customer is a distribution center operator with a safety team, their reviewer is going to open their own file and ask you for evidence. What they want is small and standard: the certificate or directory entry, the description page, the conditions of acceptability, and a statement naming the part number they are buying.

Send those four things in one packet and you save a two-week round trip. Send a marketing brochure with a file number on the back and you will spend the next month explaining what a recognized component is to someone who already knows, and who is starting to wonder about you.

What to Request, and What a Slow Answer Tells You

The package I ask for, in the order I ask for it:

1. The current Product iQ entry or certificate, showing file number, holding company, standard, and status.
2. The Description of Product page from the Follow-Up Service procedure, showing our part number and the critical components.
3. The conditions of acceptability page, complete and not excerpted.
4. The authorization to mark page, which is the supplier's permission to apply the mark and which tells you whether they mark in-house or at a contract site.
5. Cell documentation: manufacturer, model, and the cell's own certification reference.
6. A signed coverage letter, dated, from someone with authority, stating that the part number we are buying is covered by file number X as of that date.

Item six is the one people skip and the one I care about most, because it converts a marketing claim into a statement a supplier has to stand behind. Two sentences on letterhead. If a supplier will not sign it, that is your answer.

Turnaround is information too. A supplier who owns the file and has been through a customer audit pulls the directory entry and the conditions page the same day and the description page within a couple of days. Two weeks of "checking with the factory" means the file may be held somewhere else, or that the people selling to you have never opened it. Neither is fatal. Both are things to know in sourcing rather than in service.

The Things That Should Make You Stop

A file number that changes between documents. A certificate that turns out to be self-issued, because a PDF with a house logo and a compliance statement is not a UL certificate, and I have seen both printed on the same paper stock. A file that appears on the brochure and nowhere in the formal submittal. A supplier who cannot name the legal entity holding the file. A model number that was "updated" since the quote without anyone mentioning it.

None of these prove anything is wrong. They tell you the documentation is not under control, and if the documentation is not under control, the change you most need to hear about is the change you will hear about last.

One limitation worth stating plainly: none of this tells you the pack is well designed. Verifying a file number tells you whether the claim is true and whether it covers your hardware. Whether the pack is any good is a different question with a different set of tests, and a perfect file does not answer it.

What a clean verification gets you is a sentence you can say in a review without flinching. The file is active. The holder is the company we contract with. The description page names our part number and the cell, board, and housing we actually receive. The conditions of acceptability are ones our machine meets. And the supplier signed that in writing on a date. That is not exciting. It is defensible, which is what you need it to be eighteen months from now.