Field note · Stock
Why stock records keep disagreeing.
When teams keep checking physical stock because the recorded number is not trusted, the problem is rarely solved by adding one more place to record it. The first task is to find where stock truth is created, changed and lost.
Stock truth is an event problem
Each event changes the number at a defined point, with an owner and an exception rule.
Elekevu practice note · Reviewed 28 September 2026
Repeated checking is a signal
A physical check can be a sensible control. It becomes a warning sign when routine work repeatedly stops because nobody trusts the system, sheet or message that is supposed to show the current position.
Teams often respond by keeping extra records for safety. That can make the problem worse because the business now has several plausible answers and no clear rule for which one wins when they disagree.
What this looks like in practice
A customer asks for an item. The sales record suggests it is available, but the person serving the customer checks the shelf or calls someone in the store because recent returns, damaged items or transfers may not be reflected yet. The physical check solves the immediate uncertainty, but the underlying record remains untrusted for the next transaction.
Over time, that behaviour becomes normal. People learn which number to distrust, who to ask, and which adjustment tends to be late. The system still exists, but operational truth has shifted into experience and workarounds.
Trace every event that changes the number
Purchases and sales are only part of the picture. Returns, damage, transfers, reservations, delayed updates and manual corrections can all create gaps between the physical item and the record.
- Which record is meant to be authoritative when two numbers disagree?
- At what exact point is stock increased or reduced?
- Who can make adjustments, and how are those changes explained?
- How are returns, damaged items, reservations and transfers handled?
- How much time can pass between the physical event and the recorded update?
What to observe before changing systems
Choose a small number of products and follow every event that changes their quantity for several days. The goal is to identify where the recorded state and physical state first diverge, not simply to count discrepancies at the end.
- Record each sale, return, transfer, reservation and adjustment for the sample items.
- Note the exact time the physical event happens and the time the record changes.
- Capture every manual correction and why it was needed.
- When two records disagree, note which one the team trusts and why.
When the problem deserves a deeper diagnosis
Repeated stock checks become more costly when they delay sales, cause avoidable stockouts, create customer promises that cannot be kept, or require senior people to resolve routine discrepancies. Growing product ranges and multiple locations can amplify a weak update rule quickly.
If the team cannot explain where the number changed or which record should win, adding dashboards or another inventory tool is unlikely to restore trust on its own.
A system cannot repair an undefined rule
Inventory software may be useful, but only after the business has a clear answer to what counts as available stock, when the record changes and who owns exceptions.
The smallest useful intervention may be a tighter update rule, fewer duplicate records, clearer adjustment controls, integration between existing tools, or a new system. The evidence should decide which.