Playbook: building what nobody ordered
The situation
Monday, 8:00. The SMT line is booked for MO-2026-0001: 30 SmartSensor S100. The order was planned weeks ago. Since then, stock has grown to 78 free units, open customer orders need 4 and the reorder point is 20. Nobody cancelled the order, because nobody put those numbers next to each other.
The screenshots come from the Otiox demo workspace. To follow along, choose Switch to demo in the sidebar — changes there never touch your live data.
Step 1 — See orders nothing calls for
Go to Inventory → Stock Integrity. Findings titled MO beyond known demand are planned orders whose output no known demand needs.
In the demo there are four.
Step 2 — Open the finding
Open the one for MO-2026-0001.
The numbers are side by side: the order would make 30; free stock (78) and other open orders already cover open sales (4), the reorder point (20) and sub-assembly needs (0). What to do: cancel or reduce the order.
Step 3 — Reduce the quantity
Choose Open the order and reduce its quantity. The order opens with the quantity dialog ready.
Component quantities scale by the same ratio. In the demo we cut the order to 10 and choose Save. If nothing at all calls for the order, cancel it instead.
Step 4 — Check the order
The order now reads SmartSensor S100 × 10 and stays scheduled. On the next scan the finding re-evaluates the order against demand and closes once nothing is left beyond it.
Run the check before every planning meeting. An order that has lost its reason is easy to stop before the line starts — and expensive to undo afterwards.
What you have at the end
- Every planned order checked against all known demand.
- The covering stock and sales, in numbers.
- Orders cut before materials and machine time go into them.
Related
- Use case: Overproduction — /use-cases/overproduction
- Use case: Stuck Orders — /use-cases/stuck-orders