# Delivery exception handling

> Detect a shipment going wrong and act before the customer notices.

- Skill: `vstorm-co/delivery-exception-handling` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vstorm-co/delivery-exception-handling`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vstorm-co/delivery-exception-handling/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: vstorm-co (https://skillmd.com/u/vstorm-co)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vstorm-co/delivery-exception-handling

---


# Handling a delivery exception

The difference between a logistics problem and a customer problem is who finds
out first.

## Detect

No scan within the expected interval · a scan outside the planned route · a
failed delivery attempt · a customs hold · a temperature excursion on a
controlled load · an ETA that has moved past the promised date.

## Act on the customer before the carrier answers

Tell them what happened, the new expectation, and what you are doing. A customer
told at hour two is informed; the same customer discovering it at day three has
a complaint.

## Per exception type

Failed attempt → confirm the address and arrange redelivery, do not simply
retry. Customs hold → find out what is being asked for and who must provide it,
and say the deadline. Temperature excursion → quarantine on arrival, do not
accept into stock. Lost → start the claim and dispatch a replacement in
parallel, never in sequence.

## Never

Wait for the carrier's investigation before telling the customer, or promise a
new date the carrier has not given.