Costco Wholesale. 4.2 million dollars off Oracle support.

Costco Wholesale cut 4.2 million dollars from Oracle support by terminating unused licenses in the right order, with license set rules and repricing traps managed before any cancellation notice went in.

Why did Costco review its Oracle support spend?

Costco reviewed the support line because it had grown by inertia: support renewed annually on licenses bought across years of projects, while the deployed estate consolidated underneath. Support tracked purchase history, not the running footprint.

Oracle support renews at roughly 22 percent of net license fees per year under the technical support policies, so every unused entitlement still on support is pure carrying cost.

• Scope: the full Oracle estate, database and applications support lines.
• Method: deployment scans matched against the entitlement and support repository.
• Output: a support line by support line map of used versus unused entitlements.

What did the utilization assessment find?

The assessment found a material block of support spend with no deployment behind it. Consolidated data centers and retired projects had left licenses idle while their support lines kept renewing.

Why not just cancel every unused support line at once?

Because the matching service levels rule in the Oracle technical support policies document requires all licenses in a license set to carry the same support level, and repricing rules let Oracle recalculate retained support at list after a partial termination. Naive cancellations trigger exactly that.

How were the Oracle support terminations executed?

The program grouped terminations by license set, modeled the repricing effect of each group before notice, and timed notices against renewal dates. Nothing was cancelled until the net saving of the group survived the repricing math.

1. Build the license set map across every Oracle agreement and migration history.
2. Model post termination repricing for each candidate group against Oracle price list rates.
3. Sequence terminations so retained lines never reprice upward.
4. Serve non renewal notices inside the contractual notice window.
5. Verify the following year's support invoice against the modeled number.

What about the reinstatement risk on terminated support?

Reinstatement is expensive by design: Oracle charges back support for the lapsed period plus a penalty, per its lifetime support policy framework. The program accepted that risk only on entitlements with no plausible redeployment path.

What was the commercial outcome for Costco?

The program banked 4.2 million dollars in support savings with no compliance exposure and no repricing surprise on retained lines. The support base now matches the deployed estate, and the annual review keeps it that way.

• Saving: 4.2 million dollars off Oracle support spend.
• No repricing: retained support lines held their contracted rates.
• Forward control: utilization review now runs annually before each support renewal.

Does support termination damage the Oracle relationship?

Not when it is executed cleanly. Oracle treats well documented terminations as routine commercial hygiene; what damages the relationship is a compliance gap, and the utilization assessment confirmed there was none.

Where the common advice on Oracle support termination is wrong

The standard advice says never drop Oracle support because reinstatement penalties and repricing make it a one way door that always costs more later. We disagree. In roughly 30 to 40 Oracle support reviews Morten Andersen benchmarked in 2024 to 2025, estates that ran license set analysis before terminating kept 70 to 100 percent of modeled savings, and reinstatement was needed in almost none of them because the terminated entitlements were genuinely dead. The one way door argument protects Oracle's renewal base, not the buyer. The buyer side move is to model repricing per license set, terminate in clean groups, and accept reinstatement risk only where redeployment is implausible.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Match every Oracle support line to a verified deployment this quarter.
2. Build the license set map before shortlisting any termination candidates.
3. Model post termination repricing for each candidate group at list rates.
4. Check contractual notice windows and time non renewals against them.
5. Keep documentation of the utilization evidence behind every termination.
6. Repeat the utilization review annually before the support renewal date.

White Paper · Oracle

Oracle Third Party Support

When third party support is the right call for Oracle Database, Apps, and Middleware. Read it free.

Read the white paper

Frequently asked questions

How much did Costco save on Oracle support?

Costco Wholesale saved 4.2 million dollars by terminating support on unused Oracle licenses, sequenced by license set so retained support lines did not reprice upward.

What is the Oracle matching service levels rule?

Matching service levels requires every license in a license set to carry the same support level, so you cannot drop support on part of a set while keeping it on the rest without consequences for the whole set.

What is Oracle support repricing?

Repricing lets Oracle recalculate support on retained licenses at current list rates after a partial termination, which can erase the savings from the cancelled lines if terminations are not grouped correctly.

Is it safe to terminate unused Oracle support?

Yes, when a utilization assessment confirms zero deployment, the license set math is modeled first, and notices land inside the contractual window. Skipping any of those three steps is where terminations go wrong.

How often should Oracle support be reviewed?

Annually, before the support renewal date. Estates that review utilization every year keep support flat, while unreviewed estates compound 4 to 8 percent growth on spend that may include dead entitlements.