A delivery exception is a carrier event that interrupts a shipment's planned journey to the customer: a weather delay, a failed delivery attempt, a wrong or incomplete address, damage in transit, or a package held at a facility. The order shipped, but it is no longer on plan.
In ecommerce, exceptions are where ordinary where-is-my-order questions turn angry. The customer has watched a tracking page sit on the same status for days, and the email they finally send arrives already frustrated. Support inherits the problem without having caused it: the event happened in the carrier's network, but the ticket lands in the merchant's queue. Some exceptions only need an explanation and a new date. Others are fixable if caught early: an address correction while the package is still moving, a reshipment triggered before the customer asks, a follow-up on a package stuck at a facility.
The popular response is the tracking-page chatbot: a widget that reads the stalled tracking status back to the customer who has been staring at it all week. Restating a status the customer can already see is deflection, not service. The harder truth is that the ticket was preventable. The carrier emitted the exception event days before the customer wrote in, and nobody was listening to it.
Reactive vs proactive exception handling at a glance
| Dimension | Reactive handling | Proactive handling |
|---|---|---|
| Who notices first | the customer, watching stalled tracking | the operation, from the carrier event |
| First message | an angry where-is-it email | a notification that explains the delay and the next step |
| Fixable exceptions | discovered after return to sender | corrected while the package is still in motion |
| Queue effect | duplicate tickets pile up per stuck package | fewer tickets, each answered with context |
Aide, the agentic AI platform for customer experience, handles delivery exceptions as their own intent rather than a flavor of where-is-my-order. It reads live tracking and fulfillment state before writing a word, answers with what actually happened and what happens next, takes only the actions the team has approved for it, and escalates genuinely stuck shipments to a person with the full history attached. Every automated reply and action is logged for review. See Aide for ecommerce customer service for how the whole delivery workload runs on a live store.
Frequently asked questions
- What causes a delivery exception?
- The common causes are weather and network delays, failed delivery attempts, incorrect or incomplete addresses, customs holds on international shipments, and damage in transit. Many resolve on their own; the rest need an address fix, a claim, or a reshipment.
- Should you notify customers about a delivery exception before they ask?
- Yes. The carrier event is visible to the merchant before the customer notices the stall, and a message that explains the delay and the plan removes the reason to write in. Proactive notice turns an angry ticket into a moment of earned trust.