A customer emails support. The package arrived crushed, the product is broken, they want a refund. Your customer service person does what customer service people do. They apologize, refund the order, maybe send a replacement. The ticket closes. Everybody moves on.
What didn't happen. The carrier claim. Shipping insurance. The policy coverage that should have paid for this loss. The ops team didn't file because the workflow didn't include it, or it included it but it's a pain, or the filer couldn't remember if this shipment had insurance in the first place.
Across a mid-market Shopify store doing 50,000+ shipments a year, this adds up to a real number. The benchmark from our own customer data and industry surveys is that stores recover 30% to 60% less than they could on shipping damage, purely because the claim workflow is ad-hoc and claims get forgotten.
Below is the decision tree. Who pays for damaged-in-transit losses, when each party applies, and the specific workflow that actually captures the recovery you're entitled to.
The four possible payers
When a package arrives damaged, one of four parties covers the loss.
- The carrier (UPS, FedEx, USPS, DHL, regional carriers) through their built-in declared value coverage or through a filed claim against the shipment.
- Third-party shipping insurance (Shipsurance, Route, InsureShield, others) through a separate policy purchased at ship time.
- The merchant, eating the loss out of refund budget.
- The customer, if the damage is their fault, not the carrier's.
The decision tree below helps you land on the right one. Most merchants default to option 3 for 80%+ of damage claims, which is exactly where the recoverable money is leaking.
Decision tree, in order
Step 1: is the damage clearly the customer's fault?
Most of the time, no. Occasionally yes. The customer accepted delivery, moved the package to the garage, their toddler or their dog got into it, and now they want a refund. The evidence here is usually obvious in the photos they send. The package isn't damaged, the product is damaged in a way inconsistent with shipping stress, or there's a significant time gap between delivery and the damage claim.
If the damage is clearly the customer's fault, decline the claim (with appropriate tone) and offer a courtesy discount on a repurchase. If it's ambiguous, treat the customer fairly and proceed down the tree.
Step 2: was the package externally damaged at delivery?
The answer to this question determines everything downstream, and it's the question most merchants fail to ask in the first support email.
Externally damaged. Crushed corners, torn cardboard, wet package, visible seal-breaking. This is a carrier claim. The damage happened in transit, the carrier handled the package negligently, and their declared value coverage or your insurance applies.
Internally damaged, externally fine. The product is broken but the box isn't. Harder. Could be packaging failure (the product wasn't packed well enough for normal shipping stress) or a manufacturer defect (the product was already damaged when shipped). Carrier claims are weak here. The carrier will argue they handled the package normally. Your own shipping insurance may still cover it. Self-insured losses often fall here.
Make the support team ask for photos at first contact. The package, the product, any internal packaging material. That's the evidence you need for everything downstream, and asking for it at the end of the workflow (after you've already issued a refund) is too late.
Step 3: is the shipment within the carrier's claim window?
Each carrier has different filing windows:
- UPS: 60 days from delivery for damage claims, 9 months for loss.
- FedEx: 60 days from delivery for damage, 9 months for loss.
- USPS: 60 days for most services, 15 days for Priority Mail.
- DHL: 30 days typically.
Miss the window, lose the claim. This is why the workflow matters. A damage claim that sits in support for three weeks waiting for photos, then another two weeks while you debate whether to refund, can blow past the carrier's filing deadline before anyone files.
If you're past the window, the carrier is off the hook. Third-party insurance may still apply (many policies extend the filing window to 90 days or more), but your primary recovery option just closed.
Step 4: does the shipment have declared value or third-party insurance?
Default carrier coverage is limited. UPS and FedEx both include $100 of declared value automatically on most shipments. Above that, you need to have declared a higher value at ship time, and you pay a per-$100 fee for the additional coverage. USPS Priority Mail includes $100. Priority Express includes $100. Registered mail and insured mail both add coverage at additional cost.
For high-value shipments, most mid-market merchants use third-party shipping insurance. Shipsurance is the most common, Route has become popular, InsureShield is used by some. These services typically cover damage, loss, and theft up to the declared value, with faster claim processing than carrier claims and more merchant-friendly terms.
Your shipping label should capture the declared value and any insurance policy ID. If your Shopify shipping setup doesn't record this per-shipment, that's the first fix.
Step 5: file the claim.
This is where the workflow typically breaks. Each carrier and insurer has a different claim process:
- UPS. Via ups.com/claims, requires tracking number, shipment details, damage evidence (photos), and the declared value. Processing time 8 to 15 business days.
- FedEx. Via fedex.com/claims, similar requirements. Processing time 5 to 10 business days for damage claims with photos.
- USPS. Form 1000 (Insured Mail) or online via usps.com. Processing notoriously slow, 30 to 60 days.
- Route. Via their merchant portal, usually fastest of all (2 to 5 business days) because their business model depends on fast resolution.
- Shipsurance. Via claim form, processing 10 to 15 business days.
The merchant needs tracking number, order details, damage photos, and evidence of the product's value (invoice, order confirmation). If any of these are missing, the claim gets denied and re-filing restarts the clock.
Step 6: refund the customer.
The subtle part. Most merchants refund the customer first, then file the claim. Works, but it means the merchant is out the money until the claim processes (which might be weeks), and if the claim gets denied, the merchant is permanently out the money.
A slightly better workflow: refund the customer immediately (don't make them wait, that's bad CX), but tag the order in your ops system as "carrier claim filed, recovery pending." When the claim pays out, the refund cost is offset. If it's denied, you know specifically why.
The workflow most stores have vs. the workflow that works
Most stores: customer emails support, support issues refund, ticket closes, carrier claim gets filed sporadically (often weeks later by someone who has to dig up the tracking information retroactively), 30% to 50% of claimable losses never get claimed.
Workflow that works:
- First support touch. Support asks for photos of package + product, logs the order + tracking + damage description in a structured ticket.
- Structured damage log. A simple Airtable, Google Sheet, or dedicated tool tracks all damage claims with columns for tracking, carrier, declared value, insurance policy, claim status, recovery amount.
- Refund customer immediately. From the refund workflow, not blocked on anything.
- Claim filing within 5 business days. A single person or small team owns the claim workflow, files against the appropriate carrier or insurer with the photos already in hand.
- Follow-up tracking. Claims that don't resolve in the expected window get pinged. Denied claims get reviewed and often re-filed.
The difference between these two workflows at a $20M revenue store is typically $30K to $80K annually in recovered shipping loss. At higher volumes it scales close to linearly.
Where the loss really comes from
Three categories eat most of the forgotten-claim money.
The internal-damage / external-fine gray zone. The store doesn't think it has a carrier claim because the box looks OK. Sometimes it actually does. Carrier handling can damage products without visible box damage (drops onto corners, stacking stress). Even when the carrier claim is weak, third-party insurance often still pays if the policy terms include "damage in transit" broadly. Filing the claim costs 20 minutes and has a 40% to 60% chance of recovering the full value.
The multi-item order with one damaged item. Customer claims one product is broken. Store refunds the one product. Claim never gets filed because "it's just one item, not worth it." Over a year, at a store with 3 to 4 such claims a week, that's $20K to $50K of small claims that individually weren't worth the effort and collectively absolutely were.
The delayed damage report. Customer reports damage 45 days after delivery. Carrier window on UPS/FedEx is 60 days, so the claim is still filable, but only if you file fast. Most stores don't. The claim dies on the ops team's desk while they debate whether it's still worth filing. By the time they decide, it isn't.
A structured damage tracker fixes all three. It surfaces the pending claims, keeps the deadlines visible, and makes the filing decision routine rather than discretionary.
When the customer is actually at fault
This comes up less than merchants think, but it does come up.
Delayed damage report (60+ days). The customer had the product in their possession for months, and damage almost certainly happened in their hands, not in shipping.
"Acceptance" damage. The delivery driver's photo shows an intact package. The customer accepted delivery. Three days later, they claim the product was damaged. The pattern on repeat customers with multiple "acceptance" damage claims is a fraud signature. The kind of thing that ends up in the INR and post-delivery abuse categories.
Damage inconsistent with shipping. A liquid spilled on the inside of a product that was wrapped in sealed plastic outside. A crack in a pattern that doesn't match how it would have been stored in the box. Physical signs of use prior to the damage claim. These patterns don't prove fraud but should shift the response from "refund + file carrier claim" to "request the product back for inspection before refunding."
Your fraud scoring engine should weight these customer-level signals (repeat damage claims, unusual timing patterns, claim-to-order ratio above a threshold) the same way it weights return-fraud signals. The decision tree changes: if the customer is a repeat claimant with a high pattern score, the response is "no refund without returned product" rather than instant refund.
The takeaway
Damaged-in-transit losses have a recovery path. Most Shopify stores don't use it, or use it inconsistently, because the workflow to file carrier claims sits outside the normal support-ticket workflow and gets forgotten. The money left on the table at mid-market scale is $30K to $80K a year in recoverable claims that never got filed.
The fix is procedural, not technical. Capture damage photos at first customer contact. Log claims in a structured tracker. File within 5 business days. Monitor claim resolution. Don't let damage claims close in support without a recovery status attached.
And for the claims where the customer is the one at fault, make sure your fraud scoring layer sees those patterns. A customer with three damage claims in a year is a different risk than a customer with zero, and refunding their fourth without asking any questions is exactly the pattern the abusers count on.