BESS Revenue Stacking Example for Business

A battery should not be assessed as a single-purpose asset. A credible BESS revenue stacking example shows how one system can reduce electricity costs across different operating windows while protecting critical loads when reliability matters. For commercial and industrial sites, the strongest business case is usually built from controlled energy cost reduction, peak demand management, solar self-consumption, and operational resilience.

Key takeaways

• Revenue stacking combines compatible battery value streams without assigning the same stored energy to two uses at once.
• Demand charge reduction is often the most predictable source of value for facilities with sharp, recurring peaks.
• Solar shifting can improve the value of on-site PV by moving surplus daytime generation into higher-value evening consumption.
• A financial model must account for battery efficiency, degradation, dispatch limits, and the value of keeping reserve capacity for critical operations.

What revenue stacking means for a BESS

Revenue stacking is the practice of earning or creating value from multiple battery applications rather than relying on a single one. The word “revenue” can be slightly misleading in a behind-the-meter project. Much of the value is not cash paid to the site owner. It is avoided electricity cost, avoided peak charges, reduced generator use, and reduced production risk during an interruption.

The key discipline is dispatch priority. A battery cannot fully discharge to shave a late-afternoon demand peak and simultaneously remain fully available as backup power. Nor should a battery charge from the grid at an off-peak rate if that prevents it from capturing surplus solar generation later that day. A good control strategy makes those decisions in advance, then adapts to actual site load, solar output, tariff periods, and battery state of charge.

For a manufacturing plant, warehouse, cold-storage facility, retail center, or large landed property with meaningful electricity use, the stack commonly starts with demand management and energy shifting. Solar charging, backup capability, and flexible load control can then be added when the site profile supports them.

A practical BESS revenue stacking example

Consider a factory with a 1 MW / 2 MWh battery and an existing rooftop solar system. Its electricity demand rises sharply from 4:30 p.m. to 7:00 p.m. as machinery, cooling systems, and loading equipment operate at the same time. It also has excess solar output around midday on lower-production days.

The battery controller reserves part of its capacity for a recurring evening peak. On a typical day, it charges with surplus solar first. If solar generation is insufficient, it may charge during a lower-cost period, provided the forecast shows that the later savings exceed the cost of charging and the expected efficiency losses.

Assume the battery discharges 600 kW during the site’s highest-demand interval. If that action reduces billed peak demand by 600 kW and the monthly demand charge is RM35 per kW, the estimated value is RM21,000 per month, or RM252,000 per year. This is often the foundation of the stack because it is tied to a measurable site load pattern.

Next, the system shifts energy from lower-value periods into higher-value consumption. Assume 1.2 MWh is discharged on 300 operating days. With a 90% round-trip efficiency, delivering 1.2 MWh requires approximately 1.33 MWh of charging energy. If the lower-cost energy is RM0.55 per kWh and the displaced higher-cost energy is RM0.85 per kWh, the gross daily energy margin is about RM287. Across 300 days, that equals roughly RM86,000 annually.

A third layer comes from solar self-consumption. Suppose the battery captures 250 MWh each year that would otherwise have low value at the moment it is generated. If using that energy later is worth an additional RM0.30 per kWh compared with the alternative, the solar-shifting contribution is approximately RM75,000 a year.

Together, the illustrative gross annual operating value is about RM413,000: RM252,000 from demand management, RM86,000 from energy shifting, and RM75,000 from improved solar self-consumption. These figures are examples, not a promised outcome. They depend on the site’s actual tariff structure, load shape, operating calendar, solar profile, and the battery’s available capacity.

Most importantly, the three value streams must be scheduled rather than double counted. In this example, the controller prioritizes solar charging during midday, holds sufficient charge for the evening peak, and uses grid charging only when there is enough capacity and forecast value remaining after those priorities are met.

Where the financial model can go wrong

An attractive spreadsheet can become unreliable when it assumes a battery is available at full capacity every day. Usable energy is lower than nameplate energy because operators maintain a state-of-charge buffer, account for conversion losses, and avoid overly aggressive cycling that can accelerate degradation. A 2 MWh battery is not automatically 2 MWh of daily dispatchable value.

Demand reduction also depends on timing. A battery that discharges before the actual site peak may save energy but fail to reduce the highest demand interval. This is why interval data matters more than a monthly bill total. The engineering team needs to identify when peaks occur, how long they last, whether they repeat, and which equipment drives them.

Resilience presents another trade-off. A site that needs one hour of backup for essential refrigeration, security, servers, or process controls should reserve capacity for that purpose. That reserve lowers the energy available for daily cost optimization, but it may be the most valuable part of the system during an outage. The correct decision depends on the cost of disruption, not simply the electricity rate.

Battery degradation must also be included. More cycling can produce more short-term savings, but it can reduce available capacity over time. An optimized operating plan sets limits around depth of discharge, charging power, discharge power, and reserve capacity. It should also be reviewed as the facility expands, shifts production hours, or adds solar capacity.

Turning the example into an operating plan

A BESS project begins with high-resolution electricity usage data, solar generation data where applicable, and a clear definition of critical loads. From there, engineers model a range of dispatch cases rather than relying on a single best-case scenario. Conservative, expected, and high-value cases give decision-makers a more useful view of payback and risk.

The next step is selecting the battery power and energy rating. Power, measured in kW or MW, determines how much demand can be reduced at a given moment. Energy, measured in kWh or MWh, determines how long that reduction can be sustained. A site with a short, severe spike may need higher power and less duration. A site aiming to move several hours of solar generation into the evening may need more energy capacity.

The control layer is where stacking becomes real. Forecast-based controls should anticipate solar output and site demand, set an appropriate reserve, and adjust battery dispatch as conditions change. Monitoring should verify not only battery performance but also whether the expected demand reduction and energy savings are appearing on the utility bill.

Amsolar approaches battery optimization as an engineering and financial decision, combining site analysis, system design, monitoring, and operating logic to measure value after commissioning. For businesses that prefer to preserve capital, a BESS as a Service structure can also shift attention from equipment ownership to the performance outcome and monthly cash flow.

The best battery project is not the one with the most value streams listed on paper. It is the one with a dispatch plan that consistently delivers measurable value, protects the loads that matter, and remains credible after efficiency losses and operating constraints are included.