Client Profile
The client is a Paris-headquartered luxury goods conglomerate with operations across fashion, leather goods, perfumes, cosmetics, watches, jewellery, wines, and spirits. Its portfolio spans more than 75 luxury brands across more than 5,000 retail locations worldwide, with annual revenues in excess of €80 billion. The Oracle technology estate had been built through a combination of organic deployment and brand acquisition, with Oracle Retail Xstore POS, Oracle Database, Oracle E-Business Suite, and Oracle Middleware featuring prominently across multiple brand subsidiaries.
The group's centralised IT function — responsible for shared infrastructure, group-wide ERP, and technology governance across all brands — had undertaken a multi-year programme of IT consolidation following several significant acquisitions. As part of this consolidation, it became apparent that Oracle licence obligations across the group significantly exceeded current deployment requirements. Multiple brands had Oracle licences on the group support schedule for products that had been superseded, decommissioned, or were no longer deployed in active configurations.
The Challenge
The primary challenge in this engagement was the scale and complexity of the Oracle estate. Oracle licences had been acquired by individual brand subsidiaries over a period of fifteen years, under separate commercial agreements, with varying support terms and product coverage. When the group's IT governance function attempted to rationalise the estate under a single Oracle Master Agreement structure, it discovered that the complexity of the existing arrangements — combined with Oracle's aggressive position on transfer and consolidation terms — made straightforward rationalisation commercially difficult.
Specific challenges included Oracle Database Options licences held by subsidiary brands that had been acquired through acquisition and were no longer in active use but were contractually committed to the group support obligation. Oracle Retail licences for POS configurations that had been superseded by more recent Xstore deployments — but where the old licences remained on the support schedule because the termination process had not been completed. And a set of Oracle E-Business Suite licences at the group level that were over-licensed relative to actual module deployment, reflecting historical purchasing decisions made before a significant restructuring of the group's finance function.
The financial scale of the problem was significant: an internal estimate suggested that 25–30% of the group's total Oracle support obligation — approximately €3.5M annually — was attributable to licences that did not correspond to active deployments. The question was how to confirm that estimate precisely, identify the exact licences, and execute termination without triggering Oracle repricing provisions or creating compliance exposure for the retained estate.
The Approach
Redress Compliance structured the engagement as a phased, three-year programme. The phased structure was deliberate: the complexity of the estate, the number of Oracle contracts in scope, and the operational sensitivity of the retail environment meant that attempting to rationalise the entire estate simultaneously carried unacceptable execution risk.
Phase 1 (Year 1) focused on the clearest and most commercially straightforward termination opportunities: Oracle Database Options held by subsidiary brands where the options were demonstrably not deployed, and Oracle Retail licences for decommissioned POS systems. This phase did not require complex commercial negotiation — the licences were simply not in use and could be terminated without repricing risk once deployment evidence was confirmed. Phase 1 generated €3.2M in Year 1 annual savings.
Phase 2 (Year 2) addressed the Oracle E-Business Suite over-licencing at the group level. This required a combination of deployment verification — confirming the actual module deployment versus the licensed scope — and commercial negotiation with Oracle to agree a reduced support base. The negotiation was complex because Oracle's commercial team initially resisted the reduction, citing contractual provisions that required 30 days' notice before the next support anniversary. Redress Compliance's intervention in that commercial discussion — presenting deployment evidence and making the case on the contractual terms — secured a support reduction of €2.8M annually from Year 2.
Phase 3 (Year 3) completed the rationalisation of Oracle Middleware licences across subsidiary brands, where multiple brands had independently licensed Oracle Fusion Middleware, Oracle Service Bus, and Oracle WebLogic Server for deployments that had since been migrated to cloud-native integration platforms. This phase required the most complex commercial management — navigating Oracle's stance on licence transfer within the corporate group — but ultimately achieved a further €4.5M in cumulative three-year savings by restructuring the Middleware licence footprint around active deployments only.
The Outcome
Over three years, the programme eliminated €10.5M in Oracle support costs across the group, reducing the total Oracle support obligation by approximately 30% from its pre-engagement level. The savings were distributed across product families: €4.2M on Database and Database Options terminations, €2.8M on EBS support reduction, and €3.5M on Middleware rationalisation.
The programme was executed without any Oracle audit findings. All terminations were documented with deployment evidence and confirmed by Oracle in writing. The group's relationship with Oracle was maintained — the client continued to invest in Oracle OCI for selected workloads and remained a significant Oracle customer. The programme was positioned not as a hostile reduction exercise but as a responsible governance initiative, which allowed the Oracle commercial relationship to remain constructive throughout.
An additional outcome of the programme was the establishment of an internal Oracle licence management governance process within the group IT function — a process that had not existed previously. This process, which includes annual deployment reviews and proactive shelfware identification, is expected to prevent the recurrence of the licence accumulation pattern that created the original problem.
Key Takeaways
Enterprise organisations built through acquisition face a specific and often underestimated Oracle cost challenge. Each acquired brand brings its own Oracle contracts, and the natural tendency — particularly during periods of rapid acquisition — is to defer licence consolidation rather than disrupt operational systems. This deferral compounds over time, creating licence estates where a significant fraction of the support obligation has no corresponding operational value.
A phased approach to rationalisation is the correct strategy for complex, multi-entity Oracle estates. Attempting comprehensive rationalisation in a single step increases execution risk and can trigger commercial provisions that eliminate anticipated savings. A structured programme — prioritising the clearest termination opportunities first and building commercial negotiating credibility with Oracle through demonstrated success — produces better outcomes over a three-year horizon than a single aggressive intervention.
The commercial dynamics of Oracle licence termination are manageable with specialist guidance. Oracle's initial resistance to support reduction is consistent and predictable. Sustained engagement, backed by deployment evidence and contractual analysis, produces outcomes that Oracle's initial position would not suggest are achievable.
Independent Oracle estate rationalisation. Buyer-side only. We map, audit, and execute support reduction programmes across complex multi-entity environments.