Stock transfer
Moving goods between your own locations — shop to godown, branch to branch — recorded as a dispatch at one end and a receipt at the other.
A transfer is not a sale, but it is still a movement that has to be recorded twice: goods leaving one location and goods arriving at another. Between those two events the stock is in transit and belongs to neither.
Why the receiving end matters most
Transfers recorded only as a dispatch are the most common reason a location's stock is wrong. The sending branch shows the stock gone, the receiving branch never showed it arriving, and the total is short until the next physical count finds it.
Short and damaged transfers
Ten cartons leave, nine arrive. That difference has to be visible as a difference, not silently absorbed at either end. Record what was received, and let the gap be investigated while the transporter can still be asked about it.
The compliance side
A movement between your own godowns can still need an e-way bill above the notified value, and it moves on a delivery challan rather than a tax invoice. If the two locations are in different states with separate GST registrations, the treatment is different again — confirm it with your tax advisor.
How KillStock handles it
Multi-location stock supports transfers between locations with a receipt recorded against the transfer, so in-transit stock is visible and the two ends have to agree. Delivery challans are raised for the movement, and where an e-way bill is needed its details are prepared from the same document.
A common mistake
Adjusting stock up at one branch and down at the other instead of raising a transfer. The totals match; the trail is gone, and so is any way of proving what was sent.