Many businesses do not run as a single tax ID in a single location; they operate as holdings, branch networks, or multi-warehouse operations. EQLEM lets you manage company, branch, and warehouse scope in one account. Users see only the organization slice they are allowed to see; inventory, sales, and finance records write to the correct context. So you do not need a separate install per company; all of it sits in one database, in separate scopes.
Scope is configured with authorization. When definitions are clear, risk of selling to the wrong warehouse or seeing another branch’s account movements drops.
Who is it for?
Multi-branch retail, distribution warehouses, structures that split production and sales companies, and franchise-like networks. Central finance wants consolidated visibility; branch operations want to manage their own stock. IT wants to define companyId and branch/warehouse scope once and maintain it. Firms with warehouse groups can cluster physical locations logically.
How it works
Under company and system management you define companies, branches, warehouses, and warehouse groups. User sessions and records bind to those identities. List and document screens default to the user’s scope; authorized users may switch scope.
Example: a sales rep opens an order in branch A; warehouse B only sees its own transfers; central accounting accesses finance lists across companies. Stock vouchers carry warehouse identity; waybills and invoices progress in company/branch context. Business partners and master data sit on the same organization language.
Mobile field teams work with a selected warehouse/branch, reducing wrong-location movements. B2B buyers see catalog and orders by their account–company links. When syncing an existing system / ERP (Mikro, Logo, Piconn), mappings use the correct company and warehouse codes; otherwise you get duplicates or wrong stock locations.
Benefits
You manage many locations in one account without fragmenting UX. Security and operations speak the same language: “this warehouse” is both a filter and a permission boundary. Branch and warehouse report breakdowns become meaningful because records were written with the right scope from the start. Growth means adding definitions, licenses, and roles; not a new product.
It reduces center–branch tension: the center gets policy and consolidated visibility; the branch keeps daily speed. In audit, “which company was this issued for?” is readable from the record.
Relation to modules and products
Inventory, sales, purchase, finance, POS, and manufacturing modules are sensitive to warehouse/branch context. Company and business partners definitions build the backbone. Platform Web is the main place to manage scope; Mobile applies field scope. System sync mappings depend on company/warehouse keys. Document entry and list experience take default filters from this scope.
FAQ
Does every company need its own account? In most scenarios, multi-company in one account is enough. If legal/isolation needs require it, evaluate a separate account; the default path is one account with separate scopes.
What is a warehouse group for? It helps cluster physical warehouses for reporting and operations.
Can a user switch company? Yes if permission and configuration allow it; otherwise they stay in a fixed scope.
Which company does sync write to? It writes according to company/warehouse codes defined in integration mapping. Mapping setup is required.
Next step
Map your organization as company → branch → warehouse, then attach roles to that tree. Try Free to set the first scope, then lock action permissions with authorization.