Shelfware is the seat you bought, provisioned, and never used. It hides in true ups and edition upgrades, and the renewal recounts the paper, not the logins. Measure it early or pay for it again.
Salesforce shelfware is the seat you bought, provisioned, and stopped using. It hides in true ups, co term additions, and edition upgrades nobody re measured. The renewal recounts the headcount on paper, not the logins in the system, so the waste compounds unless you measure and act before the term ends.
Shelfware is rarely a single bad decision. It is the slow accumulation of seats added for a project, a hire that never landed, or a feature someone might use. Salesforce has no reason to flag it. The renewal simply recounts the paper.
This guide defines shelfware, shows how to measure it, and sets out the moves to clear it.
Shelfware builds through optimism and inertia. Seats get added for growth that slows, projects that pause, and teams that reorganize. Each true up assumes the prior count was right. Salesforce documents its products on the product overview pages, but nothing in the contract prompts a downward review.
The renewal recounts seats on the order form, not logins in the system. Without usage evidence, the safe default is to renew what you had. That default is how shelfware survives year after year.
Shelfware is any paid entitlement with no meaningful use over a measurement window. That covers dormant user seats, idle add ons, and over bought editions. The Salesforce help documentation exposes login history and feature adoption reports that make the call objective, and the editions and pricing pages show what each entitlement costs.
How to classify a Salesforce entitlement
| Category | Test | Action |
|---|---|---|
| Dormant seat | No login in 90 days | Reassign or drop at renewal |
| Light seat | Login but no record activity | Downgrade the edition |
| Idle add on | No feature adoption | Remove at renewal |
| Over bought edition | One feature drives the tier | Split or downgrade |
Measure logins and feature adoption, not provisioned seats. The platform exposes the data; the work is reading it against the contract. A clean utilization picture is the evidence the renewal turns on.
The common advice is to wait for the renewal and then ask Salesforce to true down the seat count. We disagree. In the estates we have benchmarked, the reduction right did not exist on the paper, so the request had no contractual basis and went nowhere. By the time the renewal lands, the leverage is already gone. The buyer side move is to measure utilization a full year out, give written notice of the intended reduction inside the contract window, and negotiate a reduction right into the next term so the true down is enforceable rather than a favor.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Shelfware is not a Salesforce problem. It is a measurement problem. The platform shows you every idle seat. The renewal just never asks.
Because the standard contract does not let you. Without a reduction right, the renewal value cannot fall below the prior term. Dropping seats requires either a negotiated reduction clause or written notice given inside the contract window.
Five moves clear shelfware and stop it returning. They run off the usage data and the contract calendar, both of which the buyer controls.
Salesforce shelfware is any paid entitlement, seat, add on, or edition upgrade, that has no meaningful use over a measurement window. It is provisioned and billed but not adopted, and it survives because renewals recount seats on paper rather than logins in the system.
In the estates we benchmarked, inactive or barely used seats ran at 12 to 28 percent of the licensed total. At least one paid add on per estate had never reached production. The waste is the rule, not the exception, unless utilization is measured.
Measure logins and feature adoption, not provisioned seats. The platform exposes last login and adoption reports natively. A 90 day login gap flags a dormant seat, and a login with no record activity flags a light user who may not need a full edition.
Only if the contract allows it. Standard Salesforce paper carries no reduction right, so the renewal cannot fall below the prior value. You either negotiate an explicit reduction clause or serve written notice of the reduction inside the contract notice window.
A dormant seat has no login over the window, typically 90 days, and should be reassigned or dropped. A light seat logs in but does little record activity, which usually means the user sits on too high an edition and can be downgraded rather than removed.
Reassign first. Most estates carry idle seats that can be moved to new users at no extra cost. Buying new seats while dormant ones sit unused is the most common way shelfware grows, so recycle before you purchase.
Start nine to twelve months before the renewal. That lead time lets you measure utilization, reassign idle seats, and serve any reduction notice inside the contract window. Waiting for the renewal removes the leverage to act on what you find.
Redress runs Salesforce advisory inside the Vendor Shield subscription, the Software Spend Assessment, the Renewal Program, and the Benchmark Program. The output is a utilization audit, a reassignment plan, a reduction notice, and a reduction right negotiated into the next term.
The utilization tests, the shelfware categories, the reduction notice language, and the reassignment plan to clear idle seats before the next renewal.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Every idle Salesforce seat is a renewal you pay twice. The platform shows you which ones. The only question is whether you look before the renewal or after.
