Supply Chain / Logistics
Exceptions only stay recoverable when evidence, carrier rules, and SLA clocks move together.
This control plane makes shipment pressure, carrier requirements, recovery blockers, and customer-impact risk visible before an exception becomes a refund, claim, or churn event.
5Active shipment exceptions modeled through recovery pressure.
2Shipments inside the highest SLA-risk window.
3Carrier-rule mappings that still have blockers.
3Resolution packets that still have incomplete recovery posture.
Operating Recommendation
Clear customs and terminal-proof blockers first so recoverable exceptions do not spill into refunds and churn.
NorthLine Freight · SHIP-4108
Boston -> Dallas
6 hours left · Escalate terminal proof before the customer refund SLA opens.Harbor Parcel · SHIP-4176
Chicago -> Newark
10 hours left · Route replacement plan to support and hold outbound promise until station acknowledgement lands.Union Air Cargo · SHIP-4215
LAX -> Toronto
4 hours left · Correct invoice-code mismatch before customs detention converts to storage fees.Exception Queue
Which recoveries are most likely to slip next.
| Shipment | Packet | Owner | Hours Left | Risk |
|---|---|---|---|---|
| NorthLine Freight SHIP-4108 Boston -> Dallas | Scan trail + terminal note + customer priority flag | Carrier Ops | 6 | critical |
| Harbor Parcel SHIP-4176 Chicago -> Newark | Damage photos + station acknowledgement + replacement plan | Customer Support Ops | 10 | watch |
| Union Air Cargo SHIP-4215 LAX -> Toronto | Commercial invoice + commodity code + broker note | Trade Compliance | 4 | critical |
| Peak Freight Network SHIP-4280 Atlanta -> Denver | Missed-stop explanation + reroute ETA + consignee notice | Dispatch Reliability | 12 | watch |
| Vertex Last Mile SHIP-4339 Phoenix -> Tucson | Address verification + customer confirmation + reroute ticket | Last-Mile Ops | 18 | low |
Lane Coverage
Where recovery pressure is concentrated.
Boston -> Dallas1 modeled shipment in this lane.
Chicago -> Newark1 modeled shipment in this lane.
LAX -> Toronto1 modeled shipment in this lane.
Atlanta -> Denver1 modeled shipment in this lane.
Phoenix -> Tucson1 modeled shipment in this lane.
Carrier Rules
Recovery clarity comes from mapping the carrier rule to the evidence owner, not from logging the exception alone.
Refund avoidanceTerminal exception proof → Terminal note plus scan trail with priority-service flag
Storage-fee exposureCustoms mismatch correction → Corrected invoice, commodity code, and broker acknowledgement
Claim reimbursementDamage claim eligibility → Damage photos, station acknowledgement, and replacement-cost note
Customer saveReroute SLA recovery → Updated ETA, consignee notice, and missed-stop explanation