-
Start With Your Role, Not a Datasheet
-
Scenario A: You Resell Complete BESS Under Your Own Brand
-
Scenario B: You Integrate Cells or Racks Into a System You Design
-
Scenario C: You Need an Energy Storage System OEM / Private-Label Manufacturing Partner
-
Which Scenario Are You Actually In?
-
My Minimum BESS Specification Checklist
I keep a spreadsheet of my own procurement mistakes. That isn't a personality quirk; it's how I keep myself honest before signing another battery order. Six years sourcing lithium batteries for a regional power equipment distributor, four documented errors, roughly $43,000 in rework, return freight, and overtime service. None of the failures involved bad chemistry. Each one was a specification failure: a footnote I didn't read, a test condition I assumed, or a question I didn't put in writing.
So this BESS specification guide comes from a practical place. I want you to avoid the specific mistakes I made. But before I get into them, there's one thing you need to accept: there is no universal 'best' battery spec. A distributor, a system integrator, and a private-label buyer all need different documentation, and pretending otherwise is how orders go wrong.
Start With Your Role, Not a Datasheet
After years of buying from lithium battery manufacturers, I've simplified every purchase into three scenarios:
- Scenario A — distributor: You resell a finished energy storage system under your brand, but you did not design the internal integration.
- Scenario B — system integrator: You design and assemble the complete system, so you're buying cells or rack-level packs to pair with your own power conversion and controls.
- Scenario C — OEM/private-label buyer: You want a manufacturer to build a system that is functionally yours, under your brand, using your specification.
Here's what I would tell each buyer now, based on the invoices that taught me.
Scenario A: You Resell Complete BESS Under Your Own Brand
If you're a distributor, you probably compare datasheets the way I did at first: cycle life at 6,000 versus 8,000, energy density, cost per kilowatt-hour. Those are easy numbers to compare. They are usually not the numbers that create problems later.
Ask most manufacturers about temperature performance and they will proudly quote discharge down to -20°C. That's what I focused on in one early order. What I missed was a footnote that separated discharge temperature from charge temperature. The battery could discharge in the cold, but it couldn't charge below 0°C without the optional heater package. Our customer's site was cold overnight. The battery ran down, the BMS refused to accept charge in the morning, and we paid for a diesel heater rental plus a service technician to babysit the system until it warmed up. That mistake cost us around $7,400.
Here's the counterintuitive advice for distributors: stop negotiating cycle life until you understand how the BMS behaves in your customers' real environment.
A 6,000-cycle pack that won't charge at the site's winter temperature is worthless on a January morning. Ask what happens at each temperature limit. Does the system shut down? Does it derate? Does it turn on an internal heater? Get those behaviors in writing, not just the pretty temperature range chart.
Also ask for system-level certification documents, not cell-level ones. A cell certificate doesn't cover the cable, the enclosure, or the BMS design. For a complete energy storage system, ask for the UL 9540A test report for your exact configuration, and check whether the installation manual aligns with NFPA 855 requirements for spacing, ventilation, and fire detection (Source: UL 9540A, ul.com; NFPA 855, nfpa.org). If the manufacturer can't explain these documents before you place the PO, that is valuable information.
Scenario B: You Integrate Cells or Racks Into a System You Design
If you're a system integrator, you probably care less about finished enclosures and more about cells, modules, and rack-level packs. Your risk is different: you're matching battery behavior to an inverter you selected, and that requires a deeper level of honesty from the datasheet.
The biggest trap I see is comparing C-rate claims between manufacturers as if they were universal. A claim of '1C continuous' means very little until you know the conditions behind it: ambient temperature, state of charge range, beginning of life or end of life, and whether it was measured at cell level or pack level.
In September 2022, I approved a rack-level pack for a peak-shaving application based on its maximum continuous discharge current. The number looked fine on paper. During our integration test, the pack delivered full current for the first 40 minutes, but as the state of charge dropped, the pack voltage sagged and the inverter hit its minimum DC input voltage earlier than expected. We also saw the BMS throttle current as module temperatures climbed. The datasheet value was technically true—at 25°C and at a controlled state of charge. Our application didn't operate under those conditions.
What I learned: always ask for the measured discharge curve from the manufacturer—actual voltage versus time or state of charge at the current and temperature you plan to use. Model your full operating window with that curve, not with the nominal voltage and maximum current on page one. If the manufacturer won't share measured data because it's 'confidential,' that's a mismatch in expectations before you order.
Scenario C: You Need an Energy Storage System OEM / Private-Label Manufacturing Partner
This is the scenario that most people misunderstand. A lot of buyers think private label means choosing a standard product and putting their brand on it. In reality, if you're selling a custom system with your name on it, you need to decide who owns the detailed specification, who controls the BMS firmware, and what gets documented at the factory.
In September 2023, we approved a private-label batch and the OEM quietly updated the BMS firmware as a 'free improvement' after our approval. The new firmware was good—it was actually smarter about charging—but it wasn't what we had validated. It changed the charge voltage threshold slightly, which meant a small loss in usable capacity compared to the pre-production sample. We caught it during commissioning only because one of our technicians happened to compare firmware versions between units. Correcting it on site cost us about $4,100 and three weeks of project schedule.
That's the part nobody tells you about energy storage system OEM work: the firmware is part of the product specification. We now require that no software or BMS parameter is changed after approval without a formal change request. If a manufacturer argues with that, walk away.
The other lesson from that mistake was traceability. After the firmware incident, we started asking manufacturers how they track production data from cell to finished pack. That's when we decided to move our private-label program to Gotion. We toured the Gotion lithium battery production line in Hefei before signing anything. I wasn't there to admire the automation; I wanted to see whether each cell's capacity and DCIR test data followed through the module build. It did, and that made their incoming inspection reports significantly more useful.
If you're evaluating Gotion Inc or any other lithium battery manufacturer for OEM/private-label work, ask the same questions: Can you trace a module back to its individual cells? Can you provide capacity distribution data for the batch that will go into my order? Are system-level test reports available for the exact configuration I'm buying? You don't need to become a battery engineer, but you do need to make sure the manufacturer can prove what they shipped you is what they promised.
Which Scenario Are You Actually In?
If you're reading this and still unsure which scenario applies, work backward from the acceptance test. Would you accept delivery based on the manufacturer's own test report? If yes, you're probably in Scenario A, buying a finished product. Do you plan to run your own integration testing against your own inverter and controls? Then you're in Scenario B, and you need pack-level data. Does the system need to match a custom specification and carry your brand? Then you're in Scenario C, and your purchase order needs change control, traceability, and firmware documentation.
Many companies sit between scenarios, especially between A and C. If you're in that gray zone, use the stricter requirements from Scenario C. It will force the manufacturer to explain what's standard and what's custom. If the only difference is your logo, the conversation will reveal that quickly.
My Minimum BESS Specification Checklist
After the mistakes I've made, I won't place another order without the following items in writing:
- Operating conditions: highest and lowest ambient temperature, target state of charge range, and required behavior at each limit.
- Cycle life basis: depth of discharge, charge/discharge rate, temperature, and the capacity retention percentage that defines end of life.
- Real performance data: measured discharge curves under load, not just nominal capacity or current.
- Certification package: system-level UL 9540A test report or UL 9540 listing, not cell certificates only.
- BMS documentation: firmware version, parameter access, alarm settings, and a written rule that no changes happen after approval.
- Traceability: batch records from cells to finished modules, including capacity and internal resistance data where available.
That may sound like a lot to request, but honestly, a serious lithium battery manufacturer expects these questions. The suppliers who don't will make you feel unreasonable for asking.
To be transparent, our own private-label program now runs through Gotion's production line, and this checklist is exactly what we used to evaluate them. I don't say that to sell you on one brand. I say it because the questions worked—and they will work whether you're talking to Gotion Inc or any other energy storage system OEM.
Pick your role, ask for the conditions behind every number, and don't let a glossy datasheet do the thinking for you. That's the whole BESS specification guide, really. It's basically a list of questions I wish I'd asked before the first mistake.
