ERP Shelfware: The Modules You Pay to Ignore

Your ERP vendor sold you a platform. Your team uses it as a glorified spreadsheet with a login screen. If that sounds familiar, you’re not alone. The gap between what companies license and what they actually deploy is one of the most expensive problems IT leaders never get around to discussing.

It has a name: shelfware. And in mid-market businesses, it steadily drains budgets while the features that could solve real operational problems collect dust.

How Big Is the ERP Utilization Gap?

The numbers are hard to ignore. According to Vertice’s 2025 SaaS Wastage Report, 15% of enterprise software applications are completely unused, and another 51% are underutilized, with organizations running less than half of their licensed capacity. That means two out of every three applications aren’t earning their keep.

Pendo’s Feature Adoption Report found a similar pattern at the feature level: 80% of software features go unused. Only about 12% of features drive 80% of daily usage volume. The rest exists in menus nobody opens.

For ERP specifically, the pattern is predictable. Finance and accounting modules get deployed first and used most. According to electroiq’s 2024 ERP buyer survey, 89% of buyers list accounting as their top required feature. The project management, inventory, CRM, and reporting modules that came bundled in the same license often sit dormant for months or years after go-live.

Why Do Modules Go Unused After Go-Live?

The implementation ended. The vendor declared success. Your team went back to work. And that’s where shelfware begins.

The rollout stopped at Phase 1. Most ERP implementations are phased, and Phase 1 almost always covers financials. Phases 2 and 3 (project management, CRM, advanced reporting) get indefinitely deferred because the team that ran implementation is now handling support tickets.

Training covered the system, not the workflow. One-time training workshops teach people where buttons are. They don’t teach people how the system fits their daily work. When the gap is too wide, users fall back on what they know: email, spreadsheets, and manual processes. Research from Apty on digital adoption challenges confirms that traditional training methods fail consistently for complex enterprise systems.

Nobody owns post-go-live adoption. The implementation partner leaves. The internal project manager moves to the next initiative. No one is responsible for measuring whether teams are actually using what was deployed, let alone rolling out the modules that weren’t. We’ve written about this handoff problem in our post-implementation guide.

The system doesn’t match the process. When ERP workflows don’t align with how people actually work, workarounds emerge. Users build parallel processes in spreadsheets and email. The ERP module technically exists, but the real work happens outside it.

What Does ERP Shelfware Actually Cost?

The license fee is the obvious cost. But it’s not the expensive part.

G2’s license management research estimates that $34 billion is wasted annually on unused software licenses across the US and UK. The average organization wastes $19.8 million per year on licenses nobody touches. And 76% of companies over-license deliberately, often to avoid vendor audit penalties.

The bigger cost is the operational value you’re not capturing. Every unused module represents a process that’s still manual, still disconnected, still generating errors:

Project management module unused: Project status lives in spreadsheets. Resource conflicts get discovered in Monday meetings. Margins are calculated after the project ends, when it’s too late to adjust.
CRM module unused: Sales pipeline data is scattered across inboxes. Lead-to-close conversion is unmeasured. Revenue forecasting is guesswork.
Reporting module unused: Teams spend hours pulling data from separate sources and reconciling it in Excel. By the time the report is ready, the numbers are stale. We covered this pattern in detail in our piece on spreadsheet reporting costs.

A McKinsey and University of Oxford study of 5,400 IT projects found that 66% of enterprise software projects experience cost overruns, with cumulative overruns totaling $66 billion. Each additional year of project delay adds roughly 15% to cost. Shelfware is what happens when those overruns force you to cut scope, and the cut modules never come back.

How Do You Measure ERP Utilization?

You can’t fix what you don’t measure. Most organizations have no formal process for tracking how much of their ERP is actually in use. Here’s how to start:

Map licensed vs. deployed modules. List every module included in your license agreement. Flag which ones are actively configured and used. This alone often reveals that 30-40% of what you’re paying for was never set up.
Check user login and activity data. Most modern ERPs track login frequency and feature usage. Look for modules where logins have dropped to near zero, and for users who log in only to run a single report.
Audit the workarounds. Where are your teams using spreadsheets, email threads, or standalone tools to do work that the ERP could handle? Every workaround is a signal. Our guide on double data entry costs walks through how to quantify this.
Interview department leads. Ask a simple question: “What tasks do you do regularly that you wish were automated or handled by a system?” The answers will map directly to unused ERP capabilities.
Compare processes to available features. For each business process that’s still manual or disconnected, check whether the ERP already has a module or feature that covers it. This exercise typically surfaces three to five quick wins in mid-size businesses.

How to Close the Utilization Gap

Once you know what’s unused and why, you need a strategy that doesn’t repeat the mistakes of the original rollout. This isn’t another big-bang implementation. It’s incremental, targeted activation.

Prioritize by operational pain, not by module list. Don’t start with the module. Start with the business problem. Which manual process costs the most time? Which disconnected workflow generates the most errors? Match those to the unused capabilities.

Assign ownership. Every module activation needs a business owner (who defines requirements and validates outcomes) and a technical owner (who configures and supports). Without both, you’ll repeat the pattern of deploying without adopting.

Use phased rollouts with small groups. Pick one team or department. Deploy one module. Measure usage after 30 and 60 days. Adjust. Then expand. This approach reduces risk and builds internal proof points.

Invest in contextual training, not classroom sessions. Training embedded in the workflow (tooltips, guided walkthroughs, in-app help) outperforms one-time sessions consistently. People learn systems by using them, not by watching presentations.

Renegotiate your license. If you discover modules you’ll never use, renegotiate. If you discover you need additional capabilities, you’ll negotiate from a stronger position because you can demonstrate utilization of what you already have.

Should You Pay for Modules You Might Need Later?

This question comes up in every ERP procurement cycle. The vendor offers a bundled price that includes modules you don’t need today but “might need as you grow.” The discount looks attractive. Here’s the trade-off:

The case for bundling: Module-by-module purchasing is usually more expensive over time. If you’re confident you’ll deploy the capability within 12-18 months, buying it upfront often saves money.

The case against: Unused modules aren’t free even when they’re “included.” They increase complexity, expand the surface area your IT team maintains, and create a false sense of capability. Your team says “we have that module” when what they mean is “we licensed it three years ago and never configured it.”

The right answer depends on your organization’s track record. If your last ERP rollout deployed all planned phases on time, bundle confidently. If Phase 2 got deferred indefinitely (as it does in most mid-market implementations), pay for what you’ll use in the next year and negotiate options for the rest.

Frequently Asked Questions

What percentage of ERP features do companies actually use?

Research from Pendo found that only about 20% of software features are regularly used, with 12% of features driving 80% of daily activity. For ERP systems specifically, finance and accounting modules see the heaviest use, while project management, CRM, and advanced reporting modules are frequently underutilized or never deployed.

What is ERP shelfware?

ERP shelfware refers to licensed ERP modules or features that an organization has purchased but never deployed or meaningfully used. It represents wasted spend and, more importantly, operational value that the business isn’t capturing. The term comes from the idea that the software is sitting on a shelf rather than being put to work.

How do you measure ERP utilization?

Start by comparing licensed modules against what’s actually deployed and configured. Then review user activity logs for login frequency and feature usage patterns. Audit business processes that still rely on spreadsheets or manual work, as these often map to available but unused ERP capabilities.

What causes ERP underutilization after go-live?

The most common causes are: phased implementations where later phases get indefinitely deferred, ineffective one-time training that doesn’t translate to daily workflow changes, lack of ownership for post-go-live adoption, and misalignment between ERP workflows and actual business processes. The result is that teams revert to familiar tools and build workarounds.

Is it worth paying for ERP modules you might use in the future?

It depends on your deployment track record. Bundled pricing is usually cheaper per module, but unused modules carry hidden costs in complexity, maintenance, and false capability assumptions. If your organization consistently deploys planned phases on time, bundling makes sense. If later phases typically get deferred, pay for what you’ll use within the next year.

How Tier2 Keel Tackles the Utilization Problem

Shelfware thrives when business functions are separated into distinct modules that require separate configuration, training, and rollout. Tier2 Keel takes a different approach: core business operations (leads, projects, invoicing, SLA management, customer portal) are built into a single, connected workflow rather than sold as isolated modules you may never activate.

When a team starts using Keel for project management, client billing follows naturally because the data flows from one step to the next. There’s no separate module to license, configure, and train for. The functions that would be shelfware in a traditional ERP are active from day one because they’re part of the same process.

See how Keel works or book a walkthrough.

The next time your vendor sends a renewal notice, compare the module list against what your teams actually touch. That gap between the invoice and reality is where your IT budget goes to produce nothing. Closing it doesn’t require another transformation initiative. It requires knowing what you already have, deciding what’s worth activating, and building a plan to get there one process at a time.