PROJECT INSIGHT

BESS Compliance Requirements: Which Scenario Are You Actually In?

Compliance Isn't a Checklist. It's a Scenario.

I've been buying battery cells and BESS containers for about six years now. Cumulative spend somewhere in the $4M–$6M range, though honestly I'd have to pull the exact number from our tracking system—and half the early invoices aren't even in there because we were still using spreadsheets for the first eighteen months.

Every RFP I've written says "compliance." Every vendor's spec sheet says "compliant." And yet two months later, some buyer in my network is posting about a shipment stuck at port because someone assumed UN 38.3 covered the whole story.

Here's the thing: compliance means wildly different things depending on what you're actually building. A distributor selling into a regulated market needs a different paper stack than an integrator assembling cabinets. And a private-label buyer needs something different again.

This was accurate as of early 2025. Compliance frameworks move, so verify current standard versions before locking down a BOM.

So instead of giving you a single “BESS compliance checklist” (which would almost certainly be wrong for at least two-thirds of you reading this), let me split this into the three scenarios I keep seeing in real procurement decks.

Scenario A: You're a Distributor Selling into Regulated Markets

You buy finished containers or racks and resell into the EU, U.S., UK, or Australia. Your customer is the end-user, or close to it.

Your compliance burden is the heaviest because you're the last stop before a regulator, an insurer, or a fire marshal asks for paperwork.

What you actually need:

  • Cell-level: IEC 62619, and for transport, UN 38.3 test summaries (not just a declaration letter)
  • Module and system level: UL 1973 for modules, UL 9540 for the integrated system
  • For U.S. installs: UL 9540A thermal runaway test data — insurers have started requiring the actual report, not a summary
  • Site-level: NFPA 855 for installation spacing and fire suppression design
  • EU-facing: EU Battery Regulation (EU) 2023/1542 — carbon footprint declarations and battery passports kick in on a rolling schedule

The pitfall nobody warns you about: a vendor saying "our cells are UL certified" is not the same as a certified system. I made that mistake in my first year—or rather, I almost made it. Cost me a two-week delay and a very awkward call with our legal team. The cell cert exists. The system cert often doesn't.

If you're evaluating a supplier here, one concrete question: “Can you send me the UL 9540 certificate number, or just the 9540A report?” Vendors with a real system-level listing answer in seconds. Everyone else pivots to talking about cell quality.

On cost: system-level certifications add real money—think five figures per SKU in engineering and testing, amortized over volume. Some suppliers build that into the price; others hide it in change orders. Ask upfront.

Scenario B: You're a Systems Integrator

You take cells or modules and design the cabinet, thermal management, BMS logic, and enclosure yourself. You own the system-level certification under your own name.

This is the scenario where compliance gets counterintuitive.

Conventional wisdom says buy from a supplier with the fullest certification stack. But if you're the one doing the UL 9540 listing, a supplier's existing system-level cert doesn't help you—it just raises the price. What you actually want is clean cell-level documentation and a supplier willing to share test data.

Priorities shift to:

  • Cell batch traceability — can they map a serial number back to a manufacturing lot and a test record?
  • Stable MSDS and UN 38.3 updates without renegotiation
  • Engineering responsiveness — do they answer questions from your test lab, or do they route everything through sales?
  • Consistent chemistry — switching cell variants mid-project is the fastest way to invalidate your own test data

I've never fully understood why some cell manufacturers treat technical Q&A like a trade secret. My best guess is that their engineering teams are overloaded and the sales gate-keeping is a buffer, not a policy. Either way, it costs buyers time.

If you're using a supplier with in-house cell manufacturing—like Gotion, which runs cell production out of its Hefei headquarters and assembly in Illinois and Michigan—you get a shorter documentation loop. That matters when your test lab needs a revision to the datasheet at 11 p.m. before a submission deadline.

The trade-off: you take on more design risk. Own it.

Scenario C: You're Running a Private Label or OEM Program

Your logo goes on the enclosure. Your brand carries the warranty. You need a manufacturing partner who can white-label the hardware and hand over the compliance documentation in a shape your legal team can actually use.

This is where the negotiation gets interesting, and where I've watched two colleagues get burned.

Questions that matter more than the price-per-kWh conversation:

  • Whose name appears on the UL file? Can it be transferred, licensed, or dual-listed?
  • Will the manufacturer provide editable versions of the datasheets, install manuals, and safety documentation so you can rebrand? Or do you get locked PDFs?
  • If you later switch suppliers, does the certification survive? (Usually not. Budget for re-certification on any major supplier change.)
  • Are there language and labeling requirements for your target markets baked into the OEM agreement?

Here's where the industry has genuinely changed. Five years ago, if you wanted a private-label BESS, you bought from a trading company that sourced from a factory you'd never visit. Today, several tier-one manufacturers offer direct OEM programs with proper document licensing.

It's still not easy. But it's a real option now, which it kind of wasn't in 2020.

Which Scenario Are You In?

Three quick questions. Be honest with yourself.

One: Does your name end up on the system nameplate?
If yes, you're in Scenario B or C. If your supplier's brand stays on the box, you're A or B.

Two: Are you designing the cabinet, or buying it whole?
Designing → B. Buying whole and reselling → A. Buying whole and relabeling → C.

Three: Who fields the call when an insurer asks for test data?
If it's you, you need the full paper trail. If it's the manufacturer, verify that they'll actually show up—get it in writing.

To be fair, plenty of companies blur across two scenarios. A distributor with a small integration team. An OEM that also does direct sales. That's fine—just don't assume your compliance requirements average out. They stack. You get the heavier of the two, not the lighter.

Personally, I'd argue the single most expensive compliance mistake in this industry isn't buying non-compliant hardware. It's buying compliant hardware with paperwork that doesn't match your scenario. The hardware works fine. The audit doesn't.

If you're evaluating manufacturers for a BESS program this year, start with the scenario question before the spec sheet. The paper trail is cheaper to sort out upfront than after the container's on the water.