An exception is either something that happened and shouldn’t have, such as a confirmed quantity lower than ordered, or something that should have happened and didn’t, such as a PO acknowledgment (EDI 855) that never arrived or an ASN (EDI 856) missing on the day of delivery. Supply chain exception management is the discipline of catching these early and getting them fixed.
It helps to separate two kinds of exceptions. Technical exceptions are failed or rejected messages, often flagged by a functional acknowledgment (EDI 997). Business exceptions are documents that processed correctly but describe a problem: a short shipment, a changed date, an invoice price that doesn’t match the order. Integration monitoring catches the first kind; the second needs the context of the order lifecycle.
A good process runs in a loop:
- Detect: compare what happened with what should have happened
- Prioritize: by customer impact, value and age
- Resolve: assign an owner and involve the trading partner
- Improve: find root causes and track them on a supplier scorecard