Technical reading

Powin BESS, Chapter 11, and the Lithium Battery Specification Guide: A Buyer's FAQ

A procurement manager's straight answers on Powin's Chapter 11 filing, how to read a BESS catalog and lithium battery spec guide, and where the real costs hide in a storage quote.

What this piece actually answers

I manage energy storage procurement at a 700-person EPC. That's roughly $16M a year in BESS and balance-of-plant spend, seven years of it, and a vendor list that started at 40-something names and is down to 11. I've made every mistake in this article at least once.

These are the seven questions I get from colleagues, from channel partners, and from people who found me on LinkedIn after a project went sideways:

  • Did Powin's Chapter 11 filing kill the Powin BESS pipeline?
  • What does a BESS catalog actually tell you — and what does it hide?
  • How do I read a lithium battery specification guide without drowning?
  • Why does the cheapest quote keep winning the spreadsheet and losing the project?
  • Should I care about a manufacturer's balance sheet, or just the datasheet?
  • OEM and private label: when does it actually save money?
  • What documents do I demand before I sign anything?

No vendor pitch. I buy from these companies, I don't work for them.

1. Did Powin's Chapter 11 filing kill the Powin BESS pipeline?

No, but it changed who you're signing with, and that matters more than the headline.

Powin filed for Chapter 11 protection in mid-2025. Chapter 11 is reorganization, not liquidation — the operating business keeps running under court supervision while claims get sorted out. The assets then moved through a sale process, and FlexGen came out as the acquiring entity. As of early 2026 that's the structure I'm working with when I see a Powin-branded quote cross my desk. Verify the current corporate setup yourself at the docket level; court filings are public, and they're the only source that isn't marketing.

For a buyer, the filing itself is a footnote. The three questions that actually affect your project are:

  1. Who holds the warranty obligation now, and is it backed by a balance sheet or just a PDF?
  2. Who services the installed fleet — same field team, or a new authorized network?
  3. Does the spare parts supply chain survive the transition, and for how long?

I've watched a different manufacturer's restructuring drag a warranty claim out to eleven months. The hardware didn't fail. The paperwork did.

2. What does a BESS catalog actually tell you — and what does it hide?

From the outside, a BESS catalog looks like a complete picture. Enclosure dimensions, nameplate MWh, power rating in MW, C-rate, round-trip efficiency, cycle life. Every manufacturer publishes a version of this, and they all look roughly comparable.

The reality is that catalogs are optimized for comparability, not accuracy. Here's the gap I've learned to check:

  • Nameplate vs. usable capacity. Nameplate is the marketing number. Usable (sometimes called nominal or rated) is the number that shows up in your revenue model. On some products that gap is under 5%. On others it's closer to 12%.
  • Round-trip efficiency at what C-rate. A 92% RTE figure at 0.25C is a different product than 92% at 0.5C.
  • Auxiliary load. HVAC, thermal management, and controls draw power. If it isn't in the spec sheet, it's still on your meter.
  • Warranty throughput caps. Many warranties guarantee energy throughput (MWh) rather than years. Hit the cap early and the remaining years of coverage are decorative.

I built a one-page normalization sheet after getting burned twice on this. Every vendor quote gets transcribed into the same eleven columns before I even look at price. It takes 40 minutes per quote and has saved me more than any negotiation tactic I know.

3. How do I read a lithium battery specification guide without drowning?

Skip the first six pages. That's the company history and the certification logos. Start where the numbers get uncomfortable.

What I actually need out of a lithium battery specification guide:

  • Cell chemistry. LFP or NMC. This drives cycle life, thermal behavior, and how your insurer views the site.
  • Cycle life defined at a specific DoD and temperature. "8,000 cycles" means nothing without those two variables. Ask for the test conditions in writing.
  • DC round-trip efficiency, not AC-to-AC, unless you have the PCS losses documented separately.
  • Degradation curve, not just an end-of-life percentage. A battery that holds 100% for six years and then falls off a cliff is a very different asset than one that degrades linearly.
  • Cell-level test data referenced to IEC 62619. If the vendor cites the standard but won't share a test summary, that's an answer.

Oh, and check the revision date on the spec guide. I've received two quotes in the same quarter referencing two different revisions of the same product datasheet. Nobody flagged it. I only caught it because the cycle life numbers didn't match my notes.

4. Why does the cheapest quote keep winning the spreadsheet and losing the project?

Because the spreadsheet only sees the line items the vendor chose to print.

In 2024 I ran a comparison on two 20 MWh projects — same nameplate, same site conditions, quotes $340K apart. Vendor A was higher. I nearly went with B.

Then I built the TCO model. Vendor B's number excluded EMS licensing (annual), a remote monitoring subscription, augmentation at year 4 rather than year 7, and a warranty that dropped to 5 years instead of 10 on the power conversion side. Over a 15-year horizon the delta flipped — B came in roughly 19% higher. Don't hold me to that exact figure; I'd have to pull the model, but it was in the high teens.

When I put the two total-cost stacks side by side, I finally understood why procurement teams that buy on unit price keep getting overrun approvals rejected. The cheap quote isn't cheaper. It's just shorter.

My rule now: no quote enters the comparison until it's been in the TCO model for 48 hours. Vendors who won't fill out the augmentation and licensing rows don't get a second call.

5. Should I care about a manufacturer's balance sheet, or just the datasheet?

People think a strong datasheet means a safe vendor. It's closer to the reverse: a vendor with a strong balance sheet can afford the engineering, the testing, and the warranty reserves that produce a strong datasheet in the first place.

A 10-year performance warranty is a financial instrument, not a technical one. It's worth exactly what the entity behind it is worth in year eight. That's the lesson the whole Powin Chapter 11 episode put in front of the industry — and honestly, it's the lesson every BESS buyer should have already internalized from the solar inverter shakeouts a decade earlier.

What I check now, beyond the datasheet:

  • Warranty reserve disclosure, if the company publishes it
  • Whether the warranty is insured, escrowed, or backed by a parent guarantee
  • Whether there's a source-code escrow for the EMS (nobody asks about this until the vendor changes hands)
  • Whether the field service network is owned or contracted

For the record: this isn't an argument for avoiding any particular manufacturer. It's an argument for pricing counterparty risk into every quote, including the ones from companies that look invincible today.

6. OEM and private label: when does it actually save money?

Private label saves money when you already have three things: volume, service capability, and a brand you're deliberately building. If any of those is missing, OEM usually costs more than it saves.

Here's my rough filter:

  • Under 5 MWh/year and no field team: buy branded. The margin you'd save goes straight into the service gap.
  • Consistent 20 MWh+/year with in-house commissioning: OEM starts to pencil out, mostly on the post-sale relationship rather than the unit price.
  • Multi-site portfolio with a distributor channel: this is where private label actually compounds, because you control the spec, the spares, and the customer relationship.

At least, that's been my experience with C&I-scale projects. Utility-scale is a different conversation and I'd defer to someone who's closed more of those than I have.

7. What documents do I demand before I sign anything?

This list is non-negotiable at my company. It applies to every manufacturer, including the one with the prettiest BESS catalog.

  • UL 9540 listing certificate for the specific model — a listing, not a "designed to comply with" letter
  • UL 9540A test report summary at the cell, module, unit, and installation level
  • Cell-level test data referenced to IEC 62619
  • NFPA 855 compliance letter written for your specific AHJ jurisdiction (the 2023 edition is widely adopted; a 2026 edition has been in development — confirm which one your authority having jurisdiction enforces before you order)
  • IEEE 1547-2018 interconnection certification if you're connecting to a utility network
  • Certificate of insurance covering the warranty obligation
  • EMS source-code escrow agreement, or at minimum a documented release trigger

That last one is the item nobody asks about until the vendor changes ownership — and then it's usually too late to negotiate. Add it to the contract while you still have leverage.

And on tax credits: the federal incentive landscape shifted in 2025, and I'm not the person to give you a definitive read on it. Ask your tax counsel, not the vendor's sales deck. I've watched two projects get re-underwritten because an incentive assumption came from the wrong source.

8. What I'd do differently if I were sourcing my first BESS today

I'd spend the first two weeks building the TCO model and the normalization sheet before I took a single vendor call. Not after. Before.

I'd ask every manufacturer — including the ones with the best reputation — the same three questions in the same order: Who backs the warranty? Who services the fleet in year seven? What does augmentation cost at year five?

An informed buyer asks sharper questions and closes faster. I'd rather spend twenty minutes walking a colleague through a spec guide than spend six months explaining why a project's economics didn't hold up.

The hardware is mostly good. The contracts and the assumptions are where projects die.