Bundling SAP Modules for Licensing Discounts: Strategy, Tactics and Common Traps

Why SAP Module Bundling Matters More Than Ever in 2026

Enterprise SAP licensing costs are driven by four factors: the number and types of named users, the number and scope of package and engine licences, the maintenance rate applied to all of the above, and the cloud subscription model chosen for future-state deployment. Module bundling — the practice of negotiating multiple SAP products as a single commercial package — affects all four factors and represents one of the most consequential commercial levers available to enterprise buyers.

In 2025 and 2026, the bundling conversation has become more complex. SAP restructured its RISE with SAP private cloud offering in mid-2025, rebranding the Premium tier as SAP Cloud ERP Private Edition and retiring the Premium Plus tier. Advanced AI and automation features that were previously included in higher-tier bundles are now sold as add-ons. At the same time, several previously separate tools — including SAP LeanIX (enterprise architecture), Business Network supplier portal, and elements of the Taulia financial solutions suite — have been added to the base private cloud package.

The commercial implication: what counts as "bundled" in 2026 is different from what counted as bundled in 2024. Buyers who negotiated their SAP estate two years ago may find that their current bundle is either over-paying for features they don't use or under-covered for features they now need. Redress Compliance's work as SAP commercial advisory specialists confirms that 15 to 40% of enterprise SAP spend is recoverable through systematic bundle optimisation without any reduction in business capability.

The Five Categories of SAP Bundling Opportunity

1. Named User Licence Bundling

SAP named user licences exist in a hierarchy: Professional (highest capability and cost), Limited Professional (functional scope restriction), Functional (lower cost, restricted to specific business processes), Employee Self-Service (ESS, restricted to HR self-service), and Worker (warehouse, shop floor, basic access). The bundle opportunity is to negotiate the optimal mix of user types for your actual usage pattern, rather than accepting SAP's default tendency to classify users at the highest applicable tier.

A Professional user licence in S/4HANA costs significantly more than a Limited Professional or Functional user. In a typical enterprise, 15 to 25% of users classified as Professional do not actually execute Professional-scope transactions — they have been classified that way historically, or because their manager requested maximum access, or because SAP's measurement tools default to the highest licence type when multiple roles are assigned. User type right-sizing as part of a bundle negotiation consistently delivers 10 to 20% savings on the named user component of an SAP contract.

2. Engine and Package Licence Bundling

SAP charges separately for Industry Solutions (IS-Retail, IS-Utilities, IS-Banking, etc.), Industry-Specific Engines (Pricing Engine, Output Management, etc.), and Package Licences (HR country packages, localisation packages, etc.). When negotiating new engines or expanding scope, the timing of the entire portfolio matters: adding a new engine in isolation delivers no bundling leverage. Negotiating all current and required engines as a single package deal — timed to a natural renewal window — delivers 20 to 40% better pricing than piecemeal procurement.

One pattern we see repeatedly: a client adds a new industry solution mid-contract, pays list price or a small discount, then renegotiates their base licence two years later without the new engine in scope — because it was added separately. Every new addition should be held for the next major bundle negotiation wherever operationally possible.

3. RISE with SAP Tier and Component Bundling

RISE with SAP is a subscription bundle that includes S/4HANA Cloud Private Edition, SAP BTP credits, Business Network access, and various tools depending on the tier. The bundling opportunity within RISE is to ensure that all components you need are included in the base subscription rather than priced as add-ons, and that the BTP credit allocation is calibrated to your actual Clean Core migration requirements rather than SAP's default inclusion.

The fact SAP would prefer buyers not know: the BTP credit allocation in standard RISE proposals is typically calibrated to generate initial adoption, not to cover an enterprise's actual Clean Core migration needs. A company migrating 100+ Z-code customisations to BTP extensions and integrations will exhaust a standard RISE BTP allocation within 12 to 18 months of go-live. The subsequent overage is billed at list price — which is USD 1.00 per BTP Global Credit versus the USD 0.60 to 0.75 range achievable at contract signing with volume commitment. Negotiate BTP adequacy as part of the initial RISE bundle, not as an afterthought once you're in consumption mode.

4. Line-of-Business Cloud Application Bundling

SAP sells SuccessFactors (HCM), Ariba (procurement), Concur (travel and expense), Fieldglass (external workforce), and SAP Customer Experience (CX/CRM) as separate cloud applications, each with its own pricing model. When an enterprise is in the market for two or more of these applications, bundling them into a single commercial package negotiated at the same time delivers material pricing advantages that cannot be achieved in separate procurement processes.

SuccessFactors is priced per employee per month (PEPM). Ariba is transaction and user based. Concur is per user per month. Fieldglass charges on worker transaction volume. Each of these applications has a separate account team, separate approval chain, and separate pricing structure. Presenting SAP with a combined procurement across multiple LoB applications creates portfolio leverage: your total SAP cloud spend becomes the negotiating anchor rather than each application's individual value.

5. Maintenance and Support Bundling

SAP standard maintenance is priced at 22% of net licence value per year. When negotiating the first contract term — or a renewal — the scope of the licences on which maintenance is calculated matters enormously. Licences that are out of use (shelfware) still attract maintenance fees unless they are formally surrendered. The bundle opportunity is to conduct a shelfware identification exercise before any maintenance renewal, surrender or reclassify unused licences, and negotiate the maintenance rate on the reduced, accurate base.

For companies approaching the 2027 ECC maintenance cliff, the maintenance negotiation takes on additional dimensions. EHP 0-5 mainstream maintenance ended on December 31 2025 — that deadline has already passed. EHP 6-8 mainstream maintenance ends December 31 2027. Extended maintenance from 2028 to 2030 is priced at approximately 24% of licence value — 2 percentage points above standard maintenance, representing a material long-term cost increase. Companies that right-size their licence base before 2027 will pay maintenance on a smaller and more accurate licence footprint going into Extended Maintenance, compounding the benefit of the reclassification.

The Seven Traps That Reduce Bundle Negotiating Power

Trap 1: Signing individual additions mid-contract. Every mid-contract addition is negotiated in isolation, without portfolio leverage, under time pressure. The solution is to accumulate requirements and negotiate them together at the next natural contract window.

Trap 2: Accepting SAP's default user classification. SAP's LAW measurement defaults to the highest applicable licence type when a user has multiple roles. Challenge every user at the highest tier: are they actually executing Professional-scope transactions, or do they simply have the role assigned?

Trap 3: Treating BTP as an afterthought. BTP credits included in RISE are a real asset if sized correctly and a cost trap if undersized. Model Clean Core migration credit requirements before signing RISE, and negotiate adequacy into the initial bundle.

Trap 4: Negotiating LoB applications separately. SuccessFactors, Ariba, Concur, and Fieldglass renewals typically come at different times. Aligning renewal dates and conducting combined negotiations requires planning, but consistently delivers better commercial outcomes than isolated renewals.

Trap 5: Ignoring SAP's fiscal year in timing. SAP's fiscal year ends December 31. Q4 (October–December) is when SAP account teams have maximum discount authority and maximum pressure to close deals. Timing major bundle negotiations to SAP's Q4 gives buyers access to discounts not available in SAP's Q1 or Q2.

Trap 6: Failing to quantify shelfware before negotiating. Maintenance fees apply to all licensed software, used or not. Quantifying and surrendering shelfware before a maintenance renewal reduces the base on which future maintenance — including Extended Maintenance post-2027 — is calculated.

Trap 7: Not modelling the third-party support alternative. Rimini Street and other third-party SAP support providers offer maintenance at up to 50% below SAP's standard rate, covering tax, legal, and regulatory updates. Using the third-party support alternative as a negotiating lever — even without intent to switch — consistently delivers a 3 to 5% reduction in SAP's standard maintenance rate, simply by demonstrating that the buyer has evaluated the alternative.

A Real Bundle Optimisation Pattern

A North American manufacturing enterprise with USD 18M in annual SAP spend engaged Redress Compliance for a full bundle optimisation review ahead of a major renewal. The review identified: 840 Professional users who could be reclassified as Limited Professional or Functional based on actual transaction analysis (USD 2.1M annual saving); three Industry Solution licences that had been added mid-contract at list price and could be renegotiated as part of the renewal bundle (USD 680K saving); USD 4.2M in identified shelfware that was formally surrendered before the renewal, reducing the maintenance base; and SuccessFactors and Fieldglass renewals that were aligned to the SAP core renewal date for combined negotiation (USD 320K saving on LoB blended pricing).

The combined annual saving from the bundle optimisation was USD 3.4M on a USD 18M base — an 18.9% reduction. The maintenance saving on the shelfware surrender, calculated over a five-year horizon at Extended Maintenance rates, added a further USD 1.8M in net present value terms.

The Context: 2027 and the Pressure to Bundle into RISE

SAP's preferred bundle for 2025 and 2026 is RISE with SAP: a single subscription that packages S/4HANA Cloud, BTP, Business Network, and maintenance into a unified commercial construct. For many enterprises, RISE is the right destination. But migrating to RISE is not the only way to optimise SAP module costs before 2027.

According to Gartner data from the end of 2024, only 39% of SAP's approximately 35,000 ECC customers have licensed S/4HANA. The Horváth 2025 survey found that only 37 of 200 surveyed enterprises had completed their migration, with over 60% running over budget and behind schedule. With 17,000 companies projected not ready by 2027, the practical range of options is wider than SAP's account teams present. On-premise consolidation, targeted cloud adoption, RISE at the right terms and timing, and Extended Maintenance with a longer migration runway are all viable options for specific enterprise profiles.

The right bundle depends on your specific licence estate, your integration architecture, your cloud readiness, and your commercial timeline. What is not debatable is that accepting SAP's default bundle — in whatever form it takes — without independent commercial analysis is reliably the most expensive path.