Shelfware is software you pay for but do not use. The name comes from the days of boxed software that sat on a shelf, unopened. Today it is invisible: a subscription seat assigned to someone who left, a premium module nobody switched on, a tool a project bought and forgot. It does not show up as a problem on any dashboard. It shows up only as money.
How big the problem is
The $21 million figure reflects Zylo's customer base, which skews toward large enterprises, but the pattern holds at every size: a meaningful share of every software budget pays for nothing. The more telling number is the last one. If four in ten SAM teams are not tracking SaaS usage, they cannot see shelfware in the category where it grows fastest.
Shelfware also compounds. A seat that is idle this year is renewed next year, usually at a higher price, and often with a few more seats added "for growth". Without a deliberate check, the waste is carried forward and inflated at every renewal.
The six forms of shelfware
Licenses assigned to people who have not used the product for months. Usually the largest category.
Bought "for growth" and never given to anyone. Common after over-optimistic hiring plans.
Still assigned to people who have left. A symptom of an offboarding process that stops at the identity provider.
Paid add-ons and premium tiers that were never deployed or switched on.
Tools bought by a team or project, still renewing after the need ended.
Two products doing the same job because different teams bought them. Not strictly unused, but half the spend is avoidable.
The mix varies by organization, but a typical first assessment in a mid-sized company looks something like this:
How to measure it
You need two data points for each product: how many licenses you pay for, and when each one was last used.
- Paid for: from the contract or the latest invoice. Not from the admin console, which shows what is assigned, not what is billed.
- Last used: from the vendor's admin console or usage reports, your identity provider's sign-in logs, or device inventory for installed software.
Then choose a threshold for "unused", commonly 90 days for productivity tools and shorter for products used daily. Our guide to inactive user thresholds explains how to choose. Shelfware cost is simply:
(licenses paid for − licenses used within the threshold) × cost per license
Add forgotten subscriptions from expense and card data, which often reveal tools no one in IT knew about. See shadow IT.
What shelfware looks like across a portfolio
Shelfware is rarely spread evenly. A few products account for most of it, and they are not always the most expensive ones. Products bought on enterprise-wide terms for "everyone" tend to have the lowest utilization.
The biggest shelfware is rarely in the biggest contract. It is in the tools bought for everyone and used by a few.
How to remove it
Removing shelfware is mostly a matter of timing. Most subscriptions cannot be reduced mid-term, so the work is to know the number before the next renewal, true-down or billing anniversary.
- Now: reclaim
Remove idle and leaver seats and return them to the pool. New joiners get recycled licenses instead of new purchases.
- 90–120 days before renewal: size
Recalculate the active count, add a small buffer for known hiring, and decide the renewal quantity.
- Before the notice date: tell the vendor
Send the reduction in writing before the notice period starts. See contract notice periods.
- At renewal: reset the baseline
Sign for the right number, remove unused modules and tiers, and record the saving.
- Every quarter: keep it clean
Re-run the inactive report so shelfware does not rebuild.
Specific actions for each type:
- Idle and leaver seats: reclaim them and reduce the count at the next renewal or true-down opportunity. See license reclamation.
- Unassigned licenses: reduce at renewal; keep only a small buffer for known hiring.
- Unused modules: remove at renewal, or swap for something the business does use. See right-sizing.
- Forgotten subscriptions: cancel before the next notice deadline, and route future purchases through an approval workflow.
Removing shelfware without upsetting anyone
- Tell users before you reclaim, and give them a simple way to ask for the license back.
- Use a threshold that fits the product: 30 days for daily tools, 90 for occasional ones.
- Exclude service accounts, shared mailboxes and licenses required by contract.
- Reduce at the renewal, not mid-term, unless the contract allows it.
- Reclaiming licenses from executives or on-call teams without checking first.
- Cutting the renewal count to today's usage with no buffer for hiring.
- Treating "assigned" as "used". Assignment is not activity.
- Letting the reclaim become a one-off project instead of a quarterly routine.
How MI One helps
Frequently asked questions
Is shelfware the same as overlicensing?
Overlicensing is the broader position of owning more than you use. Shelfware is the unused software itself.
Can we get a refund for shelfware?
Rarely mid-term. The savings usually come from reducing volume at renewal, true-down or the next billing period.
How often should we check for shelfware?
Quarterly for major per-user products, and always 90 to 120 days before a renewal.
What is a normal level of shelfware?
Some buffer is healthy, typically a few percent for hiring and onboarding. Anything above 10% of a product's seats is worth investigating, and above 20% usually means the renewal count is wrong.
Sources
- Zylo, "2025 SaaS Management Index," January 16, 2025. https://zylo.com/news/2025-saas-management-index
- Flexera, 2025 State of ITAM Report press release, June 18, 2025. https://www.flexera.com/about-us/press-center/it-teams-losing-visibility-according-to-flexera-2025-state-of-itam-report