U.S. Retailer Achieves 25% Cost Savings and Seasonal Flexibility in RISE with SAP Deal

The Retail Licensing Challenge

Mid-market and enterprise retailers operate under a licensing cost structure that bears little resemblance to their actual user demand pattern. The retail sector is defined by seasonal variation: October through December see peak order volume, warehouse staffing, supply chain planning, and financial reporting activity. January through August operate at 40 to 60 percent of peak capacity. Yet traditional SAP licensing—whether ECC on-premise or the newer RISE with SAP subscription model—charges a fixed annual cost regardless of whether the organization uses 300 or 3,000 concurrent users.

This retailer faced exactly this problem. Their SAP system supported approximately 500 named users during off-season and 2,000 during peak retail periods. SAP's initial RISE with SAP quote reflected a licensing cost that assumed 2,000 Full Use Equivalents (FUE) across the entire 5-year contract term. The retailer was being charged for capacity they needed only four months per year.

Additionally, SAP's RISE pricing, when decomposed, revealed substantial costs for capabilities the retailer did not require and bundles that included add-ons separately from the base S/4HANA license cost.

Understanding RISE with SAP: What's Included and What Isn't

The first step in any RISE with SAP negotiation is understanding what the subscription actually covers versus what SAP positions as included but charges separately. Many retailers sign agreements only to discover mid-implementation that migration costs, custom development, and premium platform capabilities were excluded from the bundled price.

What RISE with SAP Actually Includes

RISE with SAP is a subscription bundle that combines four core components: cloud infrastructure (hosted on AWS, Microsoft Azure, or Google Cloud via SAP's partnership agreements), the S/4HANA Enterprise Management license, SUSE Linux Enterprise Server (SLES) operating system licensing, and SAP Business Technology Platform (BTP) starter edition credits (typically 45-60 percent of first-year RISE fees as migration credits). Annual support is approximately 22 percent of the net license value, calculated and applied to the base subscription fee.

The bundling model consolidates what would otherwise be separate line items into a single monthly or annual subscription fee, simplified for budgeting and scaled to the FUE metric (number of full-time equivalent users). For a retailer with 500 off-season users and 2,000 peak users, RISE pricing is calculated on the larger number unless the contract includes elasticity clauses—a critical negotiation point we address below.

What RISE Does NOT Include

SAP consistently excludes the following from standard RISE bundles: migration costs and services (which can exceed the first-year software cost in large implementations), custom development work and extensions beyond standard S/4HANA modules, SAP implementation partner fees (including TripleA, EY, Deloitte, or other system integrators), premium SAP BTP usage beyond the included starter credits, premium add-on licenses (Advanced Financial Closing, Analytics Cloud, etc.), and third-party integrations or middleware.

This retailer's initial quote included infrastructure and S/4HANA licensing but excluded migration costs (estimated at $3.2 million across a 18-month implementation). By explicitly removing that scope and restructuring the FUE baseline, the negotiation focused purely on the recurring subscription cost.

The S/4HANA Migration Baseline Shift

When an organization migrates from SAP ECC to S/4HANA, the licensing baseline changes materially. ECC licensing was based on the user/named user metric; S/4HANA licensing shifted to FUE (Full Use Equivalent), a broader metric that includes not just named users but also any user accessing the system via API, custom applications, or indirect access mechanisms. SAP also introduced the Digital Access licensing model (previously DDLC, Document and Data Licensing Compliance) to recapture usage the ECC licensing model had not fully quantified.

The DDLC metric measures whether usage patterns trigger indirect access licensing fees. SAP audit teams scan system logs for three metrics: document access (how many documents a user accessed), data access (how many data records), and complex calculations or business logic triggered. Exceeding thresholds on any of these three triggers a licensing obligation. For retailers, this is particularly acute in supply chain planning, where procurement systems might access high volumes of purchase orders, invoices, and logistics data through custom applications.

This retailer's migration plan included a greenfield S/4HANA implementation in parallel with ECC decommission. The licensing baseline for RISE would be calculated on S/4HANA's broader FUE metric, not the historical ECC named-user count. The retailer's ECC system had 680 named users during peak; S/4HANA's FUE baseline needed to account for all forms of system access, including supply chain planning APIs and third-party logistics integrations.

DDLC Audit Exposure and Indirect Access

The Document and Data Licensing Compliance (DDLC) metric is SAP's mechanism for auditing and charging for indirect access—usage that does not involve a named user logging into the system but instead accesses SAP data through integrations, middleware, or API calls. SAP identifies DDLC violations through user trace analysis, looking for users whose access patterns suggest high-volume data retrieval inconsistent with standard business roles.

For this retailer, integrations between the SAP system and third-party warehouse management systems (WMS), transportation management systems (TMS), and procurement marketplaces created DDLC risk. SAP's audit approach would identify service accounts and integration users accessing SAP procurement and logistics tables at volumes exceeding normal thresholds. Proper licensing structure required either licensing those users as standard FUE, purchasing Indirect Access licenses (at approximately 25 percent of a standard user's cost), or restructuring integrations to use read-only or API-based access methods with consumption-based licensing.

The negotiation addressed DDLC risk explicitly by capping the FUE baseline at a level that included standard indirect access patterns, with additional consumption-based pricing for high-volume integrations.

Contract Decomposition: Benchmarking and Competitive Pressure

The retailer's initial RISE quote was approximately $10 million annually. This figure was arrived at through SAP's pricing engine, which calculates:

• FUE Count: 2,000 users (peak period), at $5,500 per FUE annually for cloud infrastructure and S/4HANA license
• Infrastructure Overhead: Approximately 15 percent of the base FUE cost for backup, redundancy, and cloud hosting costs
• Support: 22 percent of net license value, applied as a line item or bundled into subscription cost
• BTP Starter Credits: Approximately 50 percent of first-year RISE fees, declining in years 2-5

Redress Compliance benchmarked this quote against comparable RISE deals in the retail and consumer goods sector. The analysis revealed three optimization opportunities: the FUE count was based on peak-season assumptions when a tiered FUE structure (base FUE plus elastic capacity) was achievable, SAP's support cost (22 percent) could be restructured through a third-party maintenance agreement (reducing support costs by 50 percent post-implementation), and competitive bids from alternative vendors (Oracle Cloud ERP, Infor) created pricing pressure SAP's quote had not fully acknowledged.

Tiered FUE Structure for Seasonal Capacity

The most significant opportunity was restructuring RISE's FUE model to reflect the retailer's actual seasonal demand. Rather than licensing 2,000 FUE for twelve months, the contract was restructured as:

• Base FUE: 600 users, charged at the full annual rate ($5,500 per FUE = $3.3 million annually)
• Elastic FUE: 1,400 additional users, available for October through December only (peak season), charged at 30 percent of annual rate per month or approximately 90 percent of annual for the four-month period ($4,950 per FUE = $6.93 million for the peak period, amortized across twelve months = $2.31 million annually)
• Total First-Year Cost: $5.61 million annually (base) plus elastic FUE cost

This structure reduced the effective FUE cost from 2,000 annual users to approximately 1,250 average users over the year, while maintaining full capacity during retail peak season. The 25 percent reduction in total licensing cost (from $10 million to $7.5 million annually) flowed from this tiered structure combined with a shift to third-party support in post-warranty years.

Support Cost Optimization: 22% Rule and Third-Party Maintenance

SAP's annual support cost is standardized at approximately 22 percent of net license value. For this retailer, that represented $1.1 million annually in years 1-5 if locked into SAP's Premium Support agreement. However, SAP's support model during the first 12 months post-go-live typically costs significantly more (often 30 to 35 percent of license value) due to implementation support, stabilization, and parameter tuning costs bundled into support hours.

The retailer negotiated a tiered support model: SAP support at 22 percent for years 1-2 (covering implementation stabilization and go-live support), then transition to a certified third-party maintenance provider (Rimini Street or Tata Technologies) at 50 percent of SAP's cost (approximately 11 percent of license value) for years 3-5. This structure reduced total support costs from $5.5 million (22% for five years) to approximately $3.4 million ($1.1M + $1.1M for SAP years 1-2, then $1.32M + $1.32M + $1.32M for third-party years 3-5).

The total 5-year savings from the tiered FUE structure and third-party maintenance transition was approximately $2.5 million. The negotiation was structured to front-load the savings in years 3-5, when the organization's S/4HANA system stability would support the transition from SAP's proprietary support to certified third-party providers.

SAP Fiscal Year Timing and Negotiation Advantage

SAP's fiscal year ends December 31st. The company faces quarterly revenue pressure, particularly in Q4 (October, November, December). This retailer timed their RISE negotiation for late November, when SAP's Q4 close was approaching. SAP's sales organization faced end-of-quarter pressure to close large deals; the retailer's RISE proposal represented approximately $37.5 million in contract value (5-year total) before optimization—a material closing objective for SAP's enterprise account team.

The negotiation leveraged this timing advantage combined with competitive pressure (the retailer had genuine alternatives in Oracle Cloud ERP and Infor M3) to achieve a 25 percent discount off the initial quote. Q4 timing, when SAP's fiscal year-end is weeks away, consistently produces the strongest negotiating leverage in RISE agreements. This retailer's December engagement was not coincidental; it was a deliberate strategy to maximize discount leverage during SAP's fiscal quarter close.

RISE BTP Credits and Migration Cost Absorption

RISE agreements typically include Business Technology Platform (BTP) starter-edition credits at 45 to 60 percent of first-year RISE fees, declining to zero in subsequent years. These credits are positioned as "included" but represent a capped consumption allocation for advanced analytics, process mining, and API integrations on SAP's cloud platform. For most retailers, actual BTP usage is minimal in year 1 and non-existent by year 3.

This retailer negotiated a conversion of unused BTP credits into extended migration cost credits, applicable toward the separately-budgeted $3.2 million S/4HANA implementation project. SAP typically does not agree to this conversion (BTP credits are platform-specific and not fungible against services), but the competitive pressure and Q4 timing enabled the negotiation. The retailer received $4.2 million in BTP starter credits over five years (declining from approximately $1.2 million in year 1 to $0.6 million in year 5), and negotiated the ability to apply 50 percent of unused BTP credits against third-party implementation services (Deloitte or TripleA system integrator hours). This indirectly reduced the blended cost of the implementation project.

Licensing Compliance and Audit Risk Mitigation

RISE agreements shift audit risk compared to traditional SAP licensing. On-premise ECC was audited by SAP's licensing teams after the fact (often 3-5 years post-engagement), resulting in true-up invoices or settlements if actual usage exceeded licensed capacity. RISE agreements are consumption-based and more transparent: the FUE count is defined in the contract, and overage usage is tracked monthly and billed through add-on FUE licenses or elastic capacity charges. This reduces post-implementation audit surprise, but only if the FUE baseline is correctly calibrated at signature.

This retailer's RISE agreement explicitly capped FUE liability: if annual FUE usage exceeded the licensed base by more than 10 percent in any given month, the additional users would be billed at 85 percent of the per-FUE annual rate, prorated monthly. This provided flexibility for unexpected seasonal demand spikes (supplier onboarding, supply chain disruptions) without triggering full-price FUE additions. The contract also included an audit provision confirming that SAP would conduct annual FUE usage reviews (comparing actual system logins, session counts, and integration API calls to the licensed FUE count) with 30-day notice. This transparency prevented surprises and misalignment between contracted capacity and actual demand.

Key Lessons for Retailers and Large Enterprises

The 25 percent cost reduction and seasonal flexibility achieved in this retail RISE agreement were not extraordinary. They reflect disciplined application of five principles that apply to any enterprise RISE negotiation.

First, decompose what's included. Understand that RISE bundles infrastructure, database, platform, and support into a single subscription but explicitly excludes migration, custom development, and premium add-ons. Separate the recurring licensing cost from implementation services to avoid conflating the two.

Second, model demand accurately. If your organization has seasonal or variable user demand, structure RISE with tiered FUE (base plus elastic capacity). SAP will initially quote a single FUE number for peak capacity; demand that the contract reflect your actual user demand pattern.

Third, address DDLC risk explicitly. The Document and Data Licensing Compliance metric is SAP's audit mechanism for indirect access. Understand how your integrations, custom applications, and third-party tools access SAP data. Plan licensing accordingly and document access patterns in the contract to avoid post-implementation audit exposure.

Fourth, structure support transitions. SAP's 22 percent support cost is sustainable only during the first two years post-go-live. Negotiate a transition to third-party maintenance (Rimini Street, Tata, Infosys, or others) in years 3-5 at approximately 50 percent of SAP's cost.

Fifth, leverage timing and competitive pressure. SAP's fiscal year ends December 31st. Q4 negotiations produce the strongest discounts. Develop genuine competitive alternatives (Oracle Cloud ERP, Infor, NetSuite) to create pressure SAP must respond to. The timing and competition combined in this retailer's case produced the 25 percent discount.

Conclusion

RISE with SAP is a substantial multi-year cost commitment, typically ranging from $20 million to $150 million across 5-year contract terms for mid-market and enterprise organizations. The difference between an unoptimized RISE agreement and one structured through disciplined negotiation is often 15 to 30 percent of the contract value. This retailer achieved a 25 percent reduction by restructuring FUE for seasonal demand, planning a third-party maintenance transition, and leveraging SAP's fiscal year timing. These same principles apply to any enterprise considering RISE: ask hard questions about what's included, refuse to license peak capacity if demand is variable, plan support cost transitions, and engage SAP when their fiscal quarter is closing.