Licensing Model
A licensing model defines the terms and price under which an ERP system may be used – as a one-time perpetual license, a monthly subscription (SaaS), per user, per module or usage-based. It determines the right of use, cost structure and contract term.
A licensing model describes the contractual and pricing basis on which software – in the ERP context, the entire inventory management and administration system – may be used. It governs three things at once: the right of use (what may be used and for how long), the pricing metric (what the price is calculated on – users, modules, revenue, documents) and the payment form (one-time purchase or recurring fee). This makes the licensing model the actual lever that turns a software feature into a concrete price and a contract.
For companies, the licensing model is far more than a pricing question. It determines whether costs are incurred as an investment or as ongoing operating expense, how flexibly you can scale up or down as you grow or shrink, and how strongly you are tied to a vendor in the long run. Two ERP systems with identical functionality can differ considerably in total cost over five years purely because of their licensing model – which is why the model is an integral part of any serious ERP selection.
At a glance
- Licensing model = the framework of right of use, pricing metric and payment form
- Basic types: perpetual license (one-time) vs. subscription (recurring, usually SaaS)
- Common metrics: per named user, per concurrent user, per module or usage-based
- Determines cost structure (CapEx vs. OpEx), scalability and degree of vendor lock-in
- Central to TCO and ROI calculations – not just the list price, but the pricing logic
How a licensing model is structured
Every licensing model combines several building blocks. The first is the type of right of use: with a perpetual license, the company acquires a permanent right to use the respective software version – usually against a high one-time payment plus an annual maintenance fee for updates and support. With a subscription license, the right of use is rented for a period of time; when payment stops, use stops. Cloud ERP is today almost universally provided as a subscription in the form of SaaS.
The second building block is the pricing metric – the measure the price is based on. It is the actual core of every model, because it determines how costs grow along with the company. The third building block is the contract terms: minimum term, notice periods, volume discounts, price escalation clauses and the question of whether updates, hosting and support are included or billed separately.
Per-user pricing: named user and concurrent
The most widespread metric is user-based pricing. In the named-user model, every individually registered person is licensed, regardless of how often they actually open the system. In the concurrent model (simultaneous users), by contrast, only the number of concurrently active sessions counts – favorable for companies with many occasional users working in shifts. Many vendors additionally differentiate by role: a full user in sales costs more than pure read-only access in the warehouse.
Module- and usage-based models
Instead of or in addition to users, many ERP systems price individual modules – accounting, warehouse, production, CRM – separately. That way you only pay for the functionality you actually enable. Usage-based (consumption-based) models tie the price to a business metric such as the number of documents, orders, revenue or processed transactions. They suit strongly fluctuating or seasonal business well, but make costs harder to predict.
Why the licensing model is economically decisive
The licensing model determines whether an ERP appears in the books as a capital investment (CapEx) or as ongoing operating expense (OpEx). A perpetual license heavily burdens the year of acquisition, but is then depreciated over several years and afterwards only incurs maintenance costs. A subscription spreads spending evenly, but adds up to substantial amounts over the years. Which model is cheaper depends on the observation period and the company’s cash flow – not on the list price alone.
Scalability is equally important. A user-based subscription can usually be expanded or reduced by additional licenses on a monthly basis, and a module-based model allows new functions to be switched on step by step. Perpetual licenses, by contrast, are more sluggish: additional users or modules often require renewed one-time payments. Companies that know their growth paths can choose the right model and avoid expensive re-licensing.
Licensing model and vendor lock-in
An often underestimated aspect of every licensing model is the degree of vendor lock-in. Subscription models lower the barrier to entry, but make the company permanently dependent on ongoing payments – if the subscription becomes more expensive or is terminated, operations come to a standstill. Perpetual licenses do secure a permanent right of use, but without a paid maintenance contract there are no updates and no support, which lets the version age over the years.
Beyond price alone, technical openness determines vendor lock-in. Models with proprietary data formats, closed interfaces or hard exit barriers tie you down more strongly than systems with open APIs and exportable data. Open-source ERP follows a special path here: the software itself is free, and you pay for support, hosting, add-on modules or enterprise editions – a licensing model that reduces lock-in, but requires in-house expertise or a service provider.
Evaluating licensing models correctly in an ERP comparison
Because licensing models are structured so differently, offers can only be sensibly compared via total cost of ownership (TCO), not via the stated base price. A low per-user price can quickly be overcompensated by expensive add-on modules, transaction fees or mandatory premium support tiers. Conversely, a higher package price may already include everything needed. The decisive step is to realistically map your own usage structure – number of users, required modules, document volume – onto each model.
In practice, this means calculating all cost components for a defined period of three to five years: base fee, user licenses, modules, usage-dependent shares, maintenance and foreseeable expansions as you grow. Only this full-cost view shows which licensing model fits the business model. A seasonal retailer is often better off with usage-based or scalable subscriptions, a stable mid-sized company with many full users sometimes with a perpetual license.
Distinction: licensing model vs. pricing model and deployment form
The licensing model is frequently confused with two neighboring terms. The pricing model in the narrower sense describes only the price calculation (such as tiers or discounts), whereas the licensing model additionally encompasses the right of use and the contract form – it is therefore the broader term. The deployment form in turn – cloud, on-premise or hybrid – is a technical question that often goes hand in hand with a particular licensing model, but is not the same thing.
Thus SaaS is usually licensed as a subscription, yet an on-premise system can equally be offered as a subscription or as a perpetual license. Those who draw a clean distinction avoid false conclusions: not every cloud offering is necessarily a subscription, and not every perpetual license means on-premise. Only the combination of deployment form and licensing model yields the complete picture of an ERP cost structure.
Example
Example: a retailer calculates two licensing models
An e-commerce retailer with 12 full users and 20 seasonal temps during the Christmas business compares two ERP offers. Vendor A charges 39 euros per named user and month – for 32 people that would be around 1,250 euros monthly, even though the temps only work in the system for a few weeks a year. Vendor B bills by concurrent users and prices 15 concurrent sessions at 75 euros, so 1,125 euros – regardless of how many people are registered in total.
Calculated over the year, model A looks manageable in the core business, but becomes expensive due to the many seasonal named users. Model B caps costs via concurrent usage and fits shift operations during the peak season better. The functionality of both systems is comparable – the deciding factor is the licensing model alone and how well it fits the retailer’s real usage structure.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Licensing Model in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.