A multi-location inventory app for Tally is judged on one thing: whether your location figures on the phone stay equal to your location figures in Tally after three months of real trading. Almost every option will show you stock by godown in a demo, because reading data and drawing a list is the easy part of the problem. The difficulty starts when the branch storekeeper needs to record a transfer, when an invoice has to leave from two locations at once, when a new godown is created mid-season, and when somebody asks what the position was on a date in the past. This article is a buyer's checklist rather than a product pitch. Eight questions, each with a reason it matters and a way to test it during a trial, so the decision is made on behaviour you have seen rather than on a screenshot.
Key Highlights
- Reading stock is the easy half; writing transfers, challans and location-stamped invoices back into Tally is where products differ
- A location report is only as good as the vouchers behind it, so ask how the app handles lines that carry no godown
- Test with a second branch and a real week of trading, because single-location demos hide every problem worth knowing about
In This Article
- Does it write back, or only read
- Can staff record movement, not just view it
- Is the location on the line or on the document
- What happens to lines with no godown
- Can you scope a person to a location
- Does the past-date view mean what you think
- What happens when you add a branch
- The collections question nobody asks
Does It Write Back, or Only Read
The first question separates most of the field. An app that reads your Tally can show location-wise stock. An app that writes back can record the transfer, the challan and the invoice at the moment the goods move.
The difference is not a feature comparison, it is a difference in what happens to your accuracy. A read-only app leaves entry on the desktop, so the phone shows a position that is as stale as the desktop backlog. The gap between the goods moving and the entry being made is exactly the gap where branch stock goes wrong.
Test it by recording a transfer on the phone during a trial and then opening Tally on the desktop. The voucher should be sitting there against your existing voucher type, looking like an entry your accountant would have made.
Can Staff Record Movement, Not Just View It
An owner-only app solves an owner's curiosity. A distributor's location accuracy is decided by storekeepers and dispatch staff.
Ask whether a warehouse person can raise a stock journal and a delivery challan from his phone, and whether he can do it without being given access to everything else in the business. If the answer is that only an admin can record movements, the entries will keep queueing behind whoever holds the admin login, and the timing problem stays exactly where it was. The mechanics of the transfer entry are in stock transfer between godowns from mobile.
Is the Location on the Line or on the Document
This sounds like a technical detail and it decides whether the app survives normal trading.
A retailer orders eight items, six sitting at the branch and two at the main warehouse. If the app puts one location on the whole document, somebody has to split the bill artificially or record a dispatch that did not happen. If the location sits on each line, the document describes what actually left each place.
Test it by raising one invoice with items from two locations during the trial. If you cannot, you will be doing it wrong every week for as long as you keep the product. The billing side is covered in godown on sales invoices and delivery challans.
What Happens to Lines with No Godown
Every existing company file has history recorded without locations. A good product tells you about it. A weak one silently pretends it does not exist.
Ask three things. Can the company require a location on stock-bearing lines going forward, so the gap stops growing. Does the app show you how many existing lines carry no location. And if you restrict someone to specific locations, does the product warn you that those blank lines will become invisible to him.
That third one is the honest test. A product that tells you what a setting will hide before you save it is a product that has met real books.
Can You Scope a Person to a Location
Warehouse-scoped access is worth having and worth understanding precisely, because a permission you believe in wrongly is worse than none.
| Ask | Why it matters |
|---|---|
| Is the restriction refused at the server or hidden in the app | Hiding a dropdown is a suggestion, not a control |
| Which documents does the scope cover | Stock movement and stock visibility are not the same as invoice visibility |
| Do new locations join a restricted person automatically | The safe answer is no, and it makes assignment a step when you open a branch |
| What happens with two godowns of the same name | Same name usually means same grant, which is a masters problem to fix |
Push the vendor for the boundary rather than the headline. Ours is stated plainly in restricting staff to their own warehouse, including what it does not cover.
Does the Past-Date View Mean What You Think
Most products can show a position as of a past date. Fewer will tell you how the value column was computed.
Historical quantity is a fact taken from vouchers. Historical value depends on which rate was applied, and applying today's rate to last month's quantity gives a figure that is useful for a sense of size and wrong for a valuation. Ask the question directly, and be suspicious of a vendor who has not thought about it. In Takkada the backdated quantity is historical and the value uses the item's current rate, which is stated on the report itself rather than left for you to discover.
What Happens When You Add a Branch
Businesses that buy a multi-location inventory app for Tally usually buy it because a second location just opened, which means a third is possible.
Check what opening a location actually takes. Can the godown master be created from the phone on the day the branch starts operating, or does it wait for somebody to reach the office desktop. Does the app hide location features entirely for single-location companies, so your smaller sister concern is not shown a screen it has no use for. Setting the master up is covered in creating and managing godowns in Tally from mobile.
The Collections Question Nobody Asks
Inventory is half of what a branch costs you. The other half is money sitting at a counter in another town waiting for somebody to record it.
A multi-branch distributor collects in more places than he can watch, and every location where cash is taken is a place where receipts reach the books late. Ask whether the app can put a payment link on the invoice so the retailer pays from wherever he is, and whether the receipt reconciles back into Tally against the right bill. Takkada does both, with 0% MDR on UPI collection, no transaction cap and no monthly fee, which is worth checking against whatever the branch is currently paying to accept digital money.
Judged together, that is the real test of a multi-location product for a distributor: it makes stock accurate at every location and it stops money waiting at any of them.
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 should I look for in a multi-location inventory app for Tally?
A: Writeback into Tally rather than read-only viewing, movement entry by warehouse staff and not just owners, line-level locations on invoices, a way to require locations going forward, location scoping for staff that is enforced on the server, and an honest explanation of how backdated values are computed. Test each during a trial with a real week of trading.
Q: Can a mobile app record stock transfers into Tally, or only display stock?
A: It depends entirely on the product. Display-only apps leave every entry on the desktop, so the phone shows a position as stale as the entry backlog. An app that writes back records the stock journal at the moment the goods move and puts it into Tally against your existing voucher type, which is where the accuracy gain actually comes from.
Q: Do I need a separate inventory system for multiple branches?
A: Usually not. If your branches trade under one legal entity and one GSTIN, Tally already models them as godowns, and what you need is access to that data where the goods and the staff are. A separate inventory system creates a second set of numbers to reconcile, which is a bigger problem than the one it solves.
Q: How do I test a multi-location app properly during a trial?
A: Use a second location and a real week. Record a transfer from the phone and check it in Tally, raise one invoice with items from two locations, restrict a staff member to one godown and try an out-of-scope entry, create a new godown and see whether the restricted member picks it up, and read a past-date position to see how the value is described.
Q: Should branch permissions be part of the decision?
A: Yes, but check the boundary rather than the label. Ask which documents the scope covers, whether it is enforced on the server or only hidden in the interface, and what happens to old lines recorded without a location. Warehouse scoping is a strong control for stock handling and is a different thing from partitioning who sees which sales.
Q: Does a multi-location app help with collections as well as stock?
A: It can, and for a branch network it should. Money collected at a counter in another town reaches the books whenever somebody records it. An invoice-level payment link that reconciles back into Tally removes that wait. Check the cost of accepting the payment too, since MDR on every collection is a running charge on a branch network.
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.