Parcel Claims and Delivery Exceptions: What to Do When an Order Is Lost, Damaged, or Stolen
Lost, damaged and never-received parcels are a normal cost of shipping at volume. Here is how carrier claims actually work, what evidence you need, and why most of it is created at the packing bench.
Every brand that ships parcels eventually gets the email: the order says delivered, the customer says it never arrived. Or the box turns up with a corner caved in. Or tracking simply stops moving in a sort facility three states away.
These are delivery exceptions, and they are a normal cost of doing business at volume — not a sign that something is broken. What separates operations that handle them well from ones that bleed time is whether the rules were written down before the first exception landed.
Three failure modes that look identical to the customer
From the buyer's side there is one problem: no usable product. Operationally there are three, and they are handled differently.
- Lost in transit. The parcel stops scanning and never resumes.
- Damaged in transit. It arrives, but the contents are unsellable or unusable.
- Delivered, not received. A delivery scan exists; the recipient disputes it.
Sorting an inbound complaint into one of these three buckets within the first reply is the single highest-leverage step in the whole process, because each bucket has a different waiting period, a different evidence pack, and a different likely outcome.
Start with the carrier's definition, not your own
Carriers will not open a claim the moment a customer complains. Most require a package to be past its service commitment by a defined number of business days before it is even eligible to be declared lost — and "delivered but not received" usually carries its own, separate waiting window. Filing before that window opens is the most common reason a claim is rejected outright, and refiling costs another cycle.
| Exception type | What the carrier typically asks for | Who normally files |
|---|---|---|
| Lost in transit | Tracking number, ship date, declared value, proof of value such as the order record or commercial invoice | Shipper of record |
| Damaged in transit | Photos of the outer carton, the internal packaging and the item, plus retention of the packaging itself | Shipper, using recipient photos |
| Delivered, not received | Full delivery scan detail, any photo-on-delivery or geolocation record, and a written statement from the recipient | Shipper of record |
Note the third column. In almost every case the shipper of record files, not the buyer — which means if you use a third-party fulfillment partner, the claim paperwork has to move between two organisations under time pressure. Agree on who drafts it and who signs it while you are onboarding, not during your first dispute.
The evidence is created at the packing bench, not at claim time
A damage claim is won or lost by what your operation can prove about the parcel before it left the building. That means a captured outbound weight, a recorded carton size, a note of which void fill was used, and — for high-value items — a pack-out photo tied to the order number.
If a fulfillment operation cannot reconstruct what was in the box and how it was protected, a damage claim becomes one party's word against another's, and carriers resolve those in their own favour. This is worth raising directly when you evaluate a outsourced fulfillment partner: ask what is recorded at pack-out and how long those records are retained.
Decide the customer-facing rule separately from the claim
The claim and the customer are two different clocks. Recovering money from a carrier can take weeks; the customer relationship will not wait that long. Write a standing rule so nobody has to improvise:
- Under a stated order value, reship or refund immediately and file the claim in the background.
- Above that value, confirm the exception type first, then reship.
- For "delivered, not received", require a written statement before reshipping, and track repeat addresses.
The threshold matters less than having one. Support agents making case-by-case value judgments at eleven at night is how policy drift starts.
Know what is actually covered
Carrier liability defaults are low and are not insurance. Anything above the default has to be declared — and declared value costs money per parcel, so it only makes sense above a certain order value. Third-party parcel coverage is an alternative with its own exclusions, commonly around fragile goods, electronics and items packed without adequate cushioning. Read the exclusions before assuming a category is covered.
Feed exceptions back into packaging and routing
Exception data is a packaging signal. If one SKU generates damage claims disproportionately, the answer is usually carton or cushioning, not carrier — which is where carton selection and dimensional weight decisions come back into play. If exceptions cluster on one service level or one destination region, that is a routing signal instead, and belongs in the conversation about how your 3PL chooses which service ships each order.
Reviewing exceptions monthly, tagged by SKU, carrier, service and destination, turns a support annoyance into an input for two decisions you were going to make anyway.
Most of this depends on one thing: whether the pack-out record still exists when someone goes looking for it weeks later. That is a systems question, and it is part of what our own warehouse platform, AIDWMS, is built to keep hold of.
