SAP Shelfware Cleanup: Reduce Maintenance and Build Negotiating Leverage

In mature SAP landscapes, licenses accumulate over years that are paid for but never used. That is shelfware. The move to RISE opens a time-limited window to put those licenses to work systematically: as an argument in negotiations, as a lever to reduce your maintenance base, and as a foundation for strengthening your negotiating position. Anyone who misses this governance moment keeps paying the costs without realizing the value.

What Shelfware Is and How It Develops in On-Premises Environments

Shelfware refers to software licenses that are contractually in place and paid for, but that are not used, or barely used, in day-to-day operations. In SAP environments, shelfware rarely results from a single decision. It builds up through the cumulative effect of several developments over many years.

Typical patterns: a company acquires more licenses than actually needed in an expansion round, because demand was still unclear at the time of negotiation. Organizational changes mean that systems or modules intended for certain business units are never fully deployed. Add-ons negotiated as part of a larger contract package are never activated because the implementation project was delayed or never started. Usage rights for product versions that have since been superseded by newer releases remain on the books without ever being formally relinquished.

There is also a structural issue: the maintenance base in SAP contracts is calculated on licensed volume, not on used volume. That means unused licenses generate real maintenance costs without delivering any operational value in return. At an Enterprise Support rate of 22 percent, a license position with a list price of EUR 500,000 carries an annual maintenance fee of EUR 110,000, regardless of whether the associated functionality is ever used.

In practice, organizations that have run SAP for more than ten years often find that shelfware accounts for somewhere between 15 and 40 percent of their maintenance base. The exact figure depends on individual contract history. Without a systematic inventory, that share remains invisible.

Shelfware as a Governance Moment: The Link to Maintenance and the RISE Negotiation

For Directors of SAP Platforms who are now preparing for life after the end of 2027, shelfware is relevant from two directions.

The first governance moment is maintenance base reduction in the context of Extended Maintenance. Starting January 1, 2028, Extended Maintenance takes effect for SAP ERP 6.0 EhP 6-8, adding a two-percentage-point surcharge to the maintenance base of all BS7 Core Applications and Add-ons. Anyone who systematically reduces their maintenance base before that cutoff will carry the surcharge on a smaller number. The example from SAP's public Customer Evolution documentation makes this concrete: a maintenance base of EUR 1,000,000, reduced to EUR 30,000 through targeted relinquishment of unused usage rights, cleanup of ECC Engines already licensed under S/4HANA, and user reductions, generates an annual Extended Maintenance surcharge of EUR 600 instead of EUR 20,000. The difference is dramatic, and it does not come from negotiating skill alone. It comes from a clean inventory of what is actually still needed.

The second governance moment is the RISE negotiation itself. On-premises licenses can be credited against the RISE ACV through the Cloud Extension Program. Three credit types are available: Maintenance Credits, Service Credits, and Cloud Credits. The exact amount is negotiation-dependent, but your position gets stronger the earlier and more precisely you have your own inventory in hand. Shelfware that has been identified and quantified can be brought to the table as additional leverage. Shelfware that remains unknown is neutral in the negotiation, but it is not cost-neutral.

The Time Window: When Shelfware Monetization Is Still Possible

The window for active monetization is limited and follows the maintenance timeline of SAP Business Suite 7.

Through the end of 2027, it is still possible to relinquish unused usage rights and thereby reduce the maintenance base before Extended Maintenance is applied to it. This is the optimal governance moment. Organizations working through their license inventory now can still feed the results into their maintenance contract before the cutoff.

Between 2028 and 2030, during the Extended Maintenance phase, reduction is still possible, but the starting position has changed. The surcharge will already have been applied to unreduced positions for as long as the cleanup was not completed in time.

For organizations considering the Transition Option and enrolling between 2028 and 2030, shelfware is also a relevant factor. The 20-percent surcharge on the price of the comparable SAP ERP Private Edition is not calculated on the original contract volume. It is calculated on the active usage rights at that point in time. A reduced, cleaned-up base translates directly into a lower total amount.

After the end of 2033, when the Transition Option expires, on-premises usage rights lose their eligibility as credits in the RISE context entirely.

Inventory as a Prerequisite: SAP Readiness Check and License Register

Shelfware monetization requires knowing what you have. In practice, that overview is often missing. License contracts are spread across multiple addenda, usage data sits in different systems, and the connection between contracted volume and actual usage has never been systematically established.

Two instruments are central to the inventory process.

The SAP Readiness Check provides technical usage data from the live system: which transactions are active, which business processes are actually in use, which system components are running in production. This data forms the technical foundation for determining which license positions are backed by real usage and which are not.

Your own license register, ideally maintained independently of SAP, covers the contractual side: which products are licensed, in what volume, under what terms, with what maintenance amounts, and on what basis? Without this register, a reliable comparison of contract position versus usage reality is not possible.

Combining these two data sources is the first step in identifying shelfware. In a second step, you assess which unused positions can be relinquished without operational risk. Not every unused license can simply be dropped: emergency scenarios, planned projects, or compliance requirements can give licenses that are not currently in use genuine strategic value.

In a third step, you evaluate the monetization options: maintenance base reduction before Extended Maintenance kicks in, bringing the positions as negotiating leverage into a RISE negotiation, or crediting them through the Cloud Extension Program.

What Shelfware Cannot Do: Limits of Monetization

Shelfware monetization is a governance moment, but it is not a guarantee of any particular negotiating outcome.

Crediting through the Cloud Extension Program is negotiation-dependent. SAP has discretion in how it values credits, and not every license position is credited at the same rate. Add-ons with no direct S/4HANA equivalent, AMS contracts with third-party providers, and maintenance contracts outside the direct SAP agreement are typically not automatically taken into account.

Maintenance base reduction has a direct effect on the maintenance fee, but no effect on already-paid periodic fees. It is prospective, not retroactive.

Shelfware that has been identified but is not actively negotiated stays on the books and continues to generate costs. Inventory alone does not solve the problem. It creates the basis for deciding which positions to relinquish, which to bring in as credits, and which to retain for operational reasons.

Four Governance Moments and Shelfware

Shelfware is not an isolated topic. It touches all four governance moments of ongoing contract management.

In the area of usage, monitoring provides the data that makes shelfware visible: user counts, FUE values, transaction activity, BTP consumption. Without continuous usage tracking, shelfware remains structurally invisible.

In the area of authorizations, you can see where license classes are oversized. Assigning broad roles that trigger higher-value license classes, when actual usage would allow for narrower roles, creates a form of shelfware at the authorization level.

In the area of infrastructure, shelfware affects system sizing assessments. Add-ons that are licensed but not activated do not directly influence sizing, but their presence in the contract affects the starting base for Extended Maintenance calculations and Transition Option evaluations.

In the area of costs, the connection is most direct: shelfware is a cost driver that can be managed through inventory and targeted relinquishment of usage rights. Ongoing contract governance that systematically monitors this area recognizes monetization windows in time and can act on them before the maintenance timeline's deadline chain closes them off.

Next Steps

If you want to know your shelfware share and use the remaining monetization windows before the end of 2027, you need a structured analysis of your own contract and usage data.

The FinOptory Contract Check provides a solid starting point: maintenance base analysis, identification of unused license positions, assessment of credit potential, and an evaluation of your negotiating position ahead of the cutoff. Four weeks, fixed price EUR 7,900.

Request a Contract Check or schedule an initial call.

Further reading: On-Premises License Credits for RISE: Mechanics, Credits, and Negotiating Position and the Hub Page Pillar 7: SAP On-Premises Migration.