ESS OEM/ODM: Customization at Cell, Module and System Levels

Certification guides, sourcing checklists and market notes for ESS buyers

ESS OEM/ODM: Customization at Cell, Module and System Levels

Cell, module and system-level customization under NDA: where branding stops, where engineering starts, and what capacity stands behind both.

ESS OEM/ODM: Customization at Cell, Module and System Levels

Every storage supplier offers OEM and ODM. The useful question is not whether customisation is possible but at which level, because cell, module and system customisation carry entirely different tooling costs, lead times and questions of design ownership. A programme that starts at the wrong level either pays for engineering it does not need or discovers, at certification, that the customisation it bought was cosmetic.

What OEM and ODM mean in storage

OEM usually means the product exists and your brand goes on it: enclosure finish, label, packaging, documentation, sometimes a market-specific configuration. ODM means the product is developed around your specification: voltage, capacity, interface, enclosure geometry, firmware behaviour. In practice most first programmes are OEM at the system level with a small amount of ODM at the module level, and that combination is usually the right one.

The distinction that matters commercially is who owns the design record. Under ODM, the specification you paid to develop should remain yours, which is why the NDA and the design-ownership clause are not paperwork — they are the asset.

System level: enclosure, branding, configuration

Most partners start here because it is the fastest path to a sellable product. You choose a proven platform — wall-mounted residential, stackable residential, all-in-one, portable — and customise what the market sees: enclosure finish and colour, your brand on the fascia, packaging and documentation in your language, and a configuration matched to the destination market's grid and certification requirements.

Two things should be fixed before the first unit is built. The branding scope: what is yours, what stays neutral, what appears on the rating label. And the BMS configuration: which protection functions are enabled, what the default parameters are, and whether the installer can change them in the field. A branded product whose protection settings cannot be documented per market is a support problem waiting to happen.

The private-label programme sets out how the branding and configuration scope is documented under NDA on proven platforms.

Module level: voltage and interface

Module-level ODM is where a storage programme becomes specific. Pack voltage, capacity per module, mechanical interface and communication protocol are defined around your inverter, your cabinet or your device rather than around a catalogue. This is the level at which a distributor stops reselling a product and starts owning a range.

The engineering discipline that makes it safe is validation: a custom module should go through the same performance, lifecycle and safety testing as a catalogue product, on the same equipment. A module developed for your specification but validated only by simulation is a prototype, whatever the purchase order says. Ask which tests ran, on what equipment, and request the reports.

See the battery module range for the catalogue starting points that most module-level programmes adapt.

Cell level: the real factory test

True cell-level customisation only exists where cells are actually manufactured. Capacity, chemistry mix, electrode design and format are all fixed at the cell line, and no amount of pack engineering can change them afterwards.

This is where capacity claims meet reality. Yaoqian BESS operates LFP cell production alongside PACK assembly on one base — 5 GWh of cell and 6 GWh of PACK output per year, manufacturing since 2019 — with jigs and traceability from cell lot to finished pack. A supplier that buys cells can offer you a different cell from a different maker; it cannot adjust the cell.

Cell-level work is also the slowest and most capital-intensive form of customisation, so it belongs in a programme's second or third year, once the market has told you which specification is worth tooling. Starting there is the most common way a new brand spends its first year in development instead of in the market.

BMS and firmware: where customisation usually costs money

Firmware is the least visible and most expensive customisation. Changing protection thresholds is configuration; adding a communication protocol, a state-of-charge reporting behaviour or a new inverter integration is development, with a validation cycle behind it.

Budget for it explicitly. A custom BMS integration usually consumes more engineering time than an enclosure change and produces nothing a customer can see, which is why it is frequently deferred and then discovered to be necessary. The custom BMS page covers what is configuration and what is development.

Certification ownership: who owns the test reports

This is the question that decides whether a private label is an asset or a liability. When a product is rebranded, someone has to own the safety and transport certifications for the branded model. If the reports are issued to the manufacturer's model number and your label is a sticker, then in a dispute or a customs query the chain of evidence points at the manufacturer, not at you.

Establish at signature: which certifications will be issued for the branded model, who holds them, who maintains them through annual audits, and what happens to the certificate if the partnership ends. For transport, the UN38.3 summary must match the pack model being shipped — a rebadged model needs its own documentation.

Tooling, MOQ and timeline by level

The practical numbers, as quoted for portable and stackable families: MOQ from 100 units, samples within two weeks of specification sign-off, and container-scale production from the same cell and PACK lines. Tooling and engineering change the timeline at the module and cell levels; at the system level, branding and configuration usually fit inside the sample window.

A worked sequence for a first programme: agree the platform and branding (weeks one to two), sign the NDA and the design-ownership schedule, receive samples and test them, place a pilot order at the 100-unit floor, then use the pilot's market feedback to specify the module-level changes for year two. That order keeps the cash commitment low while the specification is still moving.

Choosing a level for your first year

Start at the system level unless there is a specific reason not to. It gets a branded product into your market within a quarter, proves the channel, and generates the feedback that tells you which module-level change is worth paying for. Reserve cell-level conversations for a programme that has volume to justify tooling.

The exception is a product where the interface is the business — an inverter manufacturer integrating a battery, or an equipment maker building storage into a machine. There, module-level customisation from the start is the point, and the programme should be scoped as development rather than as procurement.

Yaoqian BESS offers OEM/ODM from cell to system level from its Shenzhen base, with MOQ from 100 units, samples within two weeks of sign-off and design ownership documented under NDA. Send your specification for a customisation proposal, or review the manufacturing capabilities behind the programme.