Supplier Delivery Exception Review

A supplier confirms delivery of one hundred units on Friday, but only eighty arrive on Monday and five are damaged. An exception review connects the promise, receipt and quality evidence so teams can decide what to do next.

SAP describes purchase-order item exceptions for late dates, low quantities, missing confirmations and overdue receipts, and its supplier complaint training describes documenting damaged goods. These are workflow examples, not automatic proof that the supplier caused every variance.

Define an exception as a late confirmation, changed delivery date, short quantity, damage or missing receipt, using separate codes. Preserve the baseline by recording both requested and supplier-confirmed terms and any approved changes, and use line-level detail, since a purchase order may have one late line and several on time.

Verify the actual event, because a carrier delivery scan, warehouse receipt and usable accepted stock are different milestones, and check receiving latency, as a shipment may arrive on time but not be posted promptly, so internal delay should be investigated before charging the supplier. Record quantity in matching units, converting cases and pieces consistently, and separate damage, since a full quantity delivered with unusable units is not full usable supply.

Set tolerances, because a minor timing difference may fall within contractual or operational tolerance, and document the rules before reporting results. Assign an owner, as procurement may coordinate with the supplier, receiving verifies goods and planning manages downstream demand, and assess impact, since a missing part on a critical build deserves faster action than surplus packaging material.

Communicate quickly by asking the supplier for an accurate recovery date and plan, and avoid sending accusations before checking facts. Create a recovery action such as expedited replacement, a substitute part or a revised production schedule, confirming cost and quality approvals, and link to customer commitments by notifying the right internal owner early.

Track open age, because a logged exception without a decision can sit for weeks, so give every case a next review date. Distinguish cause, since supplier capacity, carrier issue, receiving error and purchase-order mistake need different preventive measures, and check duplicates by grouping related alerts from one shipment while retaining each affected line.

Preserve evidence such as the PO version, confirmation, advance shipping notice, receiving record and photographs, review claims separately because a damaged-goods complaint or financial credit may follow but an exception ticket is not itself a settlement, and measure closure by defining whether the case closes at recovery plan approval, receipt of replacement or verified resolution. Analyse trends, since frequent short deliveries from one supplier or late receipts at one warehouse suggest different interventions, avoid hiding exceptions, because updating the promised date after the fact can make lateness disappear, and check data feeds, as an integration failure can create false missing-confirmation alerts.

Review supplier performance fairly by sharing case evidence, reviewing transport terms from the purchase order and shipping documents rather than the delivery address, and keeping a decision log of who approved a substitute, reschedule or expedited shipment; for owners, the review connects alerts to recovery and keeps supply planning honest when every exception has a verified state, impact and owner.