I get some version of this question every week: "What should I look for when evaluating BESS manufacturers?"
Honestly, the answer I give depends entirely on who's asking. A distributor who needs four containers landed by March has completely different evaluation criteria than a developer planning a 40 MWh site for Q4 2026. A private-label buyer building their own brand? Different again.
So instead of handing you one checklist that half of you won't use, let me split this into three situations. Figure out which one you're in, and skip the other two sections.
One thing before we start. This reflects how I've been evaluating suppliers through early 2025. The market moves fast — Tesla Energy alone deployed 31.4 GWh in 2024, more than double its 2023 total, according to the company's own shareholder reporting — so verify anything specific before you build a budget around it.
The three buyer profiles
Here's the split I use when someone asks me for a sourcing recommendation:
- The rush buyer — you have a signed delivery commitment or a customer waiting, usually inside 4 to 10 weeks.
- The project developer — you have a 12- to 18-month pipeline and you're sizing systems before contracts are locked.
- The private-label / OEM buyer — you're selling under your own brand and need a manufacturing partner, not a one-off supplier.
These overlap more than people admit, but the primary evaluation criteria don't. Let me walk through each one.
Scenario 1: The rush buyer (4–10 week window)
This is my home turf. When I'm triaging a rush order, I'm not comparing spec sheets — I'm verifying inventory that actually exists and can actually move.
What matters in this scenario, in order:
- Verified production dates, not datasheet dates. A datasheet tells you what a cell is rated for. It doesn't tell you when the cell was made. Ask for the serial number range and the manufacturing date code on the physical cells. If a supplier can't produce that, they're reselling, not manufacturing.
- BMS firmware version and update path. I've seen projects get held up because the BMS firmware shipped on a batch was two revisions behind and wouldn't talk to the site controller. Ask for the exact firmware version and how updates are pushed.
- Realistic lead time, in writing. Not "about 5 weeks." I want a scheduled ship date and a named logistics contact. A quote that arrives in 2 hours but can't produce a delivery schedule in 2 days is a red flag, not a fast vendor.
- Cell-to-pack documentation. UL 9540A test reports, IEC 62619 certificates for the cells, and — critically — documentation tying the specific cells in your order to those certs.
UL 9540A is the test method used to evaluate thermal runaway fire propagation in energy storage systems. It's not optional anymore for most utility-scale deployments in North America. If a supplier can't walk you through their UL 9540A results in a call, that's a signal.
Last September, a client needed eight containers of ~5 MWh units delivered to Rotterdam in five weeks. Normal turnaround on that volume was 8–10 weeks. We found a manufacturer with cells already in bonded storage, paid roughly 12% over their standard rate in expedite fees, and delivered in 32 days. The client's alternative was a $200k+ liquidated damages clause on the downstream EPC. That math isn't close.
The trade-off in this scenario: you'll pay more, you'll have less customization room, and your QC sample size is smaller. Accept all three. The deadline is the constraint — everything else is negotiable.
Scenario 2: The project developer (12–18 month pipeline)
This is where people get the most wrong. Developers compare $/kWh like it's a commodity — and it isn't, not even close.
I went back and forth between two suppliers on a mid-size pipeline last year for almost three weeks. One had a $/kWh advantage of about 8%. The other had a stronger augmentation warranty and, more importantly, published a degradation curve I could actually audit. On paper, the cheaper one won. My gut said the warranty was worth more over a 15-year asset life. I went with the one with the warranty, and I'd make the same call again.
What to actually evaluate here:
- Cycle life and the conditions attached to it. "8,000 cycles" means nothing without the depth-of-discharge, temperature, and C-rate assumptions. Get the warranty document, not the marketing sheet.
- Augmentation roadmap. How does the supplier handle cell degradation over years 8 through 15? Do they have an augmentation SKU that fits the same rack? If not, you're buying a system that becomes un-serviceable at year 8.
- Firmware maintenance commitment. Who patches CVEs on the BMS in 2032? If the answer is "our team," ask how big that team is and where it's based.
- Spare parts availability window. Ten years, minimum. Get it in the supply agreement.
Bottom line: compare total cost of ownership, not header price. A $110/kWh pack with a 5-year firmware commitment from a vendor who'll be around is cheaper than an $95/kWh pack from a firm that may not answer email in 2029.
Scenario 3: The private-label / OEM buyer
Different game entirely. Here the question isn't "can they build a good pack" — plenty of factories can. It's "can they build my pack, consistently, without exposing my brand to their mistakes."
Three things I'd check before signing anything:
- Firmware customizability. Can they flash your brand ID, custom comms protocol, and your own telemetry endpoint into the BMS? If the answer is "no, but our app is nice," walk. Your customers need to see your infrastructure, not theirs.
- MOQ reality vs. MOQ quote. A 20-unit MOQ is often 200 in practice once you account for cell batching. Ask what happens if you order 20: do they pull from existing stock (which means you get whatever cells they had) or run a dedicated batch (which means you pay the real setup)?
- IP indemnification. If a cell supplier sues over a patent issue in your branded pack, who carries that? If the answer isn't in writing and signed, it's you. Not them.
The scenario where this goes wrong: brand gets established, orders scale, and then the manufacturer realizes they can just ship the same product under their own label at a lower price. Fix that in the exclusivity and non-compete clauses before you ship the first container, not after.
How to tell which one you actually are
I'll admit — plenty of buyers are hybrids. But you usually have one dominant mode. Ask yourself:
- Do you have a signed delivery date or a customer waiting? → You're a rush buyer. Lead with Scenario 1 criteria, treat everything else as secondary.
- Are you sizing systems that aren't contracted yet? → You're a developer. Scenario 2 applies. Don't let procurement optimize for price — optimize for warranty enforceability.
- Do you already have buyers asking for a product under your brand? → You're an OEM buyer. Scenario 3. Slow down; get the legal and firmware work done first.
If I remember correctly, the last time someone told me they were "all three," they were actually a distributor doing light OEM work with a rush order on top. That happens. In that case, run Scenario 1 criteria first — because nothing else matters if the container misses the boat — and layer in Scenario 3 protections over the following two contract cycles.
This isn't a clean decision tree, and I'd be lying if I said it was. What I can tell you, from coordinating rush energy storage orders for the better part of a decade, is that the worst evaluations happen when a buyer applies the wrong scenario's checklist. Developers optimizing for lead time waste money. Rush buyers optimizing for TCO miss deadlines. OEM buyers optimizing for price build a brand on someone else's factory floor — and they don't find out until it matters.
Pick your scenario. Then commit to the criteria that actually belong to it.
