Delivery exception report

Purpose

Reconcile promised delivery performance against actual shipment and receipt events, then explain the exceptions that require operational attention. Separate carrier delay from warehouse, inventory, address, customer, damage, and data-quality causes.

Scope

Assess order lines, promised date, pick and ship events, tracking milestones, proof of delivery, return records, damage claims, customer tickets, carrier service level, warehouse, SKU, quantity, and destination region. Calculate on-time-in-full and classify late, failed, short, damaged, lost, and misrouted deliveries.

Excluded: changing orders, filing claims, contacting carriers or customers, rerouting parcels, and inventing a delivery event.

Data basis

• Order-line table: order_id, line_id, sku, ordered_qty, promised_date, ship_from.
• Shipment and carrier events: tracking_id, shipped_at, delivered_at, event_code, carrier, service_level.
• Receipt, return, damage, ticket, inventory, address, and warehouse records.
• OTIF definition, cutoff timezone, tolerance, exception taxonomy, and severity policy.

Result

Produce a results sheet with one row per order line and an exception memo grouped by cause, carrier, warehouse, customer segment, and promised-date cohort.

Quality criteria

• OTIF counts use the declared order-line denominator and exclude only documented cancellations.
• Delivered timestamp, timezone, quantity, and proof-of-delivery status are cited for each outcome.
• A late shipment is not labelled carrier-caused without a carrier event or agreed handoff timestamp.
• Duplicate tracking IDs, partial shipments, split orders, and returns remain visible.
• Exception totals reconcile to the assessed order-line population.

Instructions

Use promised date and the policy's timezone and grace window. Evaluate quantity and timing independently before assigning OTIF. For split shipments, mark the line complete only under the supplied consolidation rule. Prefer event chronology over free-text tickets, while retaining tickets as supporting evidence. Rank severity by customer impact, quantity affected, delay days, and policy thresholds. Label root causes confirmed or suspected.

Adapt before use

• Map order, shipment, event, receipt, quantity, ticket, and warehouse columns.
• Add the OTIF definition, time zone, grace period, cancellation rule, and severity matrix.
• Define carrier handoff evidence and the required exception-owner vocabulary.