Shelfware is software you paid for and do not use. The licence fee is gone, so it looks harmless. It is not. Most enterprise software carries an annual support or subscription charge, and that charge keeps arriving for every unused licence, every year. On Oracle, support is 22% of what you paid for the licence, so ten idle Database Enterprise Edition processors cost more than US$100,000 a year at list price for doing nothing.
This guide shows where shelfware hides, how to find it, and how to stop paying for it without walking into the traps publishers set for partial cancellations.
In short
- Shelfware is licences bought but never deployed, deployed but not used, or used at a higher edition or volume than the work needs.
- It is found by comparing entitlements with deployment and real usage over three to six months, allowing for seasonal and standby systems.
- The saving comes from support and subscriptions. On Oracle Database Enterprise Edition, support is US$10,450 per processor a year at the 15 September 2026 list price.
- Cancelling part of an Oracle order can raise the price of what is left. Model the result before you terminate anything.
Where shelfware hides
| Type | Example | How to find it |
|---|---|---|
| Bought, never deployed | Licences for a project that was cancelled | Entitlements with no matching installation |
| Deployed, not used | A database for an application that was retired | Installations with no logins or activity over months |
| Over-specified | Enterprise Edition where Standard Edition 2 fits | Feature usage compared with what the edition adds |
| Duplicated | Two departments buying the same product under different agreements | All contracts for a publisher, read together |
| Idle subscription seats | SaaS seats for people who left or never logged in | Last-login reports from the SaaS admin console |
All five come from the same comparison: what you own against what you run and use. That comparison is your effective license position, and the surplus side of it is your shelfware.
A worked example: idle Oracle licences
A company owns 40 processor licences of Oracle Database Enterprise Edition across several orders. Discovery shows 30 in use. Ten are shelfware.
At list price, support on those ten is 10 x US$10,450 = US$104,500 a year. The obvious move is to stop paying support on them. Oracle’s support policies make that harder than it looks:
- All licences in a licence set must be supported at the same level. In Oracle’s words, “you may not support a subset of licenses within a license set.” To stop paying for some, you terminate them outright.
- When part of a single order is terminated, support for the licences left on that order is repriced at Oracle’s list price for support, less the standard discount. On a heavily discounted order, the bill can end up almost where it started.
- If you drop support and need it back later, Oracle charges a reinstatement fee of 150% of the last annual support fee for the lapsed period, plus the new year’s fee.
So the answer depends on how the ten licences sit across orders. Terminating a whole order of ten saves the full amount. Terminating ten out of an order of forty may save little. Our article on Oracle support costs explains the policy in detail.
What to do with shelfware
Reuse it first
The cheapest licence is one you already own. Before anyone buys more of a product, check for idle licences of it elsewhere in the company. Whether you can move them depends on the contract’s terms on territory and legal entity.
Terminate whole orders or licence sets
Where licences sit on their own order or set, terminating them is clean. Where they share an order, model the repricing before you write to the publisher.
Change the support model
For licences you keep but do not need updates for, Oracle third-party support typically costs a fraction of Oracle’s fee. It suits stable systems that will not move to a new release.
Cut subscriptions at renewal
Subscription seats can usually only be reduced at the renewal date. Put the usage report in front of the buyer three months before it, not three days.
Each of these is one of the levers in our guide on how to reduce software license costs.
Mistakes we see when companies remove shelfware
- Measuring usage for too short a time. Year-end systems, audits and disaster recovery look idle for months. Watch at least three to six months and ask the system owner.
- Treating standby licences as spare. Some disaster recovery set-ups need full licences. Check the rule before you count them as surplus.
- Cancelling before a migration. Licences that look idle may be needed for a move to the cloud or a new data centre.
- Terminating part of an order without modelling it. Repricing can cancel the saving.
- Doing it once. New shelfware appears every time a project ends. A managed SAM service finds it as it happens.
Questions we are asked about shelfware
What is shelfware?
Software that has been paid for and is not used, or is used far below what was bought. The cost that continues is the annual support or subscription fee.
How do you find unused software licences?
Compare entitlements from your contracts with installations from discovery, then check real usage, such as logins and activity, over three to six months.
Can we stop paying Oracle support on licences we do not use?
Yes, by terminating those licences. Oracle does not allow support on only part of a licence set, and terminating part of an order reprices the rest. Model it first.
Is shelfware a compliance risk?
Not in itself. Unused licences are the opposite of a shortfall. The risk is in the same records, though: a company that cannot see its idle licences usually cannot see its gaps either.
See more of our analysis in Google: add Rythium as a preferred source
