Almost no company says it keeps inventory by hand. It has a system, it has codes, it has a warehouse keeper. And yet, when the physical count comes, the differences appear and nobody can explain them. The cause is almost never the count: it is that the system records what somebody remembers to type, not what happens.
These five signs show up in most of the operations we visit before implementing XEN. Each one has a fix that does not require buying anything: it requires changing who moves the data.
1. The spreadsheet that knows more than the system
There is a file, usually on the warehouse manager's desktop, that holds the true stock. The system holds another. When the two differ, the file wins, and the system is corrected to match. That means the system is not the source: it is a stale copy.
What to do: stop correcting at the destination. Every difference is recorded as an adjustment with its reason (shrinkage, receiving error, theft, return), and the spreadsheet becomes analysis, not a record. In XEN the adjustment is one more movement in the stock ledger, and it leaves a trace of who made it and why.
2. Selling what is not there
A salesperson closes an order, promises delivery for Thursday, and on Thursday the warehouse discovers those units were already committed to another customer. The data existed; nobody looked at it in time, because available stock did not subtract pending orders.
What to do: separate physical stock from available stock. Physical is what sits on the shelf; available is physical minus what is committed. An order must reserve at the moment it is created, not when it ships. XEN shows the two figures separately, and the order reserves on its own.
3. Purchasing when it runs out
The purchase order goes out when somebody notices the shelf is empty. That somebody is usually the customer. The minimum stock lives in the warehouse keeper's head and not in the system, so it depends on that person being on shift that day and paying attention.
What to do: write the minimum per item and per warehouse, and let the system watch it. With the minimum loaded, XEN's logistics agent detects the stockout before it happens and proposes a replenishment to the purchasing agent with the quantity and the usual supplier. A person approves or corrects; the watching is no longer theirs.
4. One product with three names
Bolt 3/8, bolt 3-8 and BOLT 3/8 are one item for the warehouse and three items for the system. Stock appears split, turnover reports lie and counts never reconcile because nobody knows which of the three to count against.
What to do: one unique code per item, decided before the first purchase, and a clear rule for presentations: two presentations are two units of measure of the same item, not two items. Cleaning the catalog is boring, and it is the work with the highest return per hour invested.
5. The movement is recorded the next day
The goods left at ten in the morning and were typed in at five in the afternoon, or the next day, or never. Between one hour and the other the system lied, and any decision taken with that data (a price, an order, a delivery promise) was taken blind.
What to do: make the record the same act as the movement. An issued sale deducts; a purchase receipt adds; a transfer leaves one warehouse and enters another in the same gesture. When inventory is a consequence of the operation and not a separate task, the delay disappears because there is nothing left to delay.
What the five have in common
In all of them, a person is the bridge between what happened and what the system says. And a person, however good, gets sick, gets distracted and changes jobs. The underlying fix is the same in all five cases: remove the bridge. Let the order reserve, the sale deduct, the minimum warn, the adjustment explain. That is exactly what a system that executes does instead of one that records.
To see how an inventory is started with these rules from the very first movement, the getting started guide walks through it step by step. Read the guide to getting inventory running
