Buying decisions should follow business outcomes, not feature checklists: “Which process must close without Excel this month?” EQLEM’s modular licensing supports exactly that. You open each business module and each access channel separately — WEB, MOBILE, and B2B. EQLEM is a Solution Platform; the license model matches that flexibility.
How to read the matrix
Every process row in the Modules catalog (stock, sales, finance, CRM, POS, e-document…) can be licensed independently. Channels for the same module are also separate:
- WEB — Platform Web office and operations surface
- MOBILE — Flutter field / mobile
- B2B — Buyer web and mobile portal: catalog, cart approval, orders, shipments, invoices, payment records, returns
The tenant panel shows which combinations are open; the UI only exposes licensed surfaces. Opening web does not automatically grant mobile — channels are distinct.
A typical growth path
Start with Platform Web plus core modules (stock, sales, definitions, company). Add e-document and finance next. When field intensity rises, open MOBILE; when the partner channel grows, open B2B. Teams that need sync with an existing system / ERP plan system sync separately. Everything stays in one tenant; the data model does not fragment.
e-Document also uses a consumption-based credit model. Module license opens the e-document process; credit manages periodic document usage. That split lets you grow without forcing a fixed mega-pack.
License plus authorization
License opens the surface; granting a user action rights completes with authorization. “Why does this user see B2B?” is answered at the role + license intersection. Multi-company scope keeps branch and warehouse boundaries — even with license open, users stay inside scope.
Relation to product surfaces
Licensing also maps to Products. Platform Web, Mobile, B2B, and Integration are separate channels/surfaces; stock or CRM inside them are module licenses. A narrow pilot and later expansion is natural. Keep unused surfaces closed so training and change management stay aligned with what you license.
Who decides?
IT and system admins build the matrix. Finance wants a clear answer to “what are we paying for?” Operations wants to open only the channels teams actually use — warehouse mobile or partner B2B. In multi-branch setups some teams stay web-only while field teams use mobile — licensing reflects that.
Purchasing can plan additions against the roadmap: every capability is not a “big upgrade.” The dashboard and tenant panel keep open license rows visible; support looks at the same matrix. When you open the B2B channel, keep scope aligned with the inventory: for example, B2B does not add a new virtual POS integration, and service requests require CRM.
Next step
Decide which processes are daily-critical in your tenant. Start with Platform Web plus two or three modules; open channel licenses when the team is ready. See modular licensing and the Modules catalog for details.