Automate Lost Package Claims with FedEx and UPS
How to automate lost package claims with FedEx and UPS: the steps from ticket to filed claim, what an agent can do, and what a person keeps.
Mustafa BayramogluOctober 25, 20267 min read
To automate lost package claims with FedEx and UPS, start the claim from the exception, not from the customer complaint: detect the overdue parcel, gather the tracking number and proof of value, file through each carrier's claims tool, and keep a person on exceptions and on the customer decision. An SOP-driven agent can run the routine steps, but the carrier alone decides what it pays.
What a lost-in-transit claim needs before anyone files it
A lost-in-transit claim is filed against a shipment the carrier never delivered, which makes it different from a package marked delivered. For that second case, see our guide to delivered but not received disputes.
Every claim starts with the same three inputs: the tracking number, proof of what was in the box and what it was worth, and the order invoice. FedEx's claims FAQ says you can file online for a priority, standard or freight shipment that is damaged, lost or missing contents, and that you need your tracking or PRO number. The FedEx claims page describes filing a single claim or a batch claim online.
On timing, UPS publishes the clearest rule. Its claims page says to start a claim within 60 days of the scheduled delivery for packages that have been lost or damaged. That wording was current in the search snapshot we captured on 2026-10-20, and the UPS claims page is the place to confirm it. We could not retrieve a current FedEx filing window for lost packages from FedEx's own US pages, so we do not state one here. Check FedEx's page for your service and country, and build the deadline into the workflow as a setting you can change. For a longer look at UPS paperwork, read the UPS claims process guide.
The flow from a lost-package ticket to a filed claim
The sequence below is the one an SOP should spell out, whether a person or an agent runs it.
- Detect. Flag a parcel that has stopped scanning or is past its expected delivery date, and open a case before the customer writes in.
- Confirm. Check the tracking history. If the customer reports a missing package that tracking shows as delivered, FedEx points them to Manage Delivery and then Report Missing Package.
- Assemble evidence. Pull the tracking number, the order invoice, the item values and any photos from the order system and the helpdesk ticket. Record the date you pulled each item.
- File. Submit through the carrier's online claims tool. FedEx says you can log in, create a claim and submit it without calling customer service or sending faxes or email.
- Tell the customer. Send a status message with what you filed and when. Decide the refund or reship by your own policy instead of waiting on the carrier. Our post on resolving damaged package claims walks through that replace versus refund choice.
- Track to close. Watch the claim status, answer any request for more documents, and record the payout against the order.
Steps 1, 3 and 6 are where manual teams lose time, because they depend on someone remembering to look. The broader pattern across claim types is covered in the shipping claims automation guide.
What an SOP-driven agent can automate and what a person keeps
CorePiper builds agents from a team's SOPs, policies and runbooks, and lost packages are one of the case types it handles. Its workflows reach FedEx and UPS alongside tools such as Shopify and Zendesk. For a lost-package SOP, that points to a split like this.
Routine steps an agent can run:
- Opening the case when the exception appears, and gathering the order, invoice and tracking details into one record.
- Drafting and sending the customer update, and applying your refund or reship rule for orders inside the limits your SOP sets.
- Preparing the claim and following its status.
Steps a person keeps:
- Exceptions: CorePiper's design is that routine cases run on their own while people approve exceptions and high-impact actions. Do not read that as every action needing approval; your SOP sets the line.
- High-value shipments, repeat claimants and anything the carrier disputes.
- The outcome itself. FedEx says reimbursement requires proof of loss and proof that FedEx is at fault, so a filed claim is a request, not a result.
Carrier portals, parcel audit tools and an SOP-driven agent
There are three routes, and they solve different problems.
| Route | What it does | What it leaves to you |
|---|---|---|
| Carrier claims tools | You file in the carrier's own online tool, FedEx Claims Online or the UPS claims page. | Spotting the lost parcel, gathering documents, writing to the customer |
| Parcel audit tools | Vendors such as LateShipment advertise automatic initiation of UPS lost or damaged package refund claims. | The customer conversation and your own refund or reship decision |
| SOP-driven agent | Runs the ticket from detection through customer update using your SOP, with people approving exceptions. | Exceptions, and the carrier's final decision |
These are not exclusive. A team can keep the carrier tools as the filing channel and put an agent in front of them to run the ticket. If you only need carrier refunds recovered and your support team already handles customers well, an audit tool may be enough. If lost packages arrive as support tickets that need evidence, a customer reply and a claim, the ticket side is where an agent helps.
Where lost-package automation breaks
Most failures come from the SOP, not the software. Four are worth designing against before you switch anything on.
A deadline nobody owns. The filing window starts from a carrier date, not from the day the customer writes in. Store the scheduled delivery date on the case, compute the last filing day from the rule you confirmed for that carrier, and put the case in front of a person well before that day. A claim that misses its window is lost whatever the evidence says.
Thin evidence. A claim built from a tracking number alone invites a request for more documents. Decide in the SOP which fields must be present before filing: the invoice, the item values, the ship-from and ship-to details, and the customer's report. If a field is missing, the case should go to a person and not be filed incomplete.
Duplicate or double compensation. A customer can be refunded or reshipped while a carrier claim is also paid. Record both against the order so finance can see what the shipment cost and what came back. It also stops two people, or a person and an agent, from filing the same claim twice.
Detection that is too eager. A parcel that has not scanned for a day is not necessarily lost. Pick a trigger you can defend, such as no scan after the expected delivery date, and review how many cases it opens that later turn up delivered. Tighten or loosen it from that count, which you can read from your own queue.
Review the first few weeks of cases by hand. Look at every case the agent filed or held, and rewrite the SOP line behind any decision you would have made differently. That feedback loop matters more than any single feature.
Where to start
Write the lost-package SOP first: the trigger, the evidence list, the refund rule, the filing steps and the exception line. Then automate the steps no one needs to judge, and keep a person on the rest. Confirm each carrier's filing window on its own page, and treat every payout as the carrier's decision.