Independent IFS Cloud practice · Supply Chain
The cost of a missed check: a €200 part, a €40,000 stoppage
Key takeaways
- A purchase order that sits unconfirmed for eleven days can stop a production line for four hours — a €200 part behind a €40,000 loss.
- That ratio is not unusual: the cost of a missed check is rarely the material itself — it is the machine that went quiet and the delivery that slipped.
- The order state and the date were both correct the whole time — this is an attention problem, not a data problem.
- The fix is not more scrutiny per order — it is a systematic check that never skips one, however small it looks.
A purchase order sits in Released for eleven days. Nobody notices. The delivery date passes without anyone flagging it, and on day eleven the part still has not arrived. Production stops for four hours while a line waits on a component that costs a few hundred euros. The part itself is cheap. The line stoppage is not: four hours of idle labour, a missed shipment, a customer who now has a later delivery date than the one they were promised. The ratio between what the part cost and what the miss cost is not a freak outcome — it is close to routine, and it is exactly why exception management deserves more attention than it usually gets. This article covers why the ratio holds, what drives it, how to see the gap before it becomes a stoppage, and how to close it without turning every buyer into a full-time exception hunter.
1.Why does a small exception turn into a big loss?
Nothing about the eleven days was hidden. The order state was correct. The delivery date was correct. The information needed to catch the problem on day two, not day eleven, was sitting in IFS Cloud the entire time. What was missing was not data — it was someone looking at that specific field, on that specific order, before it mattered.
That is the trap with low-value exceptions. A buyer scanning a screen full of open orders naturally weights attention by value: the €80,000 order gets a second look, the €200 line does not. But the cost of the miss has nothing to do with the value of the part. It has to do with what that part unlocks downstream — a line, a shift, a shipment — and that downstream cost is invisible from the order screen.
2.What does the ratio actually look like?
The cost of a missed check is almost never the material. It shows up downstream, in four places that never get billed back to the exception that caused them:
- Idle production. A line waiting on one missing part burns labour and overhead hours that were already committed, regardless of the part’s value.
- Recovery cost. Catching up means expedited freight and rush fees on the missing part — and often on the parts around it, to resequence the line.
- Slipped delivery. Four hours of downtime rarely stays four hours by the time it reaches the customer’s dock — it compounds with whatever else was already queued behind it.
- Trust cost. A missed delivery date is a conversation with a customer that a €200 part should never have caused — and it is the conversation that gets remembered.
The most expensive exception in your supply chain is the one you had the data to prevent and still missed.
3.How do you catch it in IFS Cloud on day two, not day eleven?
IFS Cloud already has everything this needs: order state, confirmation status, promised delivery date, all attached to the order the moment it is raised. An order that stays in Released past a sensible age, with no confirmation and a delivery date approaching, is a pattern you can filter for today — the same underlying signal behind an unconfirmed purchase order, just viewed through the lens of downstream risk rather than supplier behaviour.
The gap is not visibility. It is that visibility, on its own, requires someone to look at the right filter on the right day. A €200 line does not earn that attention on a busy Tuesday, and that is precisely why it needs a rule that checks for it regardless of value, rather than a person who has to remember to.
4.Manual scanning versus systematic exception checking
The difference is not effort — a good buyer already works hard. The difference is what a rule catches that human attention, however diligent, structurally cannot.
| Manual | Systematic | |
|---|---|---|
| Weighted by | Order value, instinctively | Downstream risk, by rule |
| Small orders | Easy to skip | Checked the same as any other |
| Consistency | Varies by buyer, by day | The same rule, every time |
| Detection point | Whenever someone notices | The day the threshold is crossed |
| Worst case | Day eleven, at the line | Day two, at a desk |
A systematic check does not replace the buyer’s judgement — it removes the part of the job that depends on remembering to look at something that did not look urgent. That is exactly the gap between the €200 order and the €40,000 stoppage.
5.How do you roll it out safely?
Start narrow, let the data show you where the ratio bites hardest, and expand from evidence rather than a guess.
- Agree the trigger. Define the order state and age that count as a missed check for your operation — not by value, by risk to what it feeds.
- Run in dry-run. Log what would have fired over the last few months and compare it against known stoppages — the pattern usually confirms itself quickly.
- Tune the recipients. Route the alert to whoever can actually act on it that day, not just the buyer of record.
- Pilot on one line or one site. Prove the reduction in missed exceptions before widening coverage.
- Review the ratio after a month. Check what fired, what it prevented, and adjust the threshold on real evidence.
Built inside the IFS Extensibility Framework — standard Custom Events, Workflows and PL/SQL, no core modification — the check itself is update-safe, so it avoids the upgrade tax entirely while it keeps watching.
6.Frequently asked questions
Is the €200-versus-€40,000 ratio a one-off, or does it hold generally?
It is close to routine. Whenever a missing part can stop a line, the cost of the miss is set by what the line produces per hour, not by what the part cost — and that gap is usually large.
Why not just have buyers check low-value orders more carefully?
Because attention that is weighted by order value will always under-check low-value lines — it is a natural, reasonable instinct that happens to be exactly wrong for this specific risk.
Does this overlap with unconfirmed purchase order monitoring?
It shares the same underlying signal — order state and date — but the framing here is downstream cost, not supplier behaviour. The two checks complement each other rather than duplicate.
Is this update-safe?
Yes. The check is built with standard Custom Events, Workflows and PL/SQL inside the IFS Extensibility Framework — no core modification, nothing that the next R1/R2 release quietly breaks.
7.About the author
Dariusz Myśliwiec — 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally — you talk to the consultant who builds it, not a sales layer.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Close the gap before it reaches the line
If a €200 order has ever cost you a line stoppage, the fix is smaller than the incident. On a 30-minute call I’ll map a systematic check to your order states and thresholds — fixed price, dry-run before anything sends.
