Imagine a small trading company where the stock sheet says there are 120 units of a product, and the shelf has 97. Someone asks what happened. Nobody knows. The sheet shows 120 because somebody typed 120 at some point, and there is no way to tell when, who, or what that number replaced.
This is the quiet weakness in many stock systems. They store how many you have right now, and nothing about how you got there. When the number is wrong, there is nothing to investigate. All you can do is count again and type a new number over the old one, which erases the last clue you had.
The problem with a number you can overwrite
A single quantity field behaves like a whiteboard. Anyone with access can wipe it and write something else, and the board keeps no memory of what it said before.
That causes three practical problems:
- No explanation. A difference between the system and the shelf can come from a miscount, a missed delivery, a return that was never booked, a transfer between locations, a breakage, or a theft. With only the final number, all of those look the same.
- No accountability. If nobody can see who changed a figure, honest mistakes repeat and dishonest changes are easy to hide. Many discrepancies are honest, but a system that can't tell the difference makes everybody a suspect.
- No trust. When the team learns that the number can't be relied on, they stop using it. They walk to the shelf and look. At that point the system is a decoration.
The alternative: record movements, derive the balance
The sturdier design turns the idea around. Instead of storing the quantity and editing it, the system stores every movement as its own record: received 50, sold 3, returned 1, moved 10 to the second warehouse, counted and adjusted by minus 2. The current quantity is not typed anywhere. It is calculated by adding up the movements.
This is the same principle behind a bank statement. Your balance is not a number someone edits; it is the result of every deposit and withdrawal. If the balance looks wrong, you read the lines.
Each movement record carries the same few facts:
- What moved, and how many.
- When it happened.
- Who did it, tied to a personal login and not a shared one.
- Why: a sale, a purchase receipt, a return, a transfer, a damage write-off, a count correction. Ideally linked to the document that caused it, such as the order or the delivery note.
Security standards use the term audit trail for roughly this idea. NIST's glossary defines it as a chronological record that reconstructs and examines the sequence of activities surrounding or leading to a specific operation. A stock ledger is that, applied to your goods.
Corrections are new entries, never edits
Mistakes will happen. The rule that keeps the ledger trustworthy is that a record, once saved, is not changed or deleted. If a movement was wrong, you add another movement that reverses it, with a reason.
So if someone books 30 units received instead of 3, the fix is a correction entry of minus 27 with a note, not a quiet edit of the original line. Both entries stay visible. The history shows the error, who caught it, and when. That is slightly more work than overwriting, and it is exactly the point.
What this gives you in practice
- Investigating a discrepancy becomes reading, not guessing. You open the product, see every movement, and spot the delivery that was entered twice or the transfer that was only booked on one side.
- Questions get answers. "What did we sell last quarter?" "When did we last receive this?" "Who adjusted this item?" All come from the same records.
- Counts become gentler. A physical count is just another movement: the difference between expected and counted, with a reason. Large or repeated adjustments on the same item can be flagged for review.
- Different people can see different things. The warehouse team can book movements; only a manager can approve a large adjustment.
- The team trusts the number. This one matters most. A figure you can trace is a figure people use.
What it doesn't do
A ledger does not stop a mistake from being made. If someone scans the wrong product, the record is accurate about a wrong action. What it changes is that the error leaves a trail, so it can often be found and corrected quickly instead of being discovered at year end. It also depends on people booking movements at all; a barcode scanner or a simple mobile screen makes it quick enough that people are more likely to do it.
A first step
Pick one product that regularly shows a difference and ask: if the system says 120 and the shelf says 97, can we find out why from what the system holds today? If the answer is no, you have your first requirement. Write down what you would want to see on the screen to answer it: date, person, reason, document. That short list is most of the design.