VPPs shift dispatch control. They combine distributed generation and storage, coordinate assets through a central system, and trade in wholesale or ancillary service markets as one large generation unit. For operators with modest solar and battery portfolios, aggregators offer a straightforward route to market: surrender dispatch control, take a revenue share, and avoid direct market participation.
That description leaves out a significant concession. Before signing, independent operators should establish what dispatch control covers, how their revenue share is calculated, and when aggregation outperforms direct market participation.
What dispatch control actually means in practice
In a VPP agreement, the aggregator's system sends charge and discharge instructions to your assets. Your battery follows its dispatch algorithm, at the times and for the purposes it selects. The aggregator serves as the BRP, the Balance Responsible Party, for the combined portfolio.
This is a material operational issue. Portfolio optimization seeks maximum aggregate revenue, so your site's SoC path, local grid tariff, and delivery-zone intraday price profile may receive less weight. The algorithm can dispatch your battery when that is unfavorable for your site, because the action supports an aggregate position held across many assets.
Operators may ask to override dispatch on particular days. Usually they cannot, or they can do so only conditionally and with penalties. The aggregator has sold the combined capacity to market counterparties, so honoring one operator's preference could breach its own commitments.
Revenue share models and what they obscure
VPP contracts generally define a revenue share, with the operator receiving a percentage of revenue from the asset's participation. That percentage varies widely, from roughly 60 percent to 90 percent, based on the aggregator, market, and services involved.
The percentage says little about how total revenue is determined. In ancillary markets such as frequency response or reactive power, revenue per unit of battery capacity can exceed spot arbitrage in some periods and fall well below it in others. Where the aggregator pursues spread arbitrage across the pool, allocation depends on which assets it dispatches in which windows and how clearing revenue returns to each asset.
Compare projected annual revenue per kWh of usable battery capacity under the VPP agreement with the result available from direct intraday price arbitrage using automated dispatch. That requires clear asset-level attribution reporting, which some aggregators do not provide. Request historical asset-level revenue data from comparable participants before signing.
The markets where VPP participation makes genuine sense
VPP participation is not always the wrong choice. Aggregation can produce outcomes that independent operators cannot reproduce when certain conditions apply.
Ancillary service access is the clearest example. European frequency containment reserve and frequency restoration reserve markets typically set participant minimums, often 1 to 5 MW. A single 15 kWh residential battery cannot enter directly. An aggregator can include sub-threshold assets in a VPP pool. If ancillary revenue per kWh exceeds independently achievable intraday arbitrage revenue, aggregation wins economically.
Settlement simplification is another real benefit. Direct participation needs a BRP arrangement, metering that supplies 15-minute settlement data, and continual reconciliation of imbalance charges. For operators with only a few sites, that infrastructure may cost too much. VPP aggregators take on the settlement work within their service.
Contract terms that matter more than the headline revenue share
Before signing, focus on the provisions that shape long-term results, not only those highlighted in commercial negotiations.
Check exclusivity: can the agreement block other markets or a later move to direct participation? Check lock-in: what is the commitment period, and what exit terms apply if independent dispatch becomes preferable? Check data access: will you receive detailed dispatch logs and revenue attribution by asset, or only a monthly total without the calculation behind it?
Review minimum availability requirements closely. Many VPP contracts require a minimum battery SoC and availability threshold, with penalties deducted from the revenue share when the threshold is missed. Assess the operating duties imposed on you and whether your site-management capacity can meet them, an issue often overlooked during sales discussions.
What changes as portfolio size increases
The economics change as the portfolio expands. A 3-site portfolio gives an operator little negotiating power, carries greater direct-access overhead per site, and may contain batteries too small to justify dispatch software costs individually. At this stage, VPP participation is more attractive.
A 20-site portfolio averaging 15 kWh per site equals 300 kWh of aggregated capacity. Direct-participation setup costs are distributed across more sites, aggregate capacity nears minimums for some ancillary markets, and retaining the full arbitrage margin begins to exceed an aggregator's revenue share materially.
There is no universal transition point. It varies with the market, available aggregator terms, and the alternative's dispatch costs. Operators who signed with a small portfolio and have since expanded should reassess regularly. Terms that worked at five sites may not suit thirty.
Retaining optionality
Protecting optionality is the key structural consideration in a VPP agreement. Signing a long-term exclusive contract before understanding portfolio growth can lock you into a revenue model that becomes less suitable as scale and market conditions change.
Where possible, choose shorter initial terms with renewal options instead of multi-year lock-ins. Seek exit clauses permitting asset removal with reasonable notice, without a contractual buyout. Require data clauses covering the asset-level telemetry and dispatch logs needed to assess alternatives over time.
The VPP model is not inherently wrong for independent operators. It is a route to market suited to particular conditions. The error is accepting it by default instead of comparing it rigorously with direct dispatch, as with any other operating decision.
