More than one godown, one picture
Every action carries its godown automatically — one question at login does it. Split orders pack under godown prefixes, and totals cannot be wrong.
Two godowns, and everything happens "somewhere"
The second godown doubles more than the storage.
Every question now has a hidden first question inside it. Allotted — in which godown? Packed — from which godown? The count is short — which building are we even talking about?
One question at login locates everything
Nobody tags actions with a godown, because nobody would keep doing it.
Nobody tags an action with a godown, because nobody would keep doing it.Instead the system asks each person once, at login, which godown they are working in — and asks again at the mid-day check-in, for the man who moves between buildings.
Asked once, at login
And again at the mid-day check-in, for the man who moves between buildings.
Located without locating
The allotment, the checking, the packing, the receipt, the count — each carries its godown on its own.
The same by-product rule
The one that runs the whole platform: the record is what the work leaves behind, not a second job beside it.
Each godown is named in settings; add and change them as the business grows.
Split orders pack under prefixes, and the total cannot be wrong
Dispatch then knows precisely how many boxes to collect from which building and what the grand total must be.
The division and the fusion are system-made — so the number on which a short-delivery dispute turns cannot be wrong.
Audits stay inside one godown, deliberately
A stock audit runs within a godown, not across them — and the reasoning holds from both directions.
If your ERP maintains godowns, a given item most likely lives in one, so the audit lock applies where the item is. If your ERP does not maintain godowns, then it cannot say where the item is either — and the lock must apply globally.
Your ERP maintains godowns- An item most likely lives in one — so the audit lock applies where the item is
- The audit runs within a godown — which is where the stock actually is
Your ERP does not- Then it cannot say where the item is — and neither can anything reading from it
- So the lock applies globally — honest about what the books can answer
Either way, the boundary is honest about what the books can and cannot answer.
Every located action leaves a stamp
Who did it, when, and now also where — the godown rides on every record automatically.
Nobody wrote this. Each line is the act of doing the work.The second godown stops costing you the picture
Actions locate themselves. Split orders count themselves.
The question inside every question — which godown? — is already answered before anyone asks it.
Run one split order across two godowns and read the totals it produces.
Ask for a demo