Shelfware at a Software Renewal

Shelfware is licensed software with no use. At renewal it is the quantity you will pay for again unless the contract lets it come off.

The shelfware page puts average unused SaaS at 32 percent of contracted entitlements and unused perpetual licenses at 19 percent. The same page puts collaboration and productivity seats higher, around 37 percent, and ERP cores lower, around 8 percent. Those are the library's figures for the contracts it describes. The measurement on a single renewal is still the admin console, not the average.

How to count it#

For SaaS, export active users over 90 days and set them next to contracted quantity, by SKU. The shelfware page flags a line under 10 percent utilization in that window. For perpetual licenses, match the contract count to what the asset inventory says is deployed.

Split the gap into three piles before the vendor call.

• Seats nobody logged into.
• Modules that were bundled and never turned on.
• Quantity that was real last year and is gone because a team, a site, or a product was shut.

The third pile is the one a vendor will recognize. The first two look like overbuying, and they still belong on the renewal order as a reduction.

What the contract has to allow#

A true-up does not give the unused seats back. It bills the excess and leaves the baseline in place. A reduction needs a true-down already in the paper, or a renewal that is open to a new quantity. The true-down page puts that clause in a minority of renewals and describes notice of 60 to 90 days. Miss the notice and the measurement does not matter for this term.

Price moves at the same time as quantity. Cutting seats while accepting an uplift on current list can leave the invoice flat. SaaS renewal price increase is the price half. Renewal timing is the calendar.

Cloud commit that was not consumed is a different leftover. It is unused spend against EDP, MACC, or a committed use discount, and it is handled in marketplace spend and cloud commits.