Why branch stock stops matching once you add a second location
Multi-branch stock control comes down to one rule: every unit of stock must belong to exactly one location at any moment, and every movement between locations must be recorded by the person who sends it and confirmed by the person who receives it. This guide is for owners and store managers running two or more shops, or a shop plus a godown, who want branch-wise stock figures they can trust. By the end you should be able to set up your locations, run transfers with a challan, decide who buys for whom, audit each branch and give staff the right permissions.
Consider an illustrative case. A household goods retailer has a main shop in Ranchi, a smaller outlet in Ramgarh and a godown on the edge of town. The Ramgarh manager phones the godown for ten cartons of steel containers. The godown keeper loads them on the evening tempo but writes nothing down. Next morning the system still shows the cartons in the godown, the outlet sells three of them against stock its own screen says it does not have, and a month later the godown count shows a 'shortage'. The total stock across the business was never wrong. The location of that stock was.
Almost every multi-branch stock problem is a version of this story: goods moved without a document, goods received without a check, or a count adjusted without a reason. Software helps a great deal, but only after the process behind it is clear.
Set up locations, the item master and opening stock first
Before any transfer can be tracked, the system has to know what your locations are and what your items are called. Mistakes made at this stage repeat in every report afterwards, so it is worth a few careful days.
List every place stock can sit
Write down each shop, each godown and any other place goods are kept for more than a day. Many businesses also keep a separate location for damaged or returned goods so they are not counted as saleable. If you send goods out in a van for route sales, treat the van as a location too, so the stock on it does not appear to be sitting in the godown.
| Location | What it holds | Who is responsible |
|---|---|---|
| Main shop | Saleable stock on display and in the back room | Shop manager |
| Branch outlet | Saleable stock for that outlet only | Branch in-charge |
| Central godown | Bulk stock received from suppliers before it is sent to branches | Godown keeper |
| Damaged / returns area | Goods waiting for supplier return, repair or write-off | Store or purchase person |
| In transit | Goods dispatched from one location and not yet received at another | The sender, until the receiver confirms |
Use one item master for all branches
Each item should have one code, one name and one barcode across the business. If the outlet calls it 'SS container 1L' and the main shop calls it 'Steel dabba 1 litre', branch reports cannot be compared and every transfer risks creating a duplicate item. Agree naming rules for brand, size and pack size once, and allow only one or two people to create new items.
Count opening stock on one cut-off date
Count every location on the same day, ideally after closing, and enter each count as the opening stock of that location. Counting the main shop this week and the godown next week builds in errors from the goods that moved in between. If you cannot count everything in one day, stop transfers between the locations until all counts are entered.
Running transfers with a challan and an in-transit stage
A transfer is not finished when the goods leave. It is finished when the receiving branch counts them and confirms. Treating the time in between as its own stage, usually called in transit, is what stops stock from being counted twice or not at all.
- Request: the branch raises a request for items and quantities, so the godown is not working from a phone call or a WhatsApp voice note.
- Dispatch: the godown picks the goods and prints a transfer challan or slip showing items, quantities and the receiving location, and a copy travels with the goods. Stock leaves the godown and moves to in transit.
- Receive: the branch counts what actually arrived against the challan, not against its original request, and confirms receipt. Only then does the stock become saleable at the branch.
- Record differences: if two cartons are short or one arrives broken, the receiver enters the actual quantity, and the difference stays visible until someone investigates it instead of disappearing into an adjustment.
- Review: once a week, someone checks the list of transfers still in transit. A challan that has been open for days between two shops in the same town needs a phone call, not patience.
One rule worth enforcing without exceptions: no goods leave any location without a transfer document, even when the owner personally carries a box to another branch.
GST paperwork for moving goods between your own locations
How a branch transfer is documented for GST depends on whether both locations fall under the same GST registration. Movement between a shop and a godown in the same state under one GSTIN is usually covered by a delivery challan rather than a sale invoice. Branches in different states normally hold separate registrations, and a transfer between them is generally treated as a supply that needs a tax invoice. An e-way bill may also be needed for the movement. These rules are detailed and revised from time to time, so confirm your own case with your CA, the GST portal and the e-way bill portal. Our separate article on GST billing in Indian shops explains invoices, credit notes and e-way bills in more depth.
Central buying or branch buying: decide where purchases land
Who places purchase orders, and where the supplier delivers, shapes every other stock process. There are three common patterns, and most growing businesses end up using a mix.
| Pattern | How it works | Works well when | Watch out for |
|---|---|---|---|
| Central buying | One purchase person buys for all branches; suppliers deliver to the central godown; branches are fed by transfer | You buy in bulk and branches are close to the godown | Branches waiting on transfers; the godown becoming a bottleneck in festival season |
| Branch buying | Each branch orders from local suppliers and receives directly | Branches are far apart or sell different ranges | The same item bought at different rates; nobody checks total stock before ordering |
| Mixed | Bulk and fast-moving items bought centrally; local or urgent items bought by branches within agreed limits | Most chains of three to ten outlets | Unclear rules about which items a branch may buy on its own |
Whichever pattern you choose, set a minimum stock level for each item at each location rather than one figure for the whole business. A branch that sells two cartons a week and a branch that sells twenty cannot share a reorder point. Before buying more, the purchase person should check whether another branch is sitting on unsold stock of the same item, because a transfer costs far less than a fresh purchase. For the arithmetic behind reorder points, our article on setting reorder levels from daily sales and supplier lead time works through an example that applies to any kind of shop.
Stock audits that branch staff take seriously
A once-a-year full count tells you that stock was lost, but not when or where. Smaller, more frequent counts catch problems while people still remember what happened.
- Cycle counts: count a different group of items at each location every week, so every item is checked several times a year without closing the shop.
- Surprise counts of high-value items: mobile accessories, branded cosmetics and small electricals walk out more easily than buckets, so count them unannounced.
- Adjustments with reasons: every stock adjustment should carry a reason such as damage, expiry, counting error or theft, along with the name of the person who made it. 'Adjusted to match' is not a reason.
- Approval above a limit: let the branch in-charge make small adjustments, and require the owner or store manager to approve larger ones.
- Damage kept separate: broken or expired goods should move to the damaged location first and then be returned or written off, so the loss shows in a report instead of quietly vanishing from stock.
After each count, look for patterns rather than just the total. If one branch is short every month in the same category, the cause is a process or a person at that branch. If shortages cluster on items that were recently transferred, the transfer process itself is leaking.
Permissions: who can see, move and adjust stock at each branch
In a single shop the owner sees everything. With several branches, the safer setup gives each person the access their job needs and nothing more. This protects the business, and it also protects honest staff from suspicion when the numbers do not match.
| Role | Can do | Should not do |
|---|---|---|
| Counter billing staff | Bill from their own branch's stock and see that stock | Adjust stock, see purchase rates, create items |
| Branch in-charge | Raise transfer requests, receive and confirm transfers, make small adjustments | Approve their own large adjustments or change prices |
| Godown keeper | Receive purchases, dispatch transfers, print challans | Bill customers or delete transfers |
| Purchase person | Create purchase entries and see stock at all branches | Adjust branch stock |
| Owner / admin | See all locations, approve adjustments, manage users and the item master | Share the admin login with staff |
Two habits matter as much as the settings. Every person gets their own login, and nobody shares a password at the counter. Without that, no activity record can tell you who changed what.
Five branch reports to read every week
Reports only help if someone reads them on a fixed day. For most owners, a short weekly routine is enough.
- Branch-wise stock of your top-selling items, to spot one branch running out while another is overstocked.
- Transfers still in transit, with the dispatch date, so nothing is forgotten between locations.
- Stock adjustments by branch and by person, to see who is correcting stock and why.
- Items below their minimum level at each location, as the starting point for transfers and purchase orders.
- Stock valuation by location, so you know how much money is sitting in each shop and in the godown.
How MATROP Retail & Distribution ERP handles branch stock, and when you may not need it
Our Retail & Distribution ERP follows the process described above. Stock is held by branch or warehouse, with inward, outward, transfer and adjustment entries. Transfers use a transfer challan or slip, goods are tracked while in transit, and the receiving location confirms receipt. Minimum stock alerts and stock valuation reports are available, and the owner's dashboard shows sales, purchase, profit and outstanding. Each user gets role-based permissions, with audit logs available as an option. Barcode printing and scanning is also optional, and helps when the same item must be identified the same way at every branch. Multi-branch and multi-warehouse stock depends on the plan you choose.
For branches in different towns, the online version gives access to every branch from anywhere, with automatic updates and managed backups. A single counter with weak internet may be better served by the desktop version on a local network. Businesses in and around Ranchi are welcome to visit our office to talk through their locations before setup; we also work with clients elsewhere in India.
You may not need this yet if you have one shop and a storeroom behind it run by the same person; a simple billing app with stock may be enough. If your stock headaches are mainly about sizes and colours, our garments and footwear shop software is designed around variants. And if you are still deciding whether you need an ERP at all, read distribution ERP versus a simple POS first.
Questions people ask
Should each branch keep its own item list?
No. Use one item master with one code, name and barcode per item for the whole business, and keep only the quantities separate by location. Separate item lists make transfers and branch comparisons unreliable.
Where does stock show while it is on the way between branches?
It should sit in an in-transit stage: removed from the sending location's saleable stock but not yet added to the receiver's. It becomes saleable at the receiving branch only when that branch counts and confirms it.
How often should each branch count its stock?
Weekly cycle counts of a rotating group of items, plus occasional surprise counts of high-value goods, catch problems faster than one big annual count. Keep the full count for year end or when you change software.
Do we need an e-way bill to send goods from our godown to our own shop?
It can be required even when no sale takes place, depending on the value of the goods and the rules in force. Check the current rules on the e-way bill portal and confirm your case with your CA.
