Battery Buyers Launch ESCA to Rewrite the Storage Supply Contract
The Energy Storage Contract Alliance has published a buyer-side BESS supply agreement, putting testing, warranties, traceability and cybersecurity into a common procurement framework.
A new battery buyers' alliance is trying to change the document that can decide whether a storage project delivers its promised returns: the supply contract. Launched on October 13, the Energy Storage Contract Alliance (ESCA) has published an open, buyer-side agreement for utility-scale battery energy storage systems. The Swiss non-profit says its members represent more than 40 GWh of battery projects worldwide . Its proposal is not a collective equipment order or a price-setting arrangement. It is a shared starting point for the quality, testing, warranty and data obligations that buyers otherwise negotiate project by project. What changed today 40+ GWh represented by alliance members. Public core contract: free to read and download. 15+ technical appendices: available through membership, covering specifications, testing and warranty schedules. A common contract, not a common price ESCA is based in Lausanne and describes its agreement as a voluntary reference for developers, engineering and construction contractors, independent power producers and asset owners. Buyers and suppliers can adopt it in full, use selected provisions or change the wording. The organization says it takes no part in members' commercial negotiations. That distinction matters. Forty gigawatt-hours is the scale of the members' combined portfolios, not newly contracted demand under this template. Nor does publication show that suppliers have accepted its terms. The immediate news is the availability of a detailed buyer-side document, backed by an organized process for revising it. Sinovoltaics, acting as technical secretariat, drafted the first version. Members can comment on clauses, while the steering committee decides on revisions. Core provisions are public without registration; access to the technical appendices requires membership. That makes the document more accessible than a private project contract, but not every technical schedule is freely available. For smaller developers without a dedicated battery procurement team, a reference agreement could reduce the risk of accepting an equipment supplier's template without recognizing missing protections. Experienced buyers may find more value in comparing definitions and testing requirements across projects. Testing becomes a commercial gate The public model links inspection to shipping, acceptance and payment. Its published clause summary requires inspection of every container rather than sampling containers, and says equipment should not ship without a pass certificate from the buyer's third-party inspector. Factory acceptance testing checks equipment before transport; site acceptance testing validates the installed system. This addresses a practical asymmetry. A defect found at the factory can be corrected before packaging and shipment. The same defect discovered at an operating site may require international replacement logistics, additional labor and another commissioning attempt. Even a relatively inexpensive component can become costly when it prevents the whole battery from meeting a grid-connection deadline. ESCA's public payment example calls for a 10% advance after factory acceptance approval and the remaining 90% within 30 days of final delivery. Its ownership provision places title transfer after successful site acceptance testing. These are proposed contractual terms, not universal market practice or a recommendation suitable for every jurisdiction. The sequencing deserves careful review. Title, transport risk and payment are separate concepts. A developer and its lenders still need to determine who insures equipment at each stage, what happens during a failed test and how obligations interact with delivery terms. A template can make those questions visible without answering every project-specific issue. Warranty language has to match dispatch A battery's rated energy capacity is only one part of its economic performance. Availability, usable capacity and round-trip efficiency determine how much electricity can actually be bought, stored and sold. Definitions can matter as much as the headline percentage: a guarantee covering only battery modules may leave outages in power converters, cooling or controls outside the calculation. The alliance's public explanation emphasizes system-level boundaries, predefined remedies for performance shortfalls and obligations to restore guaranteed performance. It also describes a minimum end-of-warranty usable-capacity floor of 80%, measured against commissioning capacity, with annual testing. That is a model requirement, not evidence that every participating owner's existing batteries carry that guarantee. Operating conditions remain essential. Buyers need the duty cycle, temperature assumptions, state-of-charge limits and energy-throughput allowances to match their intended dispatch. Otherwise, a project can have an impressive warranty on paper while its commercial operating strategy falls outside the covered use case. The buyer's practical test Can the contract turn a measured shortfall into an enforceable remedy, using data the owner can access? A long warranty period alone does not answer that question. Traceability and cybersecurity enter the purchase order ESCA also brings cell provenance and software obligations into procurement. The published summary calls for traceable cell and component origin data within 14 days of the start of each manufacturing batch. It requires verifiable firmware and specifies notification windows for critical vulnerabilities and cybersecurity incidents. Those provisions reflect a battery system's dual role as industrial hardware and a networked control asset. Owners depend on monitoring, remote diagnostics and software updates for years after delivery. The contract is an opportunity to establish what data they receive, how software changes are verified and who responds when a security problem appears. Traceability has a separate financial function. If a recurring failure affects a particular design or manufacturing batch, knowing which cells and components were installed helps identify the exposed population. ESCA's description of its serial-defect approach presumes related units are affected unless the supplier demonstrates otherwise, rather than treating each failure as an isolated warranty claim. These terms will still be negotiated. Suppliers must be able to produce the records and support the response commitments they sign. Buyers need inspection and data-management processes capable of using that information. A clause cannot substitute for operational follow-through. The next test is adoption The alliance's launch shifts attention from equipment price to the allocation of delivery and operating risk. Common language could make bids easier to compare and give lenders a clearer view of technical protections. Those are potential benefits, not measured results from today's release. Evidence of progress would include buyers referencing the model in tenders, suppliers accepting material provisions, and transactions reaching financing with fewer unresolved technical exceptions. The harder test comes later, when an actual defect or performance shortfall reveals whether the inspection records, guarantees and remedies work together. The bottom line: ESCA has supplied a public framework for asking better procurement questions. Its value will depend on what survives negotiation and what owners can enforce after the batteries arrive. Sources and image disclosure Reporting is based on ESCA's October 13 launch announcement and its publicly available model-contract descriptions. Discussion of project economics and adoption tests is CurrentCells analysis. ESCA official contract and governance information · October 13 launch announcement · Public model supply agreement Hero image: AI-generated conceptual illustration commissioned by CurrentCells. It does not depict an ESCA member's actual facility.