The different ERP vendor tiers explained

The tiered classification of enterprise software emerged in the mid-80s alongside client-server technologies. While most of the broader software market has since abandoned this taxonomy, ERP vendors have kept it, and it still shapes how buyers research, shortlist, and ultimately spend.

Understanding what each tier actually means, and where the definitions break down, matters whenever you're evaluating scope, complexity, and price of ERP software.

One caveat before going further: there is no universally accepted definition of tiers 1, 2, and 3, nor agreed-upon criteria for assigning a system to each.

Marketing teams have always had an incentive to talk their products up, which means tier 2 systems occasionally get sold as tier 1, and products that aren't ERP at all sometimes get sold under that label. When systems are oversold, the customer is usually the one who suffers. The goal here is to cut through that and give you a working framework.

The five criteria people use (and why none of them is perfect)

Different organisations use different benchmarks when categorising ERP systems. The most common are supplier size, system cost, typical customer size, number of users supported, and functionality. Each has merit, but each also has blind spots.

1. Supplier size seems logical at first. Big systems come from big vendors. Ask someone to name tier 1 suppliers and they'll say SAP and Oracle without hesitation. But SAP Business One is clearly not a tier 1 product, even though it comes from a tier 1 company. Microsoft is an enormous business, yet whether Dynamics 365 qualifies as tier 1 depends on which version you're looking at, given that it replaced a range of products from AX down to GP. IFS, a much smaller company than Infor or Sage, would be classified as tier 1 by almost any other measure. Supplier size plays a role, but it can't carry the classification on its own.
2. System cost tracks more reliably at the high end; multi-million dollar Oracle and SAP deployments are obviously tier 1, but the category blurs quickly below that. SAP Business One, measured by price, sits in tier 2, yet it once lacked an inventory module that tracked storage locations (because it was designed as an accounting system, where location matters less than quantity and value). A competing system that outperforms it on supply chain functionality is available for less than a quarter of the price. Cost and capability don't always move in the same direction.
3. Typical customer size has the same problem in reverse. Many large organisations are essentially collections of smaller operating units, and some have deliberately chosen to run tier 2 or tier 3 systems at the unit level while consolidating financials in a tier 1 accounting platform at the group level. Tier 1 systems can be overkill for smaller subsidiaries (too cumbersome and too complex for day-to-day use). Organisation size tells you something, but not always what you need to know.
4. Number of concurrent users is arguably the most reliable proxy, even if it isn't perfect. A system capped at 25 concurrent users belongs in tier 3; one that handles 5,000 comfortably belongs in tier 1. But there's plenty of variation within each band. Some tier 3 systems run out of steam at 25 users while others hold steady at 50, and transaction volume matters as much as headcount. A company with thousands of daily telesales orders has very different demands on its database than a capital equipment business processing a handful of transactions a week.
5. Functionality is the most revealing criterion and the hardest to apply. Tier 1 systems are expected to be functionally comprehensive, but they're also heavily customised. Most organisations spending at that level want a close fit and are willing to pay for it. At the other end, a company spending £40,000 on a tier 3 system will usually accept its limitations rather than spend ten times the licence fee on custom development. There's also a sector dimension: a system that qualifies as tier 1 for a distribution business might only reach tier 2 for a manufacturer, and both assessments can be correct given the companies involved.

The most useful approach is to treat these criteria as a composite rather than picking one. No single measure gives you the full picture.

ERP vendor tier 3

Tier 3 covers businesses with annual revenues roughly in the range of $0-$20 million. At the lower end, fully integrated SaaS ERPs now dominate, largely because of lower upfront costs and faster implementation.

At the upper end, subscription-based mid-scale SaaS systems have largely displaced the hybrid on-premise/cloud setups that were common a decade ago. Pricing typically works best on a per-seat subscription model.

Recommended download: ERP Vendor Guide - Find ERP vendors suitable to your business requirements

ERP vendor tier 2

Tier 2 applies to businesses in the $20 million–$250 million revenue range. These systems need room to grow as a baseline; their processing architecture scales over time without significant additional cost, and they typically support integration with external applications as standard, including connections to IoT platforms.

Vendors like Plex, along with mid-market offerings from SAP and Oracle, sit in this space. At the upper end of tier 2, the line between tiers becomes blurry, which is where most of the marketing inflation tends to happen.

ERP vendor tier 1

Tier 1 starts around $250 million in annual revenue and scales upward from there. At the lower end of this tier, expect fully integrated modules, deep customisation capabilities, and the ability to manage mass relational data at scale.

At the high end, almost any reporting or analytical requirement can be addressed...at a cost. SAP, Oracle, Microsoft, and Epicor are the names most commonly associated with this tier. Pricing can run from the high six figures into the tens of millions for large deployments.

A note on tier 1 vs tier 2

The distinction between tier 1 and tier 2 ultimately comes down to a combination of the factors above: scale, cost, user volume, and functional depth. There's no clean dividing line, which is precisely why categorisation by tier exists as a rough guide rather than a definitive classification.

The practical risk is that buyers exclude systems that would genuinely suit them in order to purchase at a tier that feels appropriate to their size or ambitions. Some organisations also find that what they actually need isn't full ERP at all; a specialist system will serve them better than a suite with capabilities they'll never use.

Use the tiers as a starting point for narrowing your search, not as the final word on what's right for your business.