A kirana store, a pharma distributor with three godowns and a small fabrication unit have the same stock problem in different sizes: they do not know exactly what they have, where it is, or when to reorder. This article explains what an inventory management system does for a business like that, what Indian realities it must handle (barcodes, GST, UPI), and how to choose one.
What an inventory system actually does
At its core it keeps one ledger of every item: what came in, what went out, what is left, and where. Everything else is built on that ledger.
- Stock on hand by location in real time, not at month end.
- Reorder alerts when an item falls below a level you set (or a level the system calculates).
- Batch and expiry tracking for pharma, food, agrochemicals and cosmetics.
- Purchase and sales linkage so a bill automatically reduces stock and a goods receipt increases it.
- Stock transfers between shop, godown and branch, with a paper trail.
- Reports on fast and slow movers, dead stock, stock ageing, and valuation for the CA.
If a system does not tie stock to billing, it is a register, not a system. You will end up updating it by hand and it will drift from reality within a month.
What this means in practice differs by trade. For a kirana or general store, the payoff is knowing what to order from the wholesaler before the shelf is empty, and catching the slow movers that quietly tie up cash. For a distributor, it is knowing what is in each godown and in each van, and what each retailer owes. For a small manufacturer, it is raw material on hand against the orders in the book, so the purchase call is made a week early rather than a day late.
Indian realities the system must handle
Barcodes that are missing, wrong or shared
Branded FMCG carries an EAN barcode; loose grain, hardware, cut fabric and most locally manufactured goods do not. A workable system lets you print your own labels for those, and handles the case where one barcode covers several pack sizes. A USB barcode scanner and a thermal label printer are usually enough; as a rough guide, budget ₹5,000 to ₹15,000 for both.
GST, HSN and the tax stack
Every item needs an HSN code and a tax rate, and the system must produce GST-compliant invoices, handle inclusive and exclusive pricing, and export data for GSTR-1 without re-entry. If you cross the e-invoicing threshold, it must generate IRNs. If you move goods between godowns in different states, stock transfers become taxable events. Ask specifically about each.
UPI and mixed payments
Retail collections are now mostly UPI. The system should record a sale as paid by UPI, cash, card or credit, and ideally reconcile UPI settlements against the bank. Distributors also need credit limits and outstanding tracking per customer, because most B2B sales in India are on credit.
Low-end phones, patchy networks
The person doing the stock count in the godown is on an Android phone that cost ₹8,000, with one bar of signal. A stock-count screen that needs a steady connection will be abandoned. Look for offline entry with later sync, or at least a lightweight mobile web app.
Units and conversions
Buy in bags of 50 kg, sell in kg and grams. Buy cartons, sell pieces. Buy metres, sell cut lengths. Unit conversion sounds trivial and breaks more implementations than anything else we see.
Multi-location stock
The moment you have a second shop or a godown separate from the counter, three things go wrong: stock is sold from a location that does not have it, transfers happen without a record, and nobody knows the true total.
A multi-location setup needs each location to be a separate stock ledger, transfers to be two-step (dispatched, then received), and reports to show both per-location and consolidated views. Transfer-in-transit should be visible; goods on a tempo between Nagpur and Gondia are neither here nor there, and the system should say so.
For distributors with van sales, the van itself is a location. Stock is loaded in the morning, sold from the van, and reconciled in the evening.
Two features are worth asking about specifically. The first is reservation: when a customer places an order that will be dispatched tomorrow, that stock should be shown as committed so the counter does not sell it today. The second is a permission model, so a branch manager can see and transfer their own stock but not silently adjust the godown's figures. Both are easy to skip in a demo and painful to live without.
Integration with billing and accounts
The single most common failure is running inventory in one system and billing in another, and hoping someone keeps them aligned. Nobody does.
Three workable patterns:
| Pattern | How it works | Suits |
|---|---|---|
| One suite | Billing and inventory in the same product, one database | Most shops, small distributors, small manufacturers |
| Inventory system posts to accounts | Stock and invoices live in the inventory system; a daily export or API sync posts vouchers to Tally or the accounting package | Businesses whose CA insists on Tally |
| Accounting system is master | Tally or similar does billing; inventory only reads from it | Very simple stock, single location |
The first pattern is the simplest to keep honest. The second is the most common compromise in Maharashtra because CAs work in Tally. The third rarely survives growth.
For manufacturers, add a bill of materials: a production entry consumes raw material stock and creates finished goods stock. Without this, raw material figures are fiction.
Off-the-shelf, suite or custom
- Off-the-shelf inventory apps (there are many, from free to a few thousand rupees a month) suit a single shop with standard needs. They are quick to start and hard to bend.
- Suites that bundle billing, inventory and reports on one platform suit most small and mid-size businesses. Our own StockRight module in RightSutra is one option in this category, sitting alongside BillRight for point of sale.
- Custom systems make sense when your process is genuinely unusual: complex batch genealogy, made-to-order manufacturing, or integrations with machines and weighbridges. The indicative cost for a custom inventory and billing system in India is roughly ₹2 to ₹8 lakh depending on locations, users and integrations; the real figure depends on scope. See our ERP for small manufacturers guide and the POS and billing software post for related costs.
Whichever you choose, ask who owns the data and how you get it out. A system you cannot export from is a system you cannot leave.
Getting the go-live right
- Do a physical count first. Opening stock in the new system must be real. A count on a Sunday with the shutters down is the usual way.
- Clean the item master. One item, one code, one unit, one HSN. Merge duplicates before import, not after.
- Set reorder levels for the fastest-moving 20 percent of items only. The rest can wait; they are slow anyway.
- Run billing through the system from day one. Parallel manual bills are how stock drifts.
- Cycle count weekly. Count a few racks every week instead of everything once a year. Mismatches get caught while they are still explainable.
- Train the person at the counter, not just the owner. They are the ones who will create a new item called "misc" if the search is slow.
After go-live, three reports are worth reading every week: negative stock (always a data-entry error, and a sign of where training is needed), items with no movement in 90 days, and the difference between system stock and the latest cycle count. If those three stay small, the system is telling the truth and every other report can be trusted.
Where SailRight fits
We build inventory and billing systems for shops, distributors and small manufacturers, both as custom projects and through the StockRight and BillRight modules of RightSutra. Our custom software development service covers integrations with Tally, barcode hardware and multi-location setups. If you want to see how your stock process would map onto a system, contact us.
- Inventory management
- Stock control
- Retail
- Distributors
- GST billing
- StockRight