ERP pricing models explained: per user, modules, tiers and usage

Most ERP and business-management SaaS prices are built from four ingredients: who uses the system (users, often by type), what it does (modules or editions), how much it is used (transactions, storage, entities, API calls) and how much help you buy (support tier). The cheapest model for your business is the one whose main ingredient you have least of. A business with few users but thousands of orders a day should be wary of transaction pricing; a business with many occasional users should look for light-user or approval-only licences.

This guide is part of the ERP software pricing comparison overview. Every figure below is an illustrative example, not a vendor price.

Per-user pricing: named, concurrent and light users

Named user pricing charges for each person who has a login, whether they use it every day or once a month. It is the most common model for cloud ERP. Concurrent user pricing, more common with older perpetual licences, charges for the maximum number of people logged in at the same time. Concurrent licences can be cheaper for shift-based businesses but are less common in SaaS.

Many vendors now offer user types:

Count users by role, not by headcount. A common mistake is to buy full licences for everyone because the first quote was built that way, or the opposite: to discover after signing that approving a purchase order requires a full licence. Ask the vendor for the licence-rights document that says exactly what each user type can do.

Modules, editions and tiers

Module pricing starts with a base platform (usually financials) and adds a fee for each functional area: inventory, manufacturing, projects, advanced reporting, multi-entity consolidation, field service. Edition or tier pricing sells bundles: a starter edition with a capped number of users and modules, a standard edition, a premium edition.

Questions that change the total:

1. What triggers an upgrade? Some tiers cap users, transactions, entities or warehouses. Crossing one limit can move you to a tier that costs much more.
2. Are later modules discounted? A module added in year three may be priced at the then-current list price rather than your negotiated discount. Ask for a price schedule for modules you might add.
3. Is a module per company or per user? Some modules are priced per user of that module, others as a flat platform fee.
4. What is included in "unlimited"? Unlimited users or transactions may still have fair-use limits on storage or API calls.

Usage, transaction and revenue-band pricing

Some vendors charge by volume: invoices issued, orders processed, documents stored, API calls, or bands of company revenue. This suits businesses with few users and heavy automation, such as an online retailer whose orders flow in automatically. It is harder to forecast. Ask for:

• the volume included in the base price;
• the overage rate and whether it is billed monthly or at true-up;
• a cap on overage per year;
• whether integration traffic (for example from your e-commerce platform or bank feed) counts as usage.

Worked example: same business, three models (illustrative)

A Canadian distributor has 8 people who process transactions all day, 14 managers who approve purchases and read reports, and 30 warehouse staff who record counts on handheld devices. It processes about 40,000 orders a year.

The usage model looks cheapest today. But if orders double in three years, it becomes $12,000 + 80,000 × $0.30 = $36,000, while the mixed per-user model stays the same if headcount does not grow. The full-users-only quote is simply mis-specified. Run each model with your growth plan, not only your current volume, and put the result into the TCO estimator.

Support tiers, environments and other recurring fees

Beyond users and modules, check for:

• Support plans: standard support may be email-only with business-day response; premium tiers add phone support, faster response, a named contact or after-hours cover. Some vendors price these as a percentage of the subscription.
• Sandboxes and test environments: one may be included; extra sandboxes for training or testing upgrades can be billed separately.
• Additional companies or entities: a second legal entity, for example a Quebec subsidiary, may count as another company with its own fee.
• Storage and document attachments above an included limit.
• Partner-built add-ons sold from a marketplace, which often have their own subscriptions and renewal terms.

How to request a quote that compares

Ask every vendor or partner to fill in the same table: users by type and price, modules, editions, included volumes, overage rates, support tier, environments, and each figure for years one to five including renewal terms. The quote comparison method shows how to normalise what comes back, and the renewal uplift guide explains what to ask about year-two pricing.

FAQ

Are light users really cheaper?

Usually, but only if their rights match the tasks they perform. Check whether approving, editing or creating a record requires a full licence.

Can I reduce users at renewal?

Many SaaS contracts allow increases at any time but decreases only at renewal, and some set a minimum. Ask before you sign.

Is per-user or usage pricing better for a growing business?

It depends on what grows faster: your staff or your transactions. Model both against a three-year growth plan.

Do seasonal staff need permanent licences?

Some vendors allow temporary or flexible licences; others require a full year. Ask how seasonal peaks are licensed.

Sources

• Competition Bureau Canada — guidance on misleading representations, including pricing claims
• Canada Revenue Agency — audit trail and record-keeping expectations for business systems
• Innovation, Science and Economic Development Canada — small business and technology adoption resources