In EQLEM, licensing is not “all platform or nothing.” You open each business module and each access channel separately: web, mobile and B2B. Start with inventory and sales, add e-documents later, or stabilize office web before giving the field mobile access. The licence model is built for that flexibility.
Modular licensing ties purchasing to operational reality. Channels you do not use stay closed; as needs grow, you open new license rows in the same account. On e-documents, a usage-based credit model also applies; you scale with document volume.
Who is it for?
IT and system admins own the license matrix. Finance and procurement want a clear answer to “what are we paying for?” Operations leaders open the channels teams actually use: warehouse mobile, dealer B2B, office web. In multi-branch setups, some teams may work web-only while field teams use mobile; licensing reflects that.
How it works
Each module (for example inventory, sales, finance, CRM, POS) can be licensed independently. Channels are also separate for the same module: Platform Web, Mobile, and B2B. The admin panel shows which combinations are open, and the interface only offers what is licensed.
A typical path: Platform Web plus core modules (inventory, sales, definitions, company) first. Then e-documents and finance. As field intensity grows, MOBILE; as the dealer channel grows, B2B. Teams that need sync with an existing system / ERP open integration separately. Everything stays in one account; the data model does not fragment.
e-Document credits track send/consumption volume while the module license keeps the e-document process available. That split lets you grow without forcing a rigid all-in package.
Benefits
You pay for and open only what you use. Pilots stay narrow; production expansion is natural. Channel separation removes pressure to “open mobile for everyone,” so risk and training stay controlled. You grow on the same platform instead of jumping to a second software family.
License visibility also helps support and audit: “Why does this user see B2B?” is answered at the role + license intersection. Procurement can plan additions against a roadmap without every capability becoming a major upgrade.
Relation to modules and products
Licensing maps to every process row in Modules and to the channels on the Products page. Platform Web, Mobile, B2B and Integration are access channels; inventory or CRM inside are module licenses. Authorization completes licensing: even when a license is open, users still need action permissions. System sync is planned together with the Integration product.
FAQ
Must I buy every module upfront? No. License what you need and expand in the same account later.
Does web automatically include mobile? No. web, mobile and B2B are licensed separately.
What are e-document credits? While e-document processes are enabled, document consumption is tracked with credits and planned by volume.
If a license closes, is data deleted? Licensing closes the screen; data policy and continuity are handled under your setup/agreement. Confirm operational transition with support.
Next step
Decide which processes are daily-critical in your account. Start with Platform Web plus two or three modules; open channel licenses when teams are ready. Try Free to see your matrix, or pick scope from the Modules catalog.