It is the single most common complaint we hear, in almost identical words: “the system says one thing, the godown says another, so we do a physical count and use that.”
Once that happens, the system has quietly stopped being the source of truth. Everything downstream — valuation, costing, re-ordering, the owner’s idea of what the business is worth — is running on a number nobody believes.
In our experience the cause is almost never the software. It is one of seven things, and you can usually find which one in an afternoon.
1. Goods move before the paperwork does
Material physically leaves the store on Monday evening. The issue slip is entered on Wednesday. For two days the system is wrong — and if the count happens on Tuesday, it looks like a discrepancy that will be investigated for hours.
Fix: entry at the point of movement, not at the end of the week. On a shop floor that usually means a simple screen or a phone, not a full workstation. The goal is not perfect data entry; it is closing the gap between the event and the record.
2. Units of measure are inconsistent
Purchased in bags, issued in kilograms, counted in cartons. Somewhere a conversion factor is wrong, or worse, applied twice. This is the single most common cause we find, and it hides well because it only affects some items.
Fix: one base unit per item, defined once on the master, with conversions applied at entry rather than living in someone’s head. Then audit every item where the conversion factor is not 1.
3. Returns and rejections are not recorded
Material goes out, some comes back — short, rejected, over-issued, wrong shade. If there is no return entry, that quantity is gone from the system forever while it sits physically on a rack.
Fix: make the return entry as easy as the issue entry. If it takes more clicks to return material than to issue it, it will not get done.
4. Wastage and process loss are not accounted for
In any manufacturing process, 100 kg in does not give 100 kg out. If the system does not have a place for that loss, it accumulates as a permanent, growing discrepancy that everyone eventually stops trying to explain.
Fix: an explicit wastage entry, with an expected percentage per process. It also turns an accounting annoyance into a management report: which process, which machine, which shift is losing more than it should.
5. Nobody owns a location
Main store, floor store, a rack behind the office, and material with a job worker outside. If the system knows one location and the reality has four, the total will never agree.
Fix: every physical place where material rests is a location in the system, including material sent out for processing. Job-work stock is the one most often forgotten, and often the largest.
6. Backdated entries change history
Someone enters a March transaction in May. The current balance corrects itself, but every report anyone printed in April was wrong, and the March closing you reported to the owner no longer matches what the system says today.
Fix: period closing. Once a month is closed, it is closed — corrections go into the current period as adjustments, with a reason. Painful for a week, and then it eliminates an entire category of argument.
7. Two systems, one truth
The system says one thing and the storekeeper’s register says another, so people trust the register. Now every count is a reconciliation between two records that were never designed to agree.
Fix: retire the register — but only after the system is genuinely faster to use than the register. If entry is slow, the register comes back, and no policy will stop it.
How to find which one is yours
- Pick five items with the largest discrepancy, not a random five.
- Print the full ledger for each: every receipt, issue, return and adjustment for the last three months.
- Walk it backwards with the storekeeper until the system balance and the physical balance agree on some past date.
- The transaction right after that date is your problem. Nine times out of ten, all five items point at the same cause.
This takes an afternoon and it beats any amount of speculation in a meeting.
What actually makes it stick
- Cycle counting instead of an annual count. Count a small set of items every week, correct immediately with an audited adjustment. Errors get caught days after they happen, when someone still remembers.
- Every adjustment needs a reason and a name. Not to blame anyone — so that the pattern is visible. Adjustments clustering on one item, one shift or one location tell you where the process is broken.
- Make the correct action the easy action. This is the whole game. Any process that depends on someone doing extra work at the end of a long shift will fail, and it is not their fault.
A stock system does not fail because the arithmetic is wrong. It fails because the entry is slower than the material.
Stuck at this? Send us one item’s ledger and a photo of the rack. We will usually tell you which of the seven it is without charging you anything. See our inventory system or get in touch.