After enough conversations with companies moving off spreadsheets, the same five mistakes keep showing up. None of them are exotic. All of them are expensive. Here they are, with the fixes, none of which involve heroics.
1. Tracking quantities instead of items
A count that says “37” cannot tell you which three are damaged, which lot expires next month, or which unit the customer returned. Quantity-only tracking works right up until the first discrepancy, then it fails completely, because it has no memory.
The fix is unit-level tracking: every physical item is its own record with a barcode. In Knowledge ERP that is the default, and category-level tracking flags let you keep cheap consumables simple while the expensive stock gets the full treatment.
2. Reordering from memory
The person who “just knows” when to reorder is a single point of failure with vacation days. Stockouts follow them out the door, and so does the over-ordering they do to avoid being blamed for stockouts.
The fix is reorder points with suggestions. Knowledge ERP runs two comparable engines, one deterministic from usage and lead time, one forecasting on the server, and both feed a reorder queue with low-stock alerts. A digest email on your chosen mornings replaces the mental arithmetic.
3. Counting everything once a year
The annual wall-to-wall count produces a number that is wrong by February and a weekend nobody gets back. Worse, a yearly count means errors accumulate for months before anyone notices the pattern.
The fix is cycle counting: a bin or a category at a time, continuously, with per-line variance showing exactly where the record and the shelf disagree. Twenty minutes a week beats one lost weekend a year, and it catches the process problem while it is still small.
4. Letting locations blur
Stock “at the shop or maybe in the van” is stock you own but cannot use. Multi-location businesses that model only one location are blind to exactly the inventory that walks away most often.
The fix is making every place a real location, vans and job boxes included, with transfers between them instead of untracked grabs. In-transit visibility closes the gap where things used to vanish.
5. Keeping the audit trail in people's heads
When the count is off, the first question is “what happened?” If the answer lives in memory, you will get a story, not a fact. Stories do not reconcile.
The fix is a movement log the system writes for you: every receive, transfer, sale and adjustment with who, when, and before-and-after values. In Knowledge ERP, even API writes are attributed to the token that made them, and most changes can be undone from the record's history.
The theme, if there is one
Every fix above is the same move: stop depending on human memory for facts a system can record as a side effect of doing the work. Software does not make anyone more disciplined. It makes discipline unnecessary for the parts machines are better at.
If you want to see what your own numbers look like under this kind of tracking, the 30-day trial takes a CSV import, and the first cycle count will tell you things.