Playbooks/ Last updated: 2026-09-29

Playbook: a supplier slips a week — what breaks?

The situation

A purchase order for precision PCBs is twenty-four days late. Purchasing knows. What they cannot see is that a manufacturing order is waiting for those boards and a customer order is waiting for that build.

Step 1 — See the chain on the purchase order

Open the purchase order and choose the Impact tab.

Impact: late now, late only if it slips, customer orders affected

Otiox follows the links the records already hold — PO line → bill of materials → manufacturing order → customer order — and splits the result: late now, late only if it slips another N days, and customer orders affected. Move the slider to see what a further week does.

Step 2 — Simulate before it happens

Open Command → What-if scenarios, choose A supplier is late, pick the supplier and the days.

What-if: the supplier a week late — which orders turn late

The simulation moves every open purchase order from that supplier, lets production wait for the material, lets slack absorb part of it, and lists the orders that end up late. Nothing is changed; save the scenario to keep its result.

Why it matters

The delay is not the problem; the *dependencies* are. Because Otiox models how purchase orders, builds and customer orders depend on each other, one late delivery becomes a list of named customers — days before anyone calls.

What you have at the end

The full chain from a late supplier to the affected customers.
What a further slip would add.
A simulation you can run before committing to a plan.

Screenshots come from the Otiox demo workspace. Choose Switch to demo in the sidebar to follow along; changes there never touch live data. Command reads your records and never changes them.