Executive Summary
New Look is a major fashion retailer headquartered in the United Kingdom, operating over 500 stores with a substantial e-commerce platform and thousands of employees globally. The company's retail technology infrastructure relies on Oracle Database for point-of-sale, inventory management, and e-commerce systems, and Oracle Java SE deployed across servers and in-store devices.
An internal compliance review in 2024 revealed significant Oracle licensing risks across both Java SE and Database. Oracle's new Java SE licensing model created unexpected subscription requirements across New Look's extensive Java footprint. Meanwhile, Oracle Databases running on VMware without hard partitioning exposed the company to cluster-wide licensing claims. Oracle's account team proposed a solution: sign a multi-million-dollar Unlimited Licence Agreement (ULA) and an enterprise-wide Java subscription — a package designed to maximise Oracle's revenue rather than address New Look's actual compliance needs.
New Look engaged Redress Compliance for an independent Oracle licensing assessment. Redress identified that the actual compliance exposure was a fraction of Oracle's proposal, implemented targeted remediations, and negotiated minimal additional purchases at steep discounts — saving New Look approximately $3 million while achieving full compliance and avoiding a binding ULA commitment.
Retail Scale
500+ stores and major e-commerce platform — with Oracle technology embedded in POS, inventory, and fulfilment systems across the entire estate
Java Across the Estate
Oracle Java SE deployed on servers, in-store devices, and integration layers — creating a broad compliance surface under Oracle's new licensing model
VMware Database Risk
Oracle Databases on VMware without hard partitioning — exposing New Look to Oracle's cluster-wide licensing interpretation
ULA Pressure
Oracle proposed an Unlimited Licence Agreement as the "solution" — a multi-year commitment designed to lock in spending regardless of actual usage
Background & Context
New Look is one of the UK's most recognisable fashion brands, founded in 1969 and operating over 500 stores across the United Kingdom, Republic of Ireland, and internationally through franchise partnerships. The company also runs a significant e-commerce operation — newlook.com — which accounts for a growing share of revenue. With approximately 11,000 employees, New Look is a mid-cap retailer operating in one of the most competitive and margin-sensitive segments of the UK market, where technology efficiency directly impacts profitability.
Oracle's Role in Retail Operations
Oracle technology underpins several of New Look's core retail systems. Oracle Database Enterprise Edition powers the company's point-of-sale (POS) transaction processing, inventory management across 500+ stores and distribution centres, e-commerce order management, and financial reporting. These databases run in a central data centre on VMware-virtualised infrastructure, with disaster recovery and development environments on separate clusters. The combination of high transaction volumes, multi-site data aggregation, and e-commerce scalability requirements made Oracle Database a critical — and expensive — component of New Look's IT stack.
Oracle Java SE was even more pervasive. Java powered middleware integrations between POS systems and central databases, ran on in-store devices for inventory scanning and stock management, supported the e-commerce platform's server-side infrastructure, and was embedded in numerous internal applications and reporting tools. Many of these Java installations had been in place for years as a free component of the technology stack — but Oracle's 2019 licensing change and subsequent Employee Metric pricing model (January 2023) transformed this ubiquitous, historically free software into a potential compliance liability running into hundreds of thousands of pounds per year.
POS & Inventory Systems
Oracle Database processing millions of daily POS transactions across 500+ stores, with real-time inventory synchronisation and fulfilment integration.
E-commerce Platform
Java-based server-side infrastructure powering newlook.com — with Oracle Database backend for product catalogue, customer data, and order management.
VMware Infrastructure
Central data centre running a 10-host VMware ESXi cluster — hosting Oracle databases alongside non-Oracle workloads, creating the conditions for Oracle's cluster-wide claim.
Retail's Unique Oracle Licensing Exposure
Fashion retailers face a distinctive Oracle licensing profile. High transaction volumes require Enterprise Edition database features. Multi-site operations create distributed Java deployments that are difficult to inventory. Aggressive cost management leaves little budget for unplanned software compliance expenses. And VMware virtualisation — widely adopted in retail for infrastructure consolidation — creates precisely the conditions that Oracle's licensing policies exploit most effectively. New Look's situation was characteristic of the sector: Oracle technology was deeply embedded, compliance governance had not kept pace with Oracle's licensing model changes, and the financial exposure was significant but largely invisible until Oracle's account team made it visible — on Oracle's terms.
The Challenges
Java SE Compliance Gap
Oracle's Employee Metric pricing — introduced in January 2023 — calculates Java SE subscription costs based on the total number of employees in the organisation, regardless of how many actually use Java. For New Look, with approximately 11,000 employees (including seasonal retail staff), Oracle's calculation produced a Java SE subscription cost of approximately $600,000 per year. This figure was presented as the baseline for a company-wide Java subscription, with no distinction between servers genuinely requiring Oracle's commercial JDK and the majority of installations that could be migrated to free alternatives or were not subject to commercial licensing at all.
VMware Database Licensing Exposure
New Look's Oracle Databases ran on a 10-host VMware cluster at the central data centre. Under Oracle's policy that VMware is not approved hard partitioning, the company faced a potential requirement to licence all physical cores across all 10 hosts — approximately 240 cores — even though Oracle workloads occupied only 3 of those hosts. At Oracle Database Enterprise Edition list pricing, this cluster-wide claim represented a potential exposure of $2 million+ in additional Processor licences alone, plus ongoing annual support costs of approximately $440,000.
Oracle's ULA Push
Oracle's account team combined the Java and Database compliance concerns into a single commercial proposal: a 3-year Unlimited Licence Agreement (ULA) covering Oracle Database Enterprise Edition and Java SE, priced at approximately $3.5 million over the term. Oracle positioned this as a "solution" that would resolve all compliance issues and provide unlimited deployment rights for the ULA duration. In reality, a ULA would have locked New Look into a minimum 3-year commitment at a price far exceeding the actual licensing requirement, created complex certification obligations at exit, and given Oracle substantial commercial leverage at renewal. Oracle's ULA proposal was not a compliance solution — it was a revenue maximisation tactic.
Unlicensed Database Features
The internal review also revealed that several Oracle Database Enterprise Edition options and packs — including Advanced Compression, Partitioning, and Diagnostics and Tuning Packs — were enabled on production systems without corresponding licence entitlements. These features are often activated by default during Oracle Database installation or enabled by DBAs for performance optimisation without awareness of the separate licensing requirement. Each unlicensed option carried its own Processor licence cost, adding to the compliance gap.
What Retail CIOs Facing Oracle Compliance Pressure Should Do
- Never accept a ULA as a compliance "solution" without independent analysis: ULAs solve Oracle's revenue problem, not your compliance problem — always quantify the actual gap before evaluating Oracle's commercial proposals
- Audit Java installations across all environments: Retail estates typically have Java on servers, POS devices, middleware layers, and internal applications — comprehensive discovery is essential before engaging with Oracle
- Review VMware configurations for Oracle isolation: If Oracle databases can be confined to dedicated hosts with vMotion restrictions, the licensing exposure may be dramatically smaller than Oracle claims
- Check for unlicensed database features: Options and packs enabled without licences are a common hidden risk — disable or licence them before Oracle identifies them
How Redress Assessed and Resolved the Licensing Position
Phase 1: Effective Licence Position (ELP) Report
Redress conducted a comprehensive data collection across New Look's entire Oracle estate — deploying discovery tools to identify every Oracle Database instance (edition, version, features enabled, and host configuration) and every Java installation (JDK version, usage context, and application dependency). This data was cross-referenced against New Look's Oracle ordering documents, support contracts, and licence grants to produce a detailed Effective Licence Position — a complete mapping of what New Look owned versus what it was actually using.
Key Findings
The ELP revealed that New Look's actual compliance gap was substantially smaller than Oracle's claims. The Java SE exposure could be reduced by over 80% through targeted remediation. The VMware database licensing exposure could be eliminated through host isolation. And the unlicensed database features could be addressed through a combination of disabling unused options and licensing the genuinely required ones at negotiated prices.
Phase 2: Java SE Remediation
OpenJDK Migration for Non-Critical Systems
Redress identified that the majority of New Look's Java installations — including middleware integrations, internal tools, and non-production servers — could be migrated from Oracle's commercial JDK to Eclipse Temurin (OpenJDK) without any functional impact. These migrations were executed systematically, with testing protocols for each application to confirm compatibility. Within six weeks, over 70% of Java installations were running on free, open-source alternatives.
Targeted Java SE Subscription
For the remaining systems that genuinely required Oracle's commercial JDK — primarily specific POS integration components and e-commerce server processes with dependencies on Oracle-specific Java features — Redress recommended a targeted Java SE subscription covering only those servers and users, rather than Oracle's proposed enterprise-wide Employee Metric subscription. This approach reduced the annual Java SE cost from Oracle's proposed $600,000/year to approximately $120,000/year — a permanent 80% reduction.
Phase 3: Database Licence Optimisation
VMware Host Isolation
Redress worked with New Look's infrastructure team to isolate Oracle Database workloads onto 3 dedicated VMware hosts within the 10-host cluster. vMotion was disabled for Oracle VMs via DRS affinity rules, and the 3 Oracle hosts were documented as a logically separate environment. This reduced the licensable footprint from 240 cores (10 hosts) to approximately 72 cores (3 hosts) — a 70% reduction in the database licensing requirement. While Oracle's official position does not fully accept this approach, the combination of technical isolation, documented DRS rules, and contractual language analysis created a defensible position.
Feature Remediation and Targeted Licensing
Redress identified which Oracle Database options and packs were genuinely required for production operations and which had been enabled unnecessarily. Diagnostics and Tuning Packs were disabled on development and test environments (where they provided no production value). Advanced Compression was confirmed as required for the e-commerce database and licensed accordingly. Partitioning was evaluated and determined to be essential for POS data management. For the features that were genuinely needed, Redress negotiated licence purchases at steep discounts — leveraging the threat of ULA rejection and the corrected compliance position to secure pricing well below Oracle's list rates.
Phase 4: ULA Rejection and Negotiation
Audit Defence and Commercial Resolution
With the remediated compliance position documented, Redress managed all communications with Oracle. The corrected ELP was presented to Oracle's account team, demonstrating that the actual licensing requirement — after Java remediation, VMware isolation, and feature cleanup — was a fraction of Oracle's ULA proposal. Oracle's ULA was formally rejected. Instead, Redress negotiated a targeted purchase of the genuinely required database options and a small number of additional Processor licences at discounts exceeding 60% off list price. The total cost of the remediation-plus-purchase approach was approximately $500,000 — compared to Oracle's $3.5 million ULA proposal.
| Component | Oracle's Proposal | Redress Outcome | Saving |
|---|---|---|---|
| Java SE Subscription (Annual) | ~$600,000/year (Employee Metric) | ~$120,000/year (targeted) | $480,000/year |
| Database VMware Licensing | ~$2,000,000 (cluster-wide) | $0 (existing licences cover isolated hosts) | $2,000,000 |
| Database Options & Packs | Included in $3.5M ULA | ~$350,000 (targeted, 60%+ discount) | Included below |
| Additional Processor Licences | Included in $3.5M ULA | ~$150,000 (minor gap, discounted) | Included below |
| Total Outcome | $3.5M ULA + $600K/yr Java | ~$500K one-time + $120K/yr Java | ~$3,000,000 saved |
Oracle's Proposed Path
- $3.5M 3-year ULA commitment
- $600K/year Java SE subscription (Employee Metric)
- 3-year lock-in with complex certification at exit
- Oracle retains commercial leverage at renewal
- No actual compliance optimisation — just blanket coverage
Redress Optimised Outcome
- ~$500K one-time targeted purchases (60%+ discount)
- $120K/year Java SE (targeted, 80% below Oracle's proposal)
- No ULA — full strategic flexibility preserved
- New Look controls future Oracle decisions
- Full compliance achieved through remediation + optimisation
Results & Business Impact
Financial Impact
New Look's total Oracle expenditure was reduced from Oracle's proposed $3.5 million ULA plus $600,000/year Java subscription to approximately $500,000 in one-time purchases plus $120,000/year Java subscription — delivering approximately $3 million in avoided costs. The annual support expense was also reduced by eliminating unnecessary licences from the maintenance base, providing additional ongoing savings estimated at $100,000+ per year.
ULA Avoidance
By rejecting Oracle's ULA, New Look avoided a multi-year contractual commitment that would have restricted its technology choices, created complex certification obligations, and given Oracle significant leverage at renewal. The company retains full flexibility to evaluate alternative database technologies, cloud platforms, or deployment architectures on its own terms — critical in a retail environment where technology strategy must adapt quickly to changing market conditions.
Compliance Confidence
All Oracle compliance issues were resolved proactively. New Look's IT and procurement teams now hold a documented Effective Licence Position that can be produced at any time in response to an Oracle audit request. Oracle backed off its audit pressure once confronted with the verified compliance position, and subsequent account interactions have been conducted on a more balanced commercial footing.
Governance and Future Readiness
Redress established a permanent Oracle governance framework for New Look — including automated Java monitoring (preventing new unlicensed installations), VMware isolation documentation (maintaining the database licensing defence), quarterly licence reconciliation, and an Oracle renewal calendar with 90-day advance alerts. This governance capability ensures that the optimised position does not degrade over time and that New Look is prepared for any future Oracle engagement from a position of strength.
The governance framework includes four specific components. First, an automated Java discovery tool that scans all servers and workstations weekly, flagging any new Oracle JDK installations for immediate review and remediation. Second, a VMware configuration monitoring script that validates DRS affinity rules remain in place and alerts the infrastructure team if any configuration change could affect Oracle licensing compliance. Third, a quarterly ELP refresh process where New Look's IT asset management team reconciles all Oracle deployments against current entitlements — catching any drift before it becomes a compliance gap. Fourth, an Oracle commercial calendar tracking support renewal dates, contract expiry windows, and Oracle fiscal quarter boundaries — ensuring that any negotiation with Oracle is initiated on New Look's timeline, not Oracle's.
The combined effect is that New Look now treats Oracle licensing as an ongoing operational discipline rather than a periodic crisis. The retailer's CFO noted that Oracle-related financial surprises have been eliminated entirely, and that future budget planning can incorporate Oracle costs with a high degree of accuracy — a significant improvement over the uncertainty that preceded the engagement.
The Retail Sector's Oracle Licensing Blind Spots
New Look's experience is far from unique in the retail sector. Fashion retailers, grocery chains, and multi-site consumer businesses share a common Oracle licensing vulnerability: the combination of high transaction volumes (requiring Enterprise Edition database capabilities), distributed Java deployments (embedded in POS systems, middleware, and in-store devices), and VMware-based infrastructure consolidation creates a compliance surface that is both large and poorly understood by internal IT teams.
The retail industry's Oracle licensing blind spots typically fall into three categories. The first is Java proliferation. Retailers adopted Java extensively during the era when Oracle distributed it freely — embedding it in everything from POS integrations to warehouse management middleware. When Oracle commercialised Java SE, these deployments became instant compliance liabilities. The challenge is compounded by the fact that Java is often installed as a dependency of third-party software — meaning IT teams may not even be aware it is present. In New Look's case, a significant proportion of Java installations had been deployed alongside third-party retail applications, not by New Look's own IT team.
The second blind spot is VMware licensing complexity. Retailers typically consolidate infrastructure onto VMware to reduce hardware costs — a sensible strategy that inadvertently creates Oracle's preferred audit target. Oracle's cluster-wide licensing interpretation can transform a well-managed virtualisation environment into a multi-million-pound compliance exposure overnight. The 70% footprint reduction New Look achieved through host isolation is typical of the savings available — but requires specialist knowledge of both VMware configuration and Oracle's licensing mechanics.
The third blind spot is Oracle's commercial playbook. Oracle's approach to retail accounts follows a consistent pattern: identify compliance gaps (or manufacture them through aggressive interpretation), quantify the exposure at maximum list prices, then offer a ULA or large licence package at a "discount" — timed to coincide with Oracle's fiscal quarter end. This playbook exploits the fact that most retail IT and procurement teams encounter Oracle licensing complexity infrequently and lack the specialist knowledge to challenge Oracle's assertions. New Look's $3 million saving was the direct result of breaking this pattern — by obtaining independent expertise before responding to Oracle's commercial pressure.
"In our experience advising retail clients, the gap between Oracle's initial claim and the actual compliance requirement is typically 60 to 90%. The key is having the technical evidence to prove it — and the negotiation experience to convert that evidence into a commercial outcome."
— Fredrik Filipsson, Co-Founder, Redress Compliance
How New Look's Results Compare
Sixt (German Retailer) — $4M Saved
Situation: A major German mobility and retail company facing Oracle compliance pressure across database and middleware licensing, with Oracle proposing an expensive licence expansion.
Takeaway: Retailers consistently achieve better outcomes by quantifying actual compliance requirements independently before engaging with Oracle's commercial proposals. Read full case study →
Pernod Ricard (French Beverages) — $4M Saved
Situation: A global consumer goods company with Oracle licences accumulated across multiple acquisitions — facing compliance pressure and unnecessary purchase proposals from Oracle.
Takeaway: Post-M&A Oracle estates almost always contain hidden entitlements that can resolve compliance gaps without new purchases. Read full case study →
Canada Life (Irish Insurance) — $1.5M Saved
Situation: A leading Irish insurer facing Oracle pressure on both Java SE subscriptions and WebLogic middleware licensing — with Oracle pushing for a large subscription deal.
Takeaway: Java SE and middleware compliance pressure is consistently resolvable at a fraction of Oracle's initial proposal through systematic remediation and independent verification. Read full case study →
Lessons Learned
A ULA Is Almost Never the Right Answer to a Compliance Problem
Oracle ULAs are designed to maximise Oracle's revenue over a multi-year commitment period and create exit complexity that favours Oracle at renewal. For a compliance issue, a ULA is the most expensive possible solution — because it prices against theoretical unlimited usage rather than actual deployment. In New Look's case, targeted remediation and discounted purchases cost 85% less than the ULA. Always quantify the actual gap before considering a ULA.
Java SE Compliance Is Highly Manageable with Systematic Remediation
Oracle's Employee Metric pricing makes Java SE appear expensive — but the actual licensable footprint is almost always far smaller than the total installation count. Systematic classification, OpenJDK migration, and targeted subscription scoping reduced New Look's Java cost by 80%. Every enterprise facing Java SE pressure should conduct a thorough classification exercise before engaging with Oracle.
VMware Host Isolation Is the Most Impactful Database Optimisation
Confining Oracle databases to dedicated VMware hosts — with documented DRS affinity rules and vMotion restrictions — reduced New Look's licensable database footprint by 70%. This single technical change eliminated the largest component of Oracle's compliance claim. Any organisation running Oracle on VMware should evaluate host isolation as a priority.
Database Feature Discipline Prevents Hidden Compliance Exposure
Oracle Database options and packs that are enabled without licences represent a significant hidden cost. Establishing a policy that requires explicit approval and licence verification before enabling any Oracle feature prevents these costs from accumulating invisibly. For New Look, proactive feature remediation avoided what could have been a substantial addition to the audit claim.
Negotiation Leverage Comes from Data, Not from Oracle's Timeline
Oracle's account teams create urgency — time-limited offers, audit deadlines, fiscal quarter pressure. Effective negotiation requires ignoring Oracle's artificial timeline and responding on your own schedule, with verified data. New Look's $3 million saving was the direct result of having accurate compliance data that rendered Oracle's proposals indefensible. Understanding Oracle's contract levers is essential to achieving similar outcomes.
Client Perspective
"We knew our Oracle licensing had issues, but Redress Compliance revealed the full extent and showed us how to fix it. They pinpointed our gaps in Java and databases, guided us to remediate them, and negotiated with Oracle on our behalf. We avoided a multi-million-dollar spend and became fully compliant. We saved $3 million and no longer worry about surprise audits. Redress gave us the confidence and leverage to deal with Oracle on our own terms."
— Head of IT Procurement, New Look