In the purchasing meeting, the vendor suggests all packages at once and the price comes as a single line. Meanwhile, the team only wants field sales and stock visibility; the remaining modules will stay disabled for a long time.
In this table, if the license model is chosen incorrectly, unused features are billed and budget trust is shaken. The right model is to enable what is needed and keep the rest disabled.
In this article, we explained how modular licensing works, the distinction between modules and channels, e-document credits, and the logic of expanding as you grow.
Table of Contents
What is a modular license?
A modular license is a model where, instead of purchasing the entire platform as a single block, the required parts are enabled separately. Unenabled modules neither appear on the screen nor fall onto the invoice as a line item.
EQLEM is a solution platform, and this model suits gradually growing your operational surface without replacing your existing ERP system. The goal is not to buy everything from day one, but to proceed in the right order.
In classic packages, unused features are also charged, which inflates the budget. In a modular structure, costs are aligned with the actually utilized scope.
License decisions are business decisions, not technical ones; which team will perform which job must be clarified upfront. An unclear scope leads to unnecessary openings later on.
For the first-step choice, you can check the article which module to start with.
Module-based enabling
Each module covers its own business area; areas such as inventory, sales, purchasing, or CRM are separate license lines. This separation allows managing one team's needs independently of another.
When the module is opened, the relevant menus, entry screens, and reports become visible. A closed module, on the other hand, takes up no space in the interface and creates no training burden.
The decision to launch should be tied to pilot results; a module is expanded only if it is truly being used. Keeping an unused module open for months is a waste of money.
There are data links between modules, but there is no licensing dependency; for example, while orders exist, the invoicing module can be opened later. It is necessary to clarify dependencies together during setup.
We covered the pilot scope in the digital transformation pilot project article.
Channel license: web, mobile, B2B
The same module generates different usage across different channels; the office uses web while the field wants mobile. Channel licensing makes this difference visible on the invoice.
The web channel is generally for management and office operations; lists, reports, and approval flows are concentrated here. The mobile channel, however, focuses on field tasks such as visits, orders, and collections.
The B2B channel is the ordering interface opened to dealers and business partners; it is not necessary to give mobile to every user. Choosing the channel according to the business model prevents license waste.
Opening every channel to everyone both increases costs and creates notification noise. Giving the right channel to the role that needs it is sufficient.
We detailed the channel distribution in the mobile or web article.
e-Document credit model
e-Invoices and similar documents depend on usage volume; a fixed monthly package does not suit every business. The credit model makes it easy to plan based on the actual document count.
Credits are consumed periodically, and the remaining balance must be trackable. A surprise quota exhaustion halts operations on billing day.
Document volume fluctuates in seasonal businesses; therefore, the peak month should be taken as a basis, not the average. A wrong estimate creates the risk of either overpaying or disruption.
Credit and license are separate concepts; even if the module is open, the document quota is managed separately. Not confusing the two makes budget reading clear.
We explained the planning in the how to plan e-document credits article.
How to choose a starter package?
The initial package should be a narrow scope that resolves the most painful issue. A broad package creates excitement, but training and data load slow the project down.
Three questions are enough for selection: which team, which entry, which channel. If these three answers are not clear, the package is not ready yet.
If the existing ERP already handles accounting, field and operations take precedence over accounting on the platform. Creating a dual layer generates unnecessary costs.
Set a measurable goal initially; for example, reducing order entry time by half. Without a goal, license expansion becomes random.
We gathered the software selection framework in the 10 questions when choosing software article.
How does it scale as it grows?
Expansion should be tied to the measured success of the pilot; if there is no usage, new modules should not be opened. This discipline protects the license budget.
The second wave is usually reporting, authorization depth, or an additional channel. The first wave generates records, while the second strengthens control.
When the number of companies or branches increases, the scope license is also reviewed. A model established for a single company may remain insufficient in a holding structure.
The expansion schedule should be kept in writing and matched with invoice lines. Verbal promises generate surprise lines at the end of the month.
For multi-structures, see the multi-company structure article.
Reading the invoice line
In a good invoice, the equivalent of each line is clear; the module, channel, and credit appear separately. A confusing single line makes cost control impossible.
The number of users should not be confused with the license line; sometimes the channel license is independent of the user. Do not make a decision without verifying the unit in the contract.
Periodic campaigns and temporary trial licenses should be tracked separately. Get a warning against automatic charging when the trial period ends.
Compare the usage report with the invoice line at the end of the month. If there is an unused line, do not delay the cancellation request.
License discipline is considered together with role-based authorization; unauthorized users also generate unnecessary licenses.
Wrong license choices
The most common mistake is opening all modules just in case they might be needed in the future. Empty menus tire the team and prolong the training period.
The second mistake is opening the mobile channel to office users as well. The cost of an unused channel is invisible but accumulates.
The third mistake is planning e-document credits based on the average month. When the quota runs out in the peak month, operations halt.
The fourth mistake is double-licensing the platform and the existing ERP for the same work. If role division is not clear, double payment is inevitable.
We explained the collaboration model in the platform alongside existing ERP article.
Relationship with existing ERP
EQLEM is not designed to replace your existing ERP system; financial record keeping usually stays there. The platform fills the field and operation gaps.
Therefore, when choosing licenses, it is natural to prioritize operation modules rather than accounting. Licensing the same job in two places is a waste.
Synchronization scope also affects the licensing decision; it must be clear which records will be transferred. Unnecessary data types create both integration and licensing burden.
Systems like Mikro or Logo can remain as the master records; the platform works side by side with them. New capabilities are unlocked without a replacement project.
We clarified the location difference in the solution platform or ERP article.
Practical checklist
For the first month, open only the modules that solve a single main pain point. Do not add new lines in the second month without looking at usage metrics.
Write the channel distribution on a role basis; do not give every channel to every user. This list is the basis of invoice control.
Estimate the peak month for e-Document and leave a ten percent margin. Add the quota expiration warning to your operation routine.
Review unused license lines every three months. An idle line is a candidate for closure.
While the scope grows, update the branch and warehouse scope definition as well.
Frequently asked questions
Do I pay for a module I haven't activated?
You do not; inactive modules do not enter the invoice and are not visible in the interface.
Is it hard to add modules later?
No; once the need is clear, the license line is opened and the relevant menus become visible.
Is the channel license independent of the number of users?
It depends on the model; do not decide without clarifying the unit in the contract.
Will my existing ERP license be affected?
No, it won't; the platform works alongside your existing ERP system and does not cancel its license.
Modular licensing is a budget discipline that ensures you don't pay for unused features. Buying the entire package at once often reflects a sales pitch rather than actual needs.
Keep the initial scope narrow and expand based on pilot results; this order keeps both costs and training under control.
Assign channel distribution by role; giving mobile to the office and unnecessary web to the field is a waste.
Plan e-Document credits according to peak months; monthly averages are misleading.
Maintaining your existing ERP setup while only exposing the operational surface enables low-risk growth.
By consulting with the EQLEM team, you can clarify your licensing scope.