How to File a Courier Claim for a Lost Shipment, Step by Step

Why a lost parcel costs more than the parcel

The direct loss is the goods and the shipping charge. The hidden cost is the staff time spent on each case. Someone has to pull the tracking history, find the invoice, fill in a form, answer the carrier's follow-up questions, and then tell the customer what happens next. When the claim is refused or late, the business pays the full cost of the item again, and the customer relationship takes a hit.

The value at risk depends on how the parcel was shipped. Carrier liability is often much lower than the value of the goods. UPS, for example, applies a default liability of $100 to most shipments unless a higher value is declared when the label is created, and a declared value above that level carries an extra charge. Anything above the declared amount is not recovered from the carrier. If you ship goods worth $400 with no declared value, you are carrying the difference yourself. Check the carrier's current terms for your service, because liability rules differ by carrier, service level and country.

To estimate your own cost, use three numbers from your own records: the number of parcels lost or unresolved in a year, the average value above the carrier's liability limit, and the hours your team spends on each case. Multiply the hours by the loaded hourly cost of the person doing the work. Add any refunds you issued to customers before the carrier paid, and any claims that expired. That total is the figure to compare with the cost of automating the process. Industry-wide loss rates vary too much by route and carrier to quote a single reliable figure here.

The manual way and the automated way

The difference is not the claim form. Carriers accept claims through their own portals, and a person can always fill them in. The difference is who watches the deadlines, who collects the evidence, and who notices when a carrier asks for something.

Automation does not decide whether a claim is valid. A person still decides whether to accept a carrier's offer, whether to refund a customer before the carrier pays, and how to handle a dispute the rules do not cover.

How to automate it, step by step

1. Connect the tracking data. Most carriers provide tracking through an API or push notifications. FedEx has a tracking API with a daily usage limit, and its newer Advanced Integrated Visibility product sends near real-time updates to your server by webhook. UPS and USPS also offer tracking interfaces. If you use a shipping platform or a multi-carrier tool, check whether it already pulls tracking events for you before building your own connection. Store every event against the order number.
2. Set the lost-parcel rule. Define when a parcel counts as lost for each carrier and service. A common working rule is no tracking movement for a set period after the expected delivery date, but the exact threshold varies, so write it down per carrier and check it against each carrier's current terms.
3. Collect the claim pack automatically. For each flagged parcel, gather the tracking history, the shipping label, the commercial invoice or purchase invoice, proof of value, and any photos taken at packing. Where the carrier provides a proof of delivery, pull it too. FedEx makes signature proof of delivery available for up to 16 months from the ship date, but needs the shipper's account number in the request to include the signature image. UPS returns proof of delivery letters in its tracking response. DHL and USPS offer their own proof of delivery services. Store the pack in one folder linked to the tracking number.
4. Read the documents. Invoices and delivery notes often arrive as scanned PDFs or photos. Optical character recognition (OCR) tools read the printed text, and a language model can check that the invoice number, declared value, and consignee name match the shipping record. Flag any mismatch for a person. Do not let the reader decide the value on its own, because a declared value that differs from the customs or commercial invoice is a common reason claims stall.
5. Generate the claim, then have a person approve it. The system fills the carrier's form fields, or drafts the email for carriers that accept claims by email, such as DHL's cargo claims address. A named staff member reviews each pack before it is sent. This is the control point that prevents bad claims from going out.
6. Chase on fixed dates. Set reminders at fixed intervals after submission, for example at the carrier's usual response window and again before the deadline. If the carrier asks for something, such as a signed statement from the recipient, the system sends the request to the right person and tracks the response time. Log every reply in the case record so the next person sees the full history.
7. Update the customer and the ledger. Send an approved message through email or WhatsApp at each stage. The WhatsApp Business Platform Cloud API, run by Meta, lets a business send messages and receive delivery and read receipts from a business phone number. Customer service messages sent within an open conversation do not need pre-approved templates, but messages to customers who have not written in recently do need an approved template. Record the refund, the carrier payment, or the write-off in your accounting system, such as an ERP or your accounting package.

For a business with one carrier and a few parcels a week, steps 1 and 3 can be done with a shared spreadsheet and a folder, with reminders set in a calendar. The full chain is worth building when parcels are numerous, several carriers are involved, or deadlines are missed regularly.

The deadlines you have to build in

Carrier rules are the part most likely to be wrong in any guide, including this one, because they change and because sources disagree. The table below shows the rules as reported by several third-party sources in 2026. Check each carrier's own claims page before you set the system up, and use the shortest window as the working deadline.

The sources disagree on UPS and on which date starts the clock. Treat the earliest date any source gives as your deadline. The deadlines are hard stops in most cases, so a claim filed one day late is often refused.

What breaks and how to prevent it

The most common failure is a claim sent under the wrong party. In most cases the shipper of record files the claim and receives the payment, not the buyer. If your customer bought from you but the label was in your name, you file. If a marketplace or fulfilment partner created the label, the claim may have to go through them. Build the rule into the system so that the claim owner is set when the label is created.

The second failure is an incomplete pack. Carriers commonly reject forms with blank required fields, and the clock can restart each time they ask for more documents. The fix is a checklist the system enforces before submission, not a reminder to check later.

The third failure is a mismatch between the claimed value and the invoice or customs declaration. A claim that asks for more than the invoice shows will be questioned. Make the system compare the two figures and stop the submission if they differ.

The fourth is a parcel that is only late. Filing too early can slow the carrier's own search, and some carriers want a waiting period for a reason. The fix is a clear threshold and a human check before the first claim is sent.

The fifth is a scanned document the reader cannot read. OCR works well on clean printed invoices and poorly on blurred photos, handwritten notes or stamps. Route unreadable documents to a person rather than guessing.

The sixth is a changed carrier rule. Portals and terms change, and an automation that worked last year may submit to the wrong form. Assign someone to review the carrier pages every quarter and log the date of each review.

When not to automate

Automation is not worth building when you ship only a handful of parcels a year. A spreadsheet, a calendar reminder and a standard checklist will do the job, and the build cost will exceed the saving for a long time.

It is also the wrong choice when most losses are caused by your own packing or addressing errors. Automating the claim does not fix a supplier who packs badly or a checkout form that lets customers mistype addresses. Fix the cause first, then decide whether claims still need automating.

High-value or disputed cases should stay with a person. Theft after a parcel is marked delivered, claims where the carrier questions whether the goods were ever in its custody, and claims with legal or insurance implications need judgement. The automation can gather the facts and flag the case, but a person should decide and sign off.

Finally, do not automate a process you do not yet understand. If nobody on your team can explain why a claim was refused last time, the first job is to learn the rules and write down the working process. A system built on guesses will repeat the same mistakes faster.

What it typically takes

The time needed depends on the number of carriers and the state of your records. For a single carrier with clean shipping records, the first version can usually be set up in a few weeks of part-time work by someone who knows your shipping process, plus a developer or integration specialist for the tracking connection. Multi-carrier setups take longer because each carrier has its own data format, portal and deadline rules. Document scanning and the WhatsApp connection add time, mainly for approvals and testing with real cases.

Plan for a testing period of several weeks in which a person checks every automatically generated claim before it is sent. After that, the review can narrow to exceptions. The ongoing work is small but real: a monthly check of open cases, a quarterly review of carrier rules, and a periodic review of the templates your customers receive.

The person who used to do this work does not disappear. They move from chasing forms to reviewing exceptions, handling disputes, and fixing the causes of loss. The business still needs someone to own the claims process and answer for it.