ERP Migration & SelectionFree referencePDF, Excel, Word export

ERP Licensing Models Reference: Named User, Concurrent, Subscription and More

ERP cost comparisons fall apart when vendors count different things. This reference lists the licensing models you will meet in an RFP response, what each one actually measures, and where buyers are usually caught out.

Download:

Licensing model	What is counted	Typically suits	Where costs surprise buyers
Named user	Each identified person with a login	Stable, well defined user population	Shared or role-based logins breach terms; leavers must be reassigned
Concurrent user	Peak simultaneous sessions	Shift work, many occasional users	Peak definition and measurement method; session timeouts
Full-use / professional user	Users with broad create and edit rights	Planners, buyers, accountants	Tier is set by the most capable role the person holds
Limited-use / light user	Users restricted to approvals, self-service or read access	Managers, approvers, shop floor entry	Vendors can reclassify you if rights drift beyond the restricted role
Employee-based	Total employee headcount	Enterprise-wide access, HR-heavy suites	Cost grows with headcount even if few people use the system
Perpetual license plus maintenance	One-time fee, annual support percentage	Long planned on-prem deployments	Annual maintenance uplifts and cost of re-licensing on version changes
Subscription (SaaS)	Recurring fee per user, module or tier	Cloud ERP with predictable growth	Renewal uplifts, price caps absent from the contract
Module-based	Each functional module licensed separately	Phased roll-outs	Adding a module later is priced at then-current list
Tiered by revenue	Company revenue band	Mid-market suites	Revenue growth silently moves you to a higher band
Transaction or volume based	Orders, invoices or documents processed	Distribution, EDI heavy businesses	Seasonal peaks and integration traffic inflate counts
Consumption based	Metered compute, storage or API calls	Variable workloads, AI and integration use	Hard to forecast; ask for caps and alerts
Device or workstation	Registered terminals or scanners	Shop floor, warehouse handhelds	Shared devices still count; new scanners add cost
Site or enterprise license	Unlimited use within a legal entity or site	Large user counts at few sites	Acquisitions and new entities may fall outside the grant
Database or instance based	Number of production instances	Multi-company consolidation	Non-production environments often charged separately
Indirect or digital access	Third-party systems reading or writing ERP data	Heavily integrated landscapes	Integrations, portals and bots can trigger extra licensing
Bring your own database license	Customer supplies the DB engine license	Existing enterprise database agreements	Database vendor audit exposure sits with you

General descriptions of common models. Each vendor defines its metrics in its own contract, so always confirm definitions against the actual order form and license terms.

Licensing review of your ERP quote

An optional read-through of your vendor quote against your real user and integration pattern.

Optional. The tool and every export work without this. No spam.

How to use this lookup

Search for the model name a vendor used in its quote, then read the right-hand column before you compare prices. Two quotes with the same headline number can differ by a wide margin once you convert both to the same unit, such as total cost per active user per year over five years. Ask every vendor to state the metric, the measurement method and the audit rights in writing so you can line the answers up side by side.

Named versus concurrent counting

Named user licensing is simple to audit but punishes organizations with many occasional users. Concurrent licensing looks cheaper for shift operations, yet the vendor decides how a session is measured and what happens at the peak. Model your real login patterns for a full month before choosing, and ask whether read-only and approval-only users are free, discounted or counted at the full rate.

Count users by role, not by department
Include integration accounts and service users
Ask how leavers and role changes are handled

Subscription and consumption pitfalls

Subscription pricing moves cost from the project budget to the operating budget, but it also introduces renewal risk. Look for a cap on annual increases, a right to reduce quantities at renewal, and clarity on what happens to your data on termination. Consumption pricing adds a forecasting problem: AI features, API calls and storage can grow faster than headcount, so ask for usage alerts and a hard spending ceiling.

Common mistakes

The most frequent errors are comparing a perpetual quote without maintenance to a subscription quote with support included, ignoring non-production environments, and forgetting indirect access from portals, EDI and reporting tools. Another is buying every module on day one when the plan is phased. Price each phase explicitly and lock the price for later modules in the contract.

Frequently Asked Questions

Is named user or concurrent licensing cheaper?

It depends on usage. Concurrent suits shift patterns where few people are logged in at once, while named user suits a stable team. Measure peak simultaneous sessions and total distinct users for a month, then price both options before deciding.

What is shelfware in ERP?

Shelfware is licensed software or user seats you pay for but do not use. It usually arises from buying all modules up front or over-sizing user counts. Phase purchases and negotiate the right to reduce quantities at renewal.

What is a license true-up?

A true-up is a retroactive charge when your actual usage exceeds what you licensed, found through a vendor audit or self-reporting. Understand the measurement method and the price used for the excess before signing.

Do integrations need their own licenses?

Sometimes. Some vendors charge for indirect or digital access when third-party systems read or write ERP data. Ask the vendor to confirm in writing how your portals, EDI, reporting tools and bots are treated.

If you want a second opinion on how a vendor's licensing terms will translate to your real user and integration pattern, Netray can review the quote with you. The reference above works fine without us.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

Back to All Tools