Branch stock visibility is what a distributor has when he can answer, from wherever he is standing, how much of an item is lying at each of his locations. Most distributors with branches do not have it, and the reason is rarely that the data is missing. It sits in Tally, correct, on a desktop in one office, while the questions arrive at counters and warehouses in other towns. So the answer travels by phone call, arrives late, and gets rounded on the way. The cost shows up as orders promised against stock that is not there, transfers made because nobody checked the other branch first, and a physical count each year that nobody can reconcile. This article looks at where branch stock visibility actually breaks for an Indian distributor, what it costs in ordinary trading, and what changes when the answer lives on a phone.
Key Highlights
- The data is usually correct and simply unreachable, because the report opens only where Tally is installed
- Outward documents recorded without a location are the largest single cause of branch figures drifting from the shelf
- Visibility is worth having only if the person who needs the answer can get it without asking anybody
In This Article
- The 9 PM question
- Where branch visibility actually breaks
- What poor visibility costs in a normal month
- The three people who need the answer
- What good branch visibility looks like
- Money moves too, and it moves late
The 9 PM Question
The shop is shut and the owner is on his sofa with his phone. Somebody called at four o'clock wanting thirty cartons by Thursday, and he said yes because he thought the Jorhat branch was carrying enough.
Now he wants to check. Tally is on the desktop at the main office, so the options are to call the branch manager who has finished for the day, to guess, or to wait until morning and find out that he has promised stock that was dispatched last week. Every distributor with branches recognises this evening. It is not a technology problem in the sense of missing data. It is a question that arrives at a place where the answer is not.
The plumbing behind the answer is described in managing multiple branches in Tally with godowns.
Where Branch Visibility Actually Breaks
Across enough distributor books, the failure clusters into four places, and only one of them is about software.
The report is where the software is. Tally's godown-wise view works well and opens on one machine. Everybody who needs it during the day is somewhere else.
Outward documents carry no location. Transfers get recorded carefully because a truck is standing there. Invoices get recorded fast because a customer is waiting. Since sales move far more stock than transfers do, a blank location on invoices quietly drains the wrong godown, covered in godown on sales invoices and delivery challans.
Goods in transit belong nowhere. Stock loaded on Monday and received Thursday is missing from both ends unless a transit location exists to hold it, and the gap gets reported as a discrepancy by whoever notices first.
Entries wait for the desktop. A transfer recorded three days after the goods moved leaves both locations wrong for three days, every time.
What Poor Visibility Costs in a Normal Month
The cost is easy to miss because it never appears as a line in the books. It appears as ordinary friction.
| What happens | What it costs |
|---|---|
| Order promised against stock that is not at the branch | A delayed delivery and a retailer who tries the next distributor |
| Transfer raised without checking the other location | Freight on goods that were already where they needed to be |
| "Let me check and call you back" at a counter | The order, sometimes |
| Annual physical count that does not reconcile | Days of reconstruction and an adjustment nobody trusts |
None of these are catastrophes. They are a small tax on every week, and in a business running on distribution margins, a small tax on every week is the difference between a branch being worth having and being a headache the owner tolerates.
The Three People Who Need the Answer
Branch stock visibility is often built for the owner and then used by nobody else. The three roles that actually need it want different things.
The owner wants the spread. Which location is holding what, where the slow stock has piled up, and whether a branch is sitting on goods that should be selling somewhere else.
The salesman wants one item. He is standing at a counter with a retailer asking about a specific SKU, and he needs to know whether it can ship today and from where. An item drill-down across locations answers him; a company-wide list does not, covered in the godown-wise stock report on mobile.
The storekeeper wants his own location, and he needs to record movement rather than only read it. He also should not be able to move stock out of somebody else's warehouse, which is what warehouse-scoped staff access is for.
Build for only the first of these and the other two keep phoning each other, which is where you started.
What Good Branch Visibility Looks Like
Four things have to be true together, and missing any one of them puts you back on the phone call.
The position is readable wherever the question arrives, which means a phone rather than a desktop. The position is current, which means entries are made when goods move rather than when somebody reaches a machine. The position is complete, which means outward documents carry locations and transit has a home. And the person asking can get the answer without asking a colleague, which is a permissions question as much as a reporting one.
Takkada reads the godowns already defined in your Tally and puts location-wise stock on the phone, with item drill-down and a view as of a past date, while transfers, challans and location-stamped invoices are recorded from the same phone and written back into Tally. Tally stays the book of record. What changes is who can see the position and when the entry gets made.
One caveat to carry into any conversation with a backdated screen: quantities for a past date are historical and exact, while the value beside them is computed at the item's current rate. Quantity is the answer branch questions usually need.
Money Moves Too, and It Moves Late
Stock is half of what a second location costs an owner in attention. The other half is collections.
A retailer pays the branch, somebody writes it in a notebook, and the receipt reaches the books when the branch accountant next opens Tally. Meanwhile the owner is looking at outstanding figures that are days out of date, and the reminder that goes out to a retailer who has already paid costs him more goodwill than the delay cost him money.
Takkada puts a UPI payment link on the invoice, so the retailer pays from wherever he is and the receipt reconciles back into Tally against the right bill. Collection carries 0% MDR on UPI, with no transaction cap and no monthly fee, which matters across a branch network taking many small payments. Between stock that is visible and money that does not wait, the branch stops being a place the owner has to remember and becomes a place he can see.
Takkada is a Tally-integrated receivables and auto-reconciliation app for Indian distributors, with 0% MDR UPI collection and WhatsApp dispatch.
Frequently Asked Questions
Q: What is branch stock visibility for a distributor?
A: The ability to see how much of each item is lying at each of your locations, from wherever the question comes up. In Tally the underlying data is godown-wise stock. Visibility is about reach rather than data: the owner at a branch, the salesman at a counter and the storekeeper at a warehouse all need the answer in places where the desktop is not.
Q: Why does branch stock in Tally not match the physical stock?
A: Usually because outward documents were recorded without a location, since sales move far more stock than transfers do. The other common causes are goods in transit with no transit godown to hold them, entries made days after the goods moved, and opening stock entered as one lump instead of location-wise.
Q: Can I see branch stock without giving staff access to everything?
A: Yes. A team member can be restricted to named godowns, which covers godown stock reports, stock journals and delivery challans, and out-of-scope entries are refused on the server. Be precise about the boundary when you plan roles, because this scope governs stock movement and stock visibility rather than who can see which sales documents.
Q: How current is the stock figure on a phone?
A: It is as current as the entries behind it, which is the real point. An app that only displays data leaves entry on the desktop, so the phone is as stale as the backlog. When transfers and challans are recorded from the phone at the moment goods move, the position stops waiting for anybody to reach a machine.
Q: Is a separate inventory system needed for multiple branches?
A: Usually not, when the branches sit under one legal entity and one GSTIN. Tally already holds locations as godowns, and a second system creates a parallel set of numbers to reconcile every month. The gap to close is access and entry timing, not the data model. What to check before buying anything is in the multi-location buyer's checklist.
Q: What does poor branch visibility actually cost?
A: It does not appear as a line in the books. It appears as orders promised against stock that is not there, freight on transfers that were not needed, orders lost at the counter to a check-and-call-back, and an annual count that takes days to reconcile. Small amounts weekly, on distribution margins, across every location.
Takkada is a Tally-integrated receivables and auto-reconciliation app for Indian distributors, with 0% MDR UPI collection and WhatsApp dispatch. Book a free demo.