SAP shelfware swap and credit tactics

Shelfware is the SAP industry term for licences a customer has purchased but does not use. Every long-tenured SAP estate carries some shelfware; estates that have run through a major transformation, an acquisition, or a since-cancelled product programme typically carry a great deal of it. The shelfware is paying maintenance every year, contributing to the audit baseline, and crowding the buyer’s ability to negotiate fresh capacity at renewal. SAP’s standard position is that shelfware is non-refundable, non-transferable, and non-convertible. The standard position is the starting point of the negotiation, not the ending point. Across our 500+ engagements, structured shelfware swaps have generated commercial credit equivalent to 8-18 per cent of total SAP spend in the conversion event, which on a midsize estate is $6-22M of recovered value.

What “shelfware” really is

Shelfware in an SAP context comes in three categories. The first is over-purchased named-user capacity: licences the buyer purchased in anticipation of growth that did not happen, or for projects that were cancelled, or as part of a volume-discount stack that exceeded actual need. The second is unused module licences: components such as Hybris, Cloud for Customer, or specific industry-vertical modules that were purchased and never deployed. The third is engine-based shelfware: utility-metric licences (Payroll Calculations, Document Volume, HANA cores) that were sized on a forecast that turned out wrong.

Each category requires a different swap model. Named-user shelfware is the easiest to convert because the licence type is fungible across the SAP price list. Module shelfware is harder because the modules are not directly fungible. Engine shelfware is hardest because the engines are valued on a different basis.

Swap model one: like-for-like exchange

The like-for-like exchange swaps unused capacity in one product for new capacity in a different product on the same SAP price list. The mechanism is a credit at the SAP-side discount rate of the unused licence, applied against the new purchase at the new licence’s contractual discount rate. Like-for-like exchanges work because SAP’s revenue recognition treats the exchange as an internal accounting adjustment rather than as a refund, which is the trigger SAP’s commercial team is most resistant to.

The credits are typically discounted on transfer. A 100-Professional-licence shelfware position on a contract carrying 55 per cent discount might transfer to a new SuccessFactors purchase at 70 per cent of the like-for-like value. The transfer discount is the negotiation. We have seen transfers at 60-90 per cent of like-for-like value, with the variance driven by the strategic importance of the new purchase. The pattern is described in our competitive leverage article.

Swap model two: credit at renewal

The credit-at-renewal model converts shelfware into a discount applied to the next year’s licence and maintenance fees. The mechanism is simpler than the like-for-like exchange because it stays within the existing contract scope. SAP’s commercial team treats the credit as a discount adjustment rather than as a refund, which keeps it within the revenue-recognition rules.

The credit values are typically lower than the like-for-like equivalent, in the 40-60 per cent range of the underlying shelfware value. The model works best when the buyer has a near-term renewal event and a defensible measurement of the shelfware position. The renewal-timing dynamics that make credit-at-renewal viable are described in the renewal timing article.

Swap model three: RISE conversion bundle

The RISE conversion bundle is the most powerful swap model and the most under-used. When a buyer is converting from on-premise SAP to RISE, the conversion contract re-papers the entire SAP estate, and shelfware can be bundled into the conversion as a credit against the RISE contract value. The credit value in this model is typically 70-95 per cent of the underlying shelfware, because SAP’s commercial team is motivated to land the RISE conversion and is willing to absorb the credit cost in service of that goal.

The RISE conversion bundle requires careful sequencing. The shelfware position has to be measured and documented before the RISE conversation begins; otherwise, SAP’s sizing of RISE bakes the shelfware into the conversion price and the buyer loses the credit lever. The discipline is described in our RISE conversion negotiation article and in the SAP RISE topic page.

Sizing the shelfware position defensibly

Every swap model depends on a defensible shelfware position. The position is measured as the gap between contractually-owned capacity and demonstrated use over a defined window. The window we recommend is twelve months for named users, twenty-four months for modules, and the full prior fiscal year for engine-based licences. Demonstrated use comes from the USMM consolidation for named users, transaction-code logs for modules, and the engine measurement schedules for engine licences.

The position must be defensible because SAP’s commercial team will challenge any swap proposal that exceeds the documented unused capacity. The SAP License Optimization Framework white paper sets out the sizing methodology, with worked examples across each licence category.

What SAP will and will not accept

SAP’s commercial team will accept like-for-like exchanges into strategic new products, credit-at-renewal for measurable shelfware in the recent purchase history, and RISE conversion bundles where the conversion value exceeds the shelfware credit. SAP’s commercial team will not accept refund requests, cash-out conversions, or swaps into products outside the existing licence agreement’s scope.

The shape of an acceptable proposal is therefore predictable. The buyer leads with a strategic purchase or transaction event, documents the shelfware position alongside, and proposes the swap as part of the broader commercial conversation. Leading with the shelfware position alone — without a corresponding purchase — almost never works. The shelfware is the credit; the new purchase is the debit; SAP’s commercial team needs both sides of the ledger to authorise the transaction.

The audit settlement case

Audit settlements are an under-used venue for shelfware swaps. When a buyer is settling an SAP audit, the negotiation typically focuses on the disputed compliance figure. The unused capacity in the same estate is rarely brought to the table. It should be. Across our 500+ engagements, audit settlements that incorporated a documented shelfware position closed at 18-31 per cent lower total cost than equivalent settlements that did not. The pattern is described in the global manufacturer case file.

The mechanism is to size the shelfware before the position paper is delivered and to include the swap as part of the proposed resolution structure in the paper’s fourth section. The shelfware credit is netted against the audit finding, the residual is the cash settlement, and the contractual structure of the swap is documented in the settlement amendment. The discipline is described in our post-audit settlement tactics article.

What to watch for in the swap language

Three drafting traps appear in shelfware swap language. The first is the “maintenance-base preservation” clause that SAP’s legal team frequently inserts, which requires the buyer to continue paying maintenance on the swapped-out licences at the prior rate. The clause makes the swap value largely illusory and should be struck. The second is the “equivalent-licence-class” restriction, which requires the new licence to be of the same or lower class than the swapped-out licence. The restriction reduces strategic flexibility and should be replaced with a value-equivalence test.

The third is the “single-event” restriction, which prohibits subsequent swaps within a defined period. The restriction is the most subtle of the three because it does not affect the immediate swap, but it eliminates the lever for the next renewal cycle. The right replacement language is a recurring swap right with documented evidence, refreshed at each renewal.

If you have not sized your shelfware position in the past twelve months, the priority is to extract the licence-versus-use gap across the estate. The first conversation is at no cost. Our SAP contract negotiation service describes how we structure the swap engagements.