Inventory Management Software in Nepal: Making Stock Match the Shelf

Every business that holds stock eventually discovers the same thing: the number in the system and the number on the shelf are different, nobody knows when they diverged, and the only available response is to count everything and start again.

That cycle repeats because the underlying cause is never addressed. Stock does not drift because counting is hard. It drifts because things happen to stock that the system never hears about.

Every movement must be a transaction

The rule is simple and almost never fully implemented: if the physical quantity changed, a record changed. No exceptions.

The complete list of movements in most businesses:

• Purchase receipt from a supplier
• Sale to a customer
• Return from a customer
• Return to a supplier
• Transfer between locations or branches
• Consumption in production
• Output from production
• Damage or breakage
• Expiry or obsolescence
• Internal use — samples, staff consumption, marketing
• Physical count adjustment

The four that routinely happen without a record are damage, expiry, internal use and transfers done informally between branches. Those four account for most unexplained variance in most businesses. Adding a fast, low-friction way to record them — a single screen, a reason code, done in ten seconds — closes more of the gap than any amount of counting.

Adjustments need reasons, and reasons need review

An adjustment without a reason code is a hole in the ledger. Every physical count adjustment should record what the system said, what was counted, the difference, and why — and “unknown” should be an available and tracked reason rather than something people avoid by picking something plausible.

The value is in the pattern. One item with unexplained shortfall every month is a different problem from broad small variances across a category. The first is theft or a systematic process error at a specific point; the second is usually a unit-of-measure or counting-practice issue.

Units of measure cause more errors than anything else

A supplier sells a carton of 24. The shelf sells singles. The recipe consumes grams. The purchase invoice is in kilograms.

If the system holds only one unit per item, someone is doing conversions in their head at every transaction, and eventually a carton gets received as a single unit or a kilogram gets issued as a gram. Both are silent and both destroy the count.

The system should hold a base unit and defined conversions, and every transaction should record the quantity in the unit actually used — with the conversion applied by the software. Purchase in cartons, sell in pieces, and let the system reconcile.

Valuation method, chosen once

Stock has a value, and how that value is computed affects the accounts. Weighted average is the most common choice in Nepal and the easiest to explain; FIFO is required or preferred in some contexts and is more accurate where costs move sharply.

What matters is that the method is explicit, applied consistently, and that the system can show its working — the movements and costs that produced the current valuation. A closing stock figure that cannot be traced back to transactions is a figure your auditor will have to test the hard way.

Reorder points that reflect reality

Most reorder levels are set once and never revisited, which makes them either a source of stockouts or a source of dead capital.

A useful reorder point is derived: average consumption over a recent period, multiplied by supplier lead time, plus a safety buffer sized to how variable both of those are. All three inputs are in the system already if transactions are being recorded.

Lead time is the one worth tracking explicitly. The gap between a purchase order being placed and stock being received, per supplier, is data you accumulate for free and it is usually longer and more variable than anyone assumes — particularly for imported goods.

Multi-location without ambiguity

The moment there is more than one godown, shop or branch, stock is per location and every movement between them is a transfer with a dispatch and a receipt.

The in-transit state is what most systems miss. Stock that has left location A and not yet arrived at location B belongs to neither. If the transfer is recorded as a single instantaneous event, then anything lost or damaged in between disappears without a trace, and any discrepancy at receipt becomes an argument with no evidence.

Dispatch reduces A and increases in-transit. Receipt reduces in-transit and increases B. Any difference is visible, attributable and dated.

Batch, expiry and serial — only where you need them

Batch and expiry tracking is essential for pharmaceuticals, food, cosmetics and chemicals, and it is significant overhead everywhere else. Serial number tracking matters for electronics and anything under warranty.

Apply them per item category, not globally. A system that forces batch entry on every item will be defeated by staff entering the same dummy batch every time, which is worse than not tracking at all.

Where they apply, the payoff is concrete: near-expiry reports while there is still time to act, correct batch selection at sale, recall traceability, and warranty lookups by serial.

Cycle counts, not annual stocktakes

An annual count of everything is disruptive, error-prone because it is rushed, and surfaces problems up to twelve months after they happened.

Counting a section each week, on a rotation, with variance investigated while the transactions are recent, keeps the numbers honest year-round and makes the annual figure a confirmation rather than a discovery. High-value and fast-moving items get counted more often; slow-moving low-value items less.

The reports worth watching

• Stock value on hand, by location and category, and how it has moved
• Items below reorder level, with lead time
• Ageing — how long stock has been sitting, which is where cash is trapped
• Non-moving items, the category everyone underestimates
• Variance by item and by reason, over time
• Near-expiry, where applicable

Ageing and non-moving are the two that change purchasing behaviour. Most businesses carrying too much stock are not carrying too much of everything — they are carrying far too much of a specific slow tail nobody looks at.

Where it connects

Inventory is not a standalone concern. Purchases create payables, sales consume stock and create cost of goods sold, production converts one into another, and closing stock is a balance sheet line. Run separately from accounting, the two will disagree and reconciling them becomes a monthly job.

We build accounting and inventory software for businesses in Nepal, with multi-location stock, batch and expiry control, and inventory that posts straight to the ledger. If your stock report and your shelves disagree, talk to us.