Inventory

Running more than one godown without losing the count

19 Nov 2026 · 4 min read · ERPsysi Team

One godown is a list. Two is a question: where is it? Three is an argument, because by then the answer depends on who you ask and when they last looked.

Decide what a transfer is

The thing that breaks multi-location stock is not the software, it is that nobody agreed what a transfer means. Is stock out of the first godown when the van leaves, or into the second when it arrives? Both are defensible. Only one can be true in your books, and until it is written down the two counts will never tie.

Make the count a check, not a reconstruction

If the system knows what should be on each shelf, a physical count is a comparison and takes an afternoon. If it does not, the count IS the record, and everything between counts is an estimate. Barcode in and barcode out is what turns the first into the second - not because scanning is clever, but because it is faster than writing, so it actually gets done.

Give people their own logins

Multi-godown and multi-user arrive together. One shared login means every entry is by "admin" and no mistake has an owner - not for blame, but because you cannot ask a question about an entry when you do not know who made it. Separate logins with their own rights cost nothing and settle most of those arguments before they start.

Then the reports are worth reading

Once the count is trustworthy, item-wise stock by godown, dispatch with proof, and a dashboard that shows today rather than last month all start being useful. Before that they are just a faster way to circulate a number nobody believes.

ERPsysi runs multi-user and multi-godown as standard, with barcoding, dispatch and module-wise reports over the top. A demo on your own item list is the quickest way to see whether it fits.

Updated 19 Nov 2026

More from the blog

See ERPsysi running on your own numbers

A demo takes about thirty minutes. No obligation, and nothing to install.

Book Free Demo +91 87009 95511