Delivery exception auto-resolution

The problem

Couriers occasionally fail to deliver — returned to sender, marked damaged, or stuck awaiting collection. Each of these used to need someone to notice the courier scan, work out what went wrong, contact the customer, arrange a reshipment, and remember to check it actually arrived.

The replay

Under the hood

A poller checks courier status codes on every active shipment. An RTS, damage, or stuck-in-transit scan triggers classification of the likely cause, a customer notification, and — once the customer responds or a default action applies — an automatic reshipment. The same poller then watches the reshipment and closes the exception the moment it's marked delivered, so nothing is left open waiting on a human to follow up.