In this guide 6 sections
Godown stock drifts because goods move before paper does. Trucks leave Delhi without a transfer entry, the other state’s registration gets its own invoice series, and counts happen weeks apart. Fix it with one transfer document per load, a daily receipt check at the godown and a weekly count of fast movers.
Where the gap starts
Most mismatches begin at the gate, not in the books. A tempo loads forty cartons at Sadar Bazar at six in the evening. The transfer note is written next morning, if at all.
By then the godown in Ghaziabad has already sold ten cartons to a walk-in buyer. The office still shows all forty sitting in Delhi. Two records now disagree. Nobody knows which one to trust, and the accounts head spends Saturday matching carton counts against a pile of handwritten gate slips and half-readable WhatsApp photos of loading lists.
Walk the route from shop floor to vehicle once with a notebook. Mark every spot where a carton can pass the gate while no one holds a transfer slip. Night dispatch, a favour for a regular retailer and a returned item sent straight back to the godown are the usual three.
- Night loading with no transfer note
- Cash sales made at the godown and written in a notebook
- Returns routed to the godown instead of the office
- Damaged cartons written off by hand, never entered
- Item names spelt differently in the two locations
Why a second state registration makes it worse
A godown in Gurugram or Sonipat sits under another state’s tax registration. Stock sent there is not a simple move between shelves. It needs a proper document with its own number, and your accountant will tell you which one applies.
The trouble is that the Haryana or Uttar Pradesh side often keeps its own invoice series, sometimes in a separate Tally company. Delhi sees a transfer out. The godown sees nothing coming in until someone keys it.
Treat each registration as its own location inside one stock master. Use the same item codes, pack sizes and units everywhere, so a transfer matches line by line. Then a transfer is a single entry that lowers one location and raises the other, and nobody types it twice.
The daily transfer routine
Give every load a transfer number before the vehicle moves. Print it in triplicate: one for the driver, one for the godown, one for the office file. Nothing leaves without it.
At the godown, the keeper ticks each line against what actually came off the truck. Short cartons and broken packs are noted on the same sheet. This takes ten minutes and saves a week of arguing.
By evening the office compares transfers sent with transfers received. Anything open for more than one day gets a phone call. A truck that left Monday with no receipt by Wednesday evening is worth chasing now, while the driver still remembers the stops.
- Transfer number, date, vehicle number and driver
- Item code, pack size and quantity sent
- Quantity received, short, broken and signed by the keeper
- Evening match of sent against received
Counting without shutting the godown
A full stock-take is a bad habit for a trading godown. It stops sales and still misses errors. Count the fast movers weekly and the slow ones monthly.
Pick the twenty items that carry most of your turnover. Count them on a fixed weekday, before the first sale. Compare each count with the system quantity, then write down the difference and the reason beside it, even when the reason is only that nobody knows yet.
Patterns show up quickly. One keeper’s shelf always runs short, or one pack size is always miscounted. You fix a habit, not a number. Once the same three items come up short every Thursday, someone can stand at the loading bay on Wednesday night and see exactly what goes wrong.
What the software should do for you
A good stock system shows each location separately and the total together. It blocks a sale when the godown shows zero, or at least warns the sales desk. It keeps goods in transit as their own balance, so a loaded truck counts as neither Delhi stock nor godown stock until the keeper signs. Reports then show three columns.
Ask any vendor to show you one transfer from dispatch to receipt, with a short quantity. If the demo cannot do that cleanly, your real days will be harder.
This week, take one godown and list the last ten transfers. Mark how many had a document before the truck left. That single count tells you where to start.
Godown transfer and count sheet
A one-page sheet in two halves. The top half is the transfer slip: transfer number, date, vehicle, driver, item code, pack, quantity sent, quantity received, short or broken, keeper’s signature. The bottom half is a weekly count grid for twenty fast movers with system quantity, counted quantity, difference and reason.
Open a blank worksheet to printQuestions owners ask
Should the godown keep its own stock register?
Yes, but only as a working copy of the shared record. The keeper ticks receipts and counts on paper or a phone, and the office enters them once. Two separate registers always drift.
How often should godown stock be counted?
Count the fastest twenty items every week and the rest monthly. A single yearly stock-take finds problems too late to trace.
Can Tally handle a godown in another state?
Tally can hold separate godowns and branches, but the setup matters. Ask your accountant whether the other registration needs its own company file, then keep item names identical in both.
What if a sale happens at the godown before the transfer is entered?
The system should warn or block it. Without that, the keeper records the sale on the slip and the office enters the transfer first, then the sale.
