Client Profile
The client is a UK-based retail group operating across more than 300 stores nationally, with a combined annual turnover exceeding £2.5 billion. The organisation employs approximately 22,000 staff and supports a complex IT environment that evolved significantly through a series of acquisitions over the preceding decade. Its Oracle estate included Oracle Database Enterprise Edition running core finance and supply chain applications, Oracle E-Business Suite modules covering accounts payable, general ledger, and inventory management, and a portfolio of Oracle Middleware and identity management products from legacy integration projects.
The combined Oracle software and support spend had grown steadily to approximately £1.15 million per year. A significant portion of this cost was consumed by Oracle's standard 22% annual support fee, applied to the full licence value regardless of actual product usage. The organisation had never conducted a formal reconciliation of its Oracle licence entitlements against actual deployment since the completion of its most recent acquisition four years prior.
The Challenge
The immediate trigger for the engagement was a technology review initiated by the group's newly appointed Chief Technology Officer. The review identified Oracle support as the second-largest single line item in the IT operating budget and challenged the organisation to justify the cost in light of its current product usage. Initial analysis by the internal IT team suggested that several Oracle products included in the support agreement had not been actively used since the completion of an ERP consolidation programme two years earlier, but the team lacked the technical capability to produce a formal deployment inventory or navigate Oracle's contractual mechanisms for licence termination.
Oracle's standard support contract structure creates a deliberate barrier to cost reduction. Once a support agreement is in place, Oracle requires formal termination notices for individual licence sets with specific lead times, and does not permit retroactive termination for products that were technically deployed but functionally inactive. The organisation's procurement team needed to establish both which products could be legitimately terminated and the correct contractual process to ensure that any termination did not inadvertently create compliance gaps in the remaining estate.
A further consideration was the technology roadmap. The group had no plans to upgrade its Oracle E-Business Suite environment — the current version had been stable for six years and no Oracle upgrade was required or planned. This meant the primary driver of Oracle support value — access to product updates and new releases — held negligible value for the majority of the Oracle estate, raising the question of whether third-party support could provide equivalent functional coverage at materially lower cost.
The Approach
Redress Compliance conducted a comprehensive Oracle licence reconciliation as the first phase of the engagement. Working with the organisation's database administrators and application owners, the team produced a full inventory of Oracle products with active deployment evidence, including processor counts, named user counts, and last-access dates for Oracle Database and E-Business Suite components.
The reconciliation identified three distinct categories of Oracle entitlement. The first category — active and business-critical products — covered Oracle Database Enterprise Edition on six production servers and eight active E-Business Suite module licences. The second category — dormant but technically deployed products — covered two Oracle Identity Management licences, one Oracle Business Intelligence installation, and several Oracle Middleware components that had been retained in the environment without active use. The third category — fully inactive products — covered four Oracle Fusion Middleware licences for a point-to-point integration layer that had been decommissioned during the ERP consolidation.
For the fully inactive products in the third category, Redress structured a formal licence termination notification under Oracle's contractual terms. For the dormant second-category products, Redress negotiated a partial termination combined with a true-down of the support agreement to reflect only the retained active footprint. This process required careful management of Oracle's account team to avoid triggering a broader licence review — a risk that exists whenever an organisation seeks to reduce its Oracle commercial footprint.
For the remaining active estate — Oracle Database on production servers and core E-Business Suite modules — Redress evaluated the business case for third-party support. Given the organisation's confirmed position of no planned Oracle upgrades for a minimum of three years, the risk profile of third-party support was assessed as low. The transition to a third-party support provider was executed over a 60-day period, covering patch management processes, Oracle Critical Patch Update equivalency, and escalation procedures for production incidents.
The Outcome
The combination of licence terminations and the transition to third-party support reduced the group's annual Oracle support spend from £1.15 million to £555,000 — a reduction of 52%. The saving of £595,000 per year compounded over three years to deliver £1.785 million in cumulative cost reduction, and the organisation maintained this level of support coverage without any Oracle audit findings or escalated incidents during the engagement period and subsequent review windows.
The organisation also recovered budget that had previously been locked in unproductive Oracle support fees and reallocated it to a cloud-native commerce platform initiative that had been deferred due to funding constraints. The Oracle support cost reduction directly enabled a strategic technology investment that would not otherwise have been possible within the existing IT budget envelope.
Key Takeaways
- Shelfware is almost always present in mature Oracle estates. Organisations that have grown through acquisition, platform consolidation, or technology refresh cycles routinely carry Oracle licences for products that are no longer deployed. A formal reconciliation reliably identifies 20–40% of the estate as candidates for termination or reduction.
- Third-party support is a viable option for stable, non-upgrading Oracle environments. Organisations with no Oracle upgrade plans within a two-to-three year horizon typically derive minimal value from Oracle's standard support contract beyond break-fix coverage. Third-party providers deliver equivalent functional coverage at 45–55% of Oracle's rate.
- Reducing Oracle support requires contractual precision. Oracle's termination and true-down mechanisms have defined processes and timing requirements. Engaging without expert knowledge of these contractual mechanics risks creating compliance exposure rather than resolving it.
- Savings recapture can fund strategic investment. The most compelling outcome in this engagement was not the cost reduction in isolation but the reallocation of recovered budget to a strategic initiative. Optimised Oracle spend is a source of strategic capital, not merely an operational efficiency.
Overpaying for Oracle support on products you no longer use?
Redress Compliance can audit your Oracle estate and identify termination and third-party support opportunities.