Multi-location business management that keeps sites comparable without merging them.
Workspaces, branches, stores, teams, and warehouses give each site a real scope, and the consolidated view reads from the same underlying records rather than from a monthly export. For retailers, distributors, and service businesses whose second or third site turned a single-counter process into a group operation.
What breaks when a second site opens
Nothing fails dramatically. Each site develops its own habits, the owner learns about them from whichever report arrives first, and the group view becomes a set of numbers that are close enough to be believed and wrong enough to be unhelpful.
Two branches count the same evening and disagree
Both produce different numbers for products they both claim to hold. Because every sale and receipt moved a real balance, the drift is traceable — which is the conversation that is impossible from a spreadsheet alone.
Head office cannot compare like with like
One site discounts heavily and logs nothing, another is strict, and the group total looks acceptable. The number is right; the meaning is not.
Permissions follow the person, not the site
A manager who moves between sites keeps the access they had, and access they should lose follows them out. Scope is what fixes this.
Consolidation is a spreadsheet exercise
Group numbers arrive from a manual export built the night before, so nobody can trace a total back to the transactions underneath it.
The order that keeps a multi-site rollout coherent
Scope first, then people, then transactions, then consolidation. Reversed, it becomes a spreadsheet project.
Decide workspace or branch
Separate operations get separate scope; several counters under one operating model stay in one workspace with distinct sites. Write the reason down, because it decides every permission after it.
Open the site
Branches, stores, teams, and warehouses are created first, with the counters, devices, and storage points each one actually has.
Scope the people to the site
Roles are held inside a scope, so a store manager can be an admin at one site and a member at another — or at neither, which is a legitimate answer.
Bill with location awareness
Invoices, payment methods, and the stock position attach to the operating location, so a day at one counter is not tangled with another.
Close each site, then consolidate
Close the shift and the location before you consolidate periods, payment totals, transfers, variances, and exceptions — in that order.
Compare sites and act on the difference
Once the numbers come from the same records, the question stops being which spreadsheet to believe and becomes which site needs attention.
Balances held per warehouse, reviewed together
Shown from a dedicated Nox-Billings deployment, which remains available as a scoped custom deployment for multi-counter trading businesses. In the unified NoxOrigin app, the same records live in Commerce.
Where this is the wrong tool
Multi-site management sounds generic, and it is worth being specific about which problems this does and does not address.
Not a group consolidation or ERP
Inter-company accounting across separate legal entities, statutory consolidation, and treasury management are accounting functions, not site-operations ones.
Not a franchise or territory engine
Royalty calculation, territory design, and franchisee compliance are not part of the workspaces and branches model. If that is the core requirement, say so before rollout.
Not a warehouse automation system
Barcode scanning, conveyor, and WMS integrations are not covered here. Locations and warehouses are the structure stock lives in, not the machinery that moves it.
Multi-site does not mean multi-currency
The commercial model is built for Indian billing in rupees with GST treatment. Group reporting in other currencies belongs with your accounting package.
Priced on the structure you actually need
Public NoxOrigin plans carry workspace and user limits: the Agency plan includes 3 workspaces, and beyond that a workspace is a listed add-on at ₹750/month (+1 workspace), with team members at ₹500/month (+5 users). Larger estates and dedicated environments are scoped as a custom deployment after your site list, hardware, and connectivity are reviewed.
Multi-location management questions
Should each location be a workspace or a branch?
That is a decision to make deliberately rather than a default to inherit. Workspaces, branches, stores, and teams exist so a group with genuinely separate operations can keep separate records, while a business with several counters and one operating model can be one workspace with several sites inside it. The consolidated view reads from the same underlying data either way, rather than from a monthly export.
Can we compare sites without merging them?
Yes. Balances and activity can be held per warehouse or location while the group view is read from the same records, so a group-level number and a shop-level number are not two different truths that have to be reconciled by hand.
Can each location have different staff and permissions?
Permissions are workspace-scoped, and roles are what people hold inside a scope. Location-aware access and per-site roles are part of the operating model, though the exact setup should be reviewed for your team — a counter that shares a device with a warehouse is a different setup from a branch with its own manager.
How does stock move between locations?
Transfers are recorded as operational movement, with the source and destination visible, so a two-branch stock count disagreement becomes traceable rather than mysterious. Warehouses and their balances are modelled separately, which is what allows stock to be held apart where the operation is genuinely separate.
How many locations can we run?
The plans carry workspace limits rather than a hard location count: the Agency plan includes 3 workspaces, and additional workspaces are listed as a paid add-on alongside additional team members. Larger estates, dedicated environments, and multi-location rollouts are scoped as a custom deployment rather than sold as a self-serve seat count.
Does this replace our accounting package or ERP?
No. It produces the operational records — site activity, stock movement, invoices, payments, and day-end — that a ledger needs. Group consolidation, statutory reporting, and anything that must reconcile across separate legal entities stay with the tools built for them.
Bring your list of sites and the question you cannot answer about them.
Whether the group number or the site number is the one you cannot trust, that is the right place to start. We will map the scope before quoting anything.