Shipment exception to an investigation and a credible customer update
Use this playbook when an order is not progressing as the customer expects. The objective is a verified state, an accepted investigation and a specific next update. Sending the tracking link again is not a resolution when the same unresolved event remains on the carrier page.
Keep the stages distinct
Order accepted, label created, carrier acceptance, delivery exception, delivery, return receipt and refund are separate states. Name the authoritative system for each. A business may generate a label before the carrier physically receives the parcel, so the customer message must describe the actual evidence.
Shippo and ShipStation can be investigated for shipping execution. Goflow and Linnworks address broader order coordination. Validate the configured event transfer and notification behavior rather than assuming an integration sends every update correctly. Shippo overview and ShipStation scope.
Open one accountable exception record
| Field | Useful content |
|---|---|
| Order and parcel references | Source order, shipment and affected line items |
| Verified event | Exact state, source and observation time |
| Customer request | What the buyer needs, in their own terms |
| Investigation | Question to warehouse or carrier and reference |
| Owner and backup | Person accepting the case during staffed hours |
| Next update | A time the business can meet, even if no final answer exists |
| Remedy authority | Who can approve replacement, cancellation or refund |
Keep the case open until the accepted action and customer update are recorded. An internal carrier enquiry is progress, not proof that the buyer's problem is resolved.
Classify the first action
For no first scan, verify warehouse handover before claiming the parcel is moving. For an in-transit exception, inspect the carrier event and the applicable service process. For partial delivery, identify the remaining items and parcels. For an address change, establish whether the party currently holding the parcel can accept it.
Avoid invented universal waiting periods. Set review and escalation times appropriate to the carrier, service and your customer promise. Give the customer an honest next-update window instead of an unsupported arrival guarantee.
Prevent conflicting system updates
Identify which application sends the shipping notification and which support record stores the investigation. Shippo's Shopify guidance describes updating tracking and fulfillment and optionally triggering a Shopify notification; inspect those settings before enabling another email source. Integration guidance.
A repeated event should not create duplicate messages. A cancelled label should not leave an unquestioned 'shipped' claim. Keep a manual review route for missing, late and contradictory updates.
Run a representative rehearsal
Use staff-controlled cases for no first scan, two parcels, a cancelled label and a returned item. Ask someone outside shipping to explain the current state and next action using the record. Inspect the actual customer email, not merely the internal status.
For financial remedies, record the approved action and actual payment-system state separately. Do not close the case only because another department was contacted.
Review and improve
Count exceptions without an owner, overdue updates, repeated enquiries and cases reopened because the promised action did not happen. Review a small sample regularly before increasing automation.
Use Shippo vs ShipStation for shipping selection and Goflow vs Linnworks for multichannel control. Keep a working existing tool if clearer investigation ownership solves the customer problem.
Research basis: official information reviewed November 2, 2026, with original editorial analysis. Trial scenarios are proposed checks, not hands-on results. Confirm current plans and availability before purchase.