Each row ties shipment context to the evidence packet, SLA window, and next action needed to keep the recovery path intact.
| Shipment | Excerpt | Owner | Next Action | Risk |
|---|---|---|---|---|
| NorthLine Freight SHIP-4108 Boston -> Dallas | Carrier exception requires a scan trail and terminal evidence before reroute credit is approved. | Carrier Ops | Escalate terminal proof before the customer refund SLA opens. | critical |
| Harbor Parcel SHIP-4176 Chicago -> Newark | Damage claims require photos, station acknowledgement, and customer resolution path before reimbursement. | Customer Support Ops | Route replacement plan to support and hold outbound promise until station acknowledgement lands. | watch |
| Union Air Cargo SHIP-4215 LAX -> Toronto | Cross-border hold cannot clear until the commodity code and invoice details reconcile. | Trade Compliance | Correct invoice-code mismatch before customs detention converts to storage fees. | critical |
| Peak Freight Network SHIP-4280 Atlanta -> Denver | Recovery path needs missed-stop proof and consignee-facing ETA narrative. | Dispatch Reliability | Bundle consignee notice with updated ETA before support confirms recovery. | watch |
| Vertex Last Mile SHIP-4339 Phoenix -> Tucson | Address-correction shipments can proceed once customer confirmation and reroute ticket are matched. | Last-Mile Ops | Finalize reroute ticket and watch only for carrier completion. | low |