An exception status says that a shipment needs attention, but its meaning depends on the carrier’s actual description. A customs hold, address problem and unsuccessful delivery attempt require different next actions. Preserve the source evidence instead of replacing it with one generic failure message.
Trace’s action feed distinguishes carrier_fact from trace_inference. A carrier-fact exception attributes a reported condition to the source; it is not an independent investigation or a guarantee about what will happen next.
Start with the original evidence
Read the latest event text, location when present, scan time and last verification time. Keep the order and parcel mapping available to the authorized support operator. If the source has not been refreshed successfully, make that limitation visible before deciding whether the condition is still current.
| Reported issue | Investigation prompt |
|---|---|
| Customs | Check the carrier’s stated document or clearance requirement. |
| Address | Verify the merchant’s fulfillment address through its authorized system. |
| Delivery attempt | Review the carrier’s stated redelivery or collection instructions. |
| Return | Determine which shipment cycle is returning and why. |
| General exception | Read the original description; avoid guessing a more specific cause. |
Record who is investigating and what they checked
Use an owner label and a resolution note to keep a clear handover. An owner label is a workflow label, not a new team account or permission grant. Notes should describe the evidence reviewed and the next action without storing unnecessary customer personal data.
Acknowledgement, assignment and resolution are explicit mutations. Do not automatically replay them when a network response is ambiguous; inspect current workflow state first. A support note must not be treated as a carrier scan.
Explain the condition without promising an outcome
A buyer message should identify the parcel, state what the carrier reported and explain the merchant’s next action. If a delivery estimate is absent, leave it absent. Do not generate customs charges, legal advice or a guaranteed release date from the exception label.
For a split order, keep unaffected parcels visible. One parcel’s exception does not establish that the entire order failed, and another parcel’s delivery does not resolve the exception.
Close the investigation and watch for recurrence
Human resolution records the investigation result; active remains the underlying rule condition. Later verified evidence can clear that condition. If it returns after clearance, treat the new recurrence as a new operational event and preserve the earlier history.
Test an exception followed by a successful scan, an acknowledged but still active issue, and a later recurrence. Verify that the dashboard, customer page and notification consumer agree on what was observed and what an operator merely recorded.
Common questions
Can resolving an alert clear a carrier exception?
It records your investigation outcome. It does not alter carrier evidence or guarantee that the underlying condition has cleared.
References & next steps
Implementation details were checked against Trace’s current API. External product details may change; verify the linked documentation before deciding.