In This Article
Salesforce shelfware is the enterprise equivalent of a gym membership you stop using in February but keep paying for through December. The difference is that enterprise Salesforce shelfware costs are typically measured in six or seven figures — not the $50 per month of a personal membership.
We define Salesforce shelfware as any licensed product, feature, or user seat included in an enterprise contract where actual utilisation falls materially below contracted levels. Our benchmark data across 100+ enterprise Salesforce engagements shows that the average enterprise pays for substantially more Salesforce capability than it actually uses — and that this gap compounds over successive renewal cycles as Salesforce's account teams add products to contracts without reducing the prior year's shelfware.
What Salesforce Shelfware Actually Is
Shelfware in Salesforce contracts manifests in three distinct forms, each with different causes and different remediation approaches. The first is seat shelfware — named user licenses assigned to employees who are inactive, departed, or whose role does not require Salesforce access at the tier licensed. The second is product shelfware — entire products or modules included in the contract that are technically available but have not been deployed, configured, or adopted. The third is feature shelfware — add-on capabilities within licensed products (Einstein AI features, advanced analytics modules, industry-specific functionality) that are included in the contracted edition but have never been activated.
All three forms are negotiable at renewal. Seat shelfware supports a direct license count reduction. Product shelfware supports removal of entire product lines from the contract. Feature shelfware is more nuanced — it often reflects unused capability within a higher-tier edition that could be managed through an edition downgrade to a lower tier for affected user populations.
How Shelfware Accumulates in Enterprise Contracts
Understanding how shelfware accumulates is important context for the renewal negotiation. Shelfware does not typically appear because an enterprise knowingly purchases unused capability. It accumulates through a series of individually rational decisions that compound over time.
Workforce changes are the primary driver of seat shelfware. Employees leave, roles change, and reorganisations reduce headcount in Salesforce-using departments — but auto-renewal provisions ensure that license counts remain at the prior year's levels unless someone actively manages the inventory. In enterprises without centralised SaaS management governance, the Salesforce license count often reflects peak historical headcount rather than current organisational reality.
Product expansion during prior renewals is the primary driver of product shelfware. Salesforce's account team is skilled at including additional products — Einstein Analytics, Salesforce Maps, Inbox, Social Studio — in renewal conversations by framing them as strategic additions at "deeply discounted" rates. In the moment of renewal, when the primary focus is on base platform pricing, these additions feel trivial. Over 3–4 renewal cycles, they compound into a portfolio of licensed but largely unused products that collectively represent 20–30% of the total contract value.
The Compounding Effect: A typical enterprise Salesforce contract grows by 7–10% per year through a combination of price escalation, headcount additions, and product expansions. Without active shelfware management, the shelfware layer grows proportionally — meaning a $500K Salesforce contract at Year 1 with 20% shelfware becomes a $750K contract at Year 5 with the same 20% shelfware that has now grown to $150K in annual unused spend. Shelfware never self-corrects. It must be actively audited and eliminated.
The 6 Most Common Salesforce Shelfware Categories
Based on our enterprise engagement data, these six categories consistently account for the majority of Salesforce shelfware value:
1. Dormant named users. Users who have not logged into Salesforce in the prior 90 days represent the most visible and easiest-to-justify shelfware. In enterprises with seasonal or project-based Salesforce usage, dormant user populations can represent 20–35% of total licensed seat counts. The audit tool: run the User Login History report filtered to the prior 90 days and compare active users to total licensed users.
2. Einstein Analytics and Intelligence features. Einstein Analytics (now part of the Einstein 1 platform), Einstein Prediction Builder, and similar AI features require active configuration and adoption effort after licensing. These features are frequently licensed as part of Unlimited or Einstein 1 tier purchases but never configured for production use. Adoption below 10% of licensed users is the threshold we use for shelfware classification.
3. Salesforce Maps and Field Service licenses. Maps and Field Service Lightning are point solutions with specific use cases in field service and mobile sales. They are frequently added to enterprise agreements during renewals when an account executive identifies a potential use case — but are often deployed to a small fraction of the contracted user population. Licence counts for these products are frequently set at the total sales or service organisation headcount rather than the subset with genuine field activity.
4. Marketing Cloud contact volumes above actual database size. Marketing Cloud pricing is based on contracted contact volumes. Enterprises frequently contract for contact volumes based on projected database growth that does not materialise — or maintain contracted volumes for databases that have been partially archived or cleaned. Comparing contracted contact volume to actual Marketing Cloud contact database size is a straightforward audit step that consistently reveals over-contracted positions.
5. Inbox and Pardot Growth add-ons. Salesforce Inbox (email integration) and Account Engagement (formerly Pardot) Growth tier add-ons are frequently bundled into enterprise agreements at renewal as low-cost additions. The user populations that actively use these integrations typically represent 20–40% of the licensed population, with the remainder maintaining the license passively.
6. Edition over-allocation for specific user segments. A portion of most enterprise user populations has access requirements that would be fully met by a lower license edition. The most common pattern: Unlimited edition licenses assigned uniformly across a sales organisation where 30–40% of users are internal support staff or sales operations personnel who do not use the advanced features that distinguish Unlimited from Enterprise. See our guide on Salesforce License Types for a full breakdown of edition differences and where downgrades are viable.
The Shelfware Audit: Step-by-Step
A complete Salesforce shelfware audit requires access to Salesforce's built-in reporting and the License Management App. The following methodology is executable internally by a Salesforce administrator or with external advisory support.
Extract the Contract Inventory
Pull your current Salesforce order form and master service agreement. Create a spreadsheet inventory of every licensed product, the contracted quantity, and the annual cost. This is your baseline against which utilisation will be measured.
Run User Activity Analysis
In Salesforce Setup, navigate to Users → Login History. Filter to the prior 90 days and export. Compare the count of users with at least one login in the period to total active licensed users. Users with zero logins in 90 days are dormant seat shelfware candidates. Cross-reference with HR data to identify termed employees who may still hold active licenses.
Audit Product Feature Adoption
For each add-on product in your contract — Einstein Analytics, Maps, Inbox, Field Service, etc. — run Salesforce's feature adoption reports or use the Setup → Permission Sets menu to identify users with the relevant feature permission assigned and active. Compare active users per feature to contracted seats per product. Features with below 25% activated user populations are shelfware candidates.
Analyse Edition Requirements by User Segment
Map your user population by role and identify which specific Enterprise or Unlimited features each role segment actively uses. Focus on the features that distinguish Enterprise from Professional (workflow automation, developer sandbox) and Unlimited from Enterprise (expanded sandbox count, premier support). User segments that use none of the distinguishing features of their licensed edition are edition downgrade candidates.
Check Marketing Cloud and Pardot Consumption
In Marketing Cloud, navigate to Administration → Account → Billing to review contact database size versus contracted contacts. In Account Engagement, check the Prospect database count against contracted prospect limit. Document any gap between contracted and actual volumes.
Quantify the Total Shelfware Value
For each shelfware category identified, calculate the annual cost based on contracted per-unit pricing: dormant seats × annual per-seat cost; unused products × annual product cost; over-licensed editions × annual per-seat premium. Total these values to produce your documented shelfware reduction case for the renewal negotiation.
Using Shelfware Evidence in Renewal Negotiations
The shelfware audit produces a documented, data-backed case for contract value reduction that Salesforce cannot credibly dispute — because the evidence comes from Salesforce's own systems. Present this evidence before Salesforce presents its renewal quote, as part of the buyer-initiated engagement process described in our Salesforce Renewal Tactics guide.
Frame the shelfware evidence not as a complaint but as a business opportunity: "We have completed a utilisation analysis using Salesforce's own reporting tools. Here is what we found. We want to right-size the contract to reflect actual deployment, and we're open to a multi-year commitment at the right-sized value with appropriate price protections." This framing positions the shelfware reduction as the foundation for a renewed commercial relationship rather than an adversarial demand.
Salesforce will typically accept documented shelfware reductions on product lines where usage evidence is clear, while pushing back on license count reductions by pointing to annual peaks rather than 90-day rolling averages. Negotiate on 12-month average active users rather than peak historical counts — this produces a fairer and typically more favourable baseline for the right-sizing conversation.
Preventing Shelfware in Future Renewals
Shelfware prevention requires governance processes that most enterprises have not built into their SaaS management frameworks. The essential components are: quarterly license reconciliation reviews comparing active users to licensed counts; annual product adoption reviews that document utilisation rates against contracted volumes; renewal calendar management that triggers shelfware audits at the 120-day mark before each renewal; and contract provisions that include usage-based true-down rights allowing license count reduction of up to 15% annually without penalty.
The most effective long-term shelfware prevention mechanism is the contractual true-down provision — a right, negotiated into the Salesforce agreement, to reduce license counts annually based on documented utilisation data without triggering a contract restructure or penalty payment. True-down provisions are not standard in Salesforce contracts but are negotiable, particularly on multi-year commitments where they provide commercial certainty for Salesforce while preserving flexibility for the buyer.
For advisory support with Salesforce shelfware audits and renewal negotiations, firms like Redress Compliance — the leading Salesforce commercial advisory firm — and Atonement Licensing provide end-to-end services from utilisation analysis through negotiation execution. For a comprehensive view of the Salesforce negotiation landscape, return to the Salesforce Negotiation Guide 2026.