A customer emails you at 9:47 PM: "My order never arrived. The tracking says delivered, but I don't have it. What's going on?"
Your stomach drops a little. Not because this is unusual—lost package claims happen to every ecommerce business—but because you're never quite sure what the right call is. Replace it and eat the cost? Refund and lose the sale? File a carrier claim that takes three weeks and leaves your customer waiting?
Here's the truth: most small ecommerce teams handle lost package support inconsistently. Not because they don't care, but because nobody ever wrote down the actual decision framework. Every ticket becomes a judgment call, which means different outcomes depending on who's answering and what kind of day it's been.
This guide gives you an operator-ready framework for handling lost package claims—clear decision points, specific thresholds, and real examples you can adapt for your team. Whether you're handling support yourself or working with an outsourced team like Evergreen Support, you'll know exactly when to replace, when to refund, and when to involve the carrier.
Table of Contents
Why Lost Package Decisions Feel So Hard
The Three-Path Framework: Replace, Refund, or Carrier Claim
Decision Matrix: Matching Situations to Actions
Required Information for Every Lost Package Ticket
Escalation Boundaries for Lean Teams
Sample Workflows and Response Templates
Preventing Lost Package Issues Before They Start
Frequently Asked Questions
Why Lost Package Decisions Feel So Hard
Lost package support sits at an uncomfortable intersection: customer service, logistics, and finance all collide in a single ticket.
The stakes feel high because they are. According to research from Loqate, delivery problems—including lost packages—contribute significantly to customer churn, with consumers increasingly expecting retailers to take responsibility regardless of carrier fault [1]. Your customer doesn't care that USPS lost the package. They ordered from you.
At the same time, the cost implications are real. Replace every "lost" package without verification, and you'll attract fraud. Demand extensive proof before helping, and you'll lose customers who simply won't bother.
Small teams struggle here because the "right" answer depends on multiple variables:
Order value
Customer history
Carrier tracking status
Time since shipment
Product type (can it even be replaced?)
Your current margins
Without a documented framework, each decision requires weighing all these factors from scratch. That's exhausting when you're also doing marketing, operations, and everything else.
The Three-Path Framework: Replace, Refund, or Carrier Claim
Every lost package situation ultimately resolves through one of three paths. Understanding when to use each one simplifies everything.
Path 1: Immediate Replacement
What it is: You ship a new order at your cost, no questions asked.
When it makes sense:
Order value is below your replacement threshold (typically $50-75 for most small ecommerce businesses)
Customer has good purchase history with no previous claims
Tracking shows genuine delivery issue (stuck in transit, no movement for 7+ days)
The product is in stock and replaceable
Why this works: For low-value orders, the cost of investigating typically exceeds the cost of replacing. You also preserve the customer relationship and avoid drawn-out back-and-forth.
Path 2: Refund
What it is: You return the customer's money rather than shipping a replacement.
When it makes sense:
Customer explicitly requests refund over replacement
Product is out of stock with no restock date
It's a one-time or custom product that can't be replicated
Customer relationship shows red flags (multiple claims, aggressive behavior)
Order value is high enough that replacement without investigation isn't viable
Why this works: Sometimes the cleanest resolution is financial. Particularly for high-value items or situations where you can't actually fulfill a replacement.
Path 3: Carrier Claim
What it is: You file a formal claim with the shipping carrier (USPS, UPS, FedEx, etc.) to recover the shipment cost.
When it makes sense:
Order value exceeds your claim-filing threshold (typically $75-150)
Tracking shows "delivered" but customer disputes receipt
Insurance was purchased on the shipment
Package is high-value and you need documentation for your records
You've already replaced or refunded but want to recover costs
Why this works: Carrier claims protect your margins on higher-value orders. They're slow (expect 2-4 weeks minimum), but they're the right move when real money is at stake.
Important note: These paths aren't mutually exclusive. You might replace immediately and file a carrier claim to recover costs. The customer-facing action and the back-office action can differ.
Decision Matrix: Matching Situations to Actions
Here's the framework your team can reference for every lost package ticket. Adjust the dollar thresholds based on your margins and average order value.
Scenario 1: Tracking Shows "In Transit" Beyond Expected Delivery Date
Typical timeframe: 3-7 business days past expected delivery
| Order Value | Customer History | Recommended Action |
| Under $50 | Any | Replace immediately |
| $50-150 | Good (no previous claims) | Replace immediately |
| $50-150 | New customer (no history) | Wait 3 more business days, then replace |
| $50-150 | Previous claim in past 6 months | Escalate to owner/manager |
| Over $150 | Any | Wait for carrier scan update (48 hours), then escalate |
Scenario 2: Tracking Shows "Delivered" But Customer Says Not Received
This is the trickiest scenario because "porch pirates" are real—but so is fraud.
| Order Value | Customer History | Recommended Action |
| Under $50 | Any | Replace with soft verification (ask if they checked common drop spots) |
| $50-100 | Good history | Replace after basic verification |
| $50-100 | New customer | Request customer file police report, then replace |
| Over $100 | Any | File carrier claim, offer replacement when claim opens |
| Any | Multiple "not received" claims | Escalate immediately |
Soft verification script: "I'm sorry to hear that! Could you check with neighbors, your building's mail room, or behind any bushes or gates where carriers sometimes leave packages? If it doesn't turn up by tomorrow, let me know and we'll get a replacement shipped right away."
Scenario 3: Tracking Shows No Movement (Stuck at Facility)
| Days Without Movement | Order Value | Recommended Action |
| 3-5 business days | Under $75 | Replace proactively |
| 3-5 business days | Over $75 | Contact carrier, notify customer of delay |
| 7+ business days | Any | Replace (or refund if preferred), file carrier claim |
Scenario 4: Package Returned to Sender
| Reason for Return | Recommended Action |
| Insufficient address | Contact customer for correct address, reship |
| Refused by recipient | Contact customer to understand why before refunding |
| Unclaimed | Reship with signature requirement, or refund |
| Damaged | Replace immediately, file carrier claim |
Required Information for Every Lost Package Ticket
Before your team can resolve a lost package claim, they need specific data points. Missing information means delays and back-and-forth that frustrates everyone.
Required fields (gather before any decision):
From your systems:
Order number
Order date
Order total
Shipping carrier and tracking number
Current tracking status (screenshot if possible)
Customer's complete shipping address
Customer's purchase history (total orders, total claims)
From the customer:
Confirmation of shipping address
Description of the issue ("never arrived" vs. "tracking says delivered but I don't have it")
Whether they've checked common delivery spots
Any relevant details (vacation, recently moved, etc.)
Red flag indicators (escalate immediately):
Customer has 2+ "lost package" claims in the past 12 months
Shipping address differs from billing address and is a known reshipping service
Customer immediately demands refund and threatens chargeback
Order contains high-value or frequently-targeted items
Customer refuses to provide any verification or check delivery location
Having this checklist documented means your support team—whether internal or outsourced—can gather everything in the first response rather than going back and forth.
Escalation Boundaries for Lean Teams
Not every lost package decision should sit with frontline support. Clear escalation boundaries protect your team and your business.
Support team can handle independently:
Replacements for orders under $75 (adjust based on your margins)
Standard "in transit" delays with proactive communication
Clear-cut tracking issues (stuck, returned to sender)
First-time claims from customers with good purchase history
Requires manager/owner review:
Single replacements or refunds over $150
Any customer with 2+ claims in 12 months
"Delivered but not received" claims over $100
Requests that involve both refund AND keeping merchandise
Any situation involving threats, legal language, or chargeback mentions
Requires documentation before resolution:
All claims over $200 (screenshot tracking, save email thread)
Repeated claims from same customer (build a file)
Any claim involving potential fraud indicators
Pro tip for outsourced teams: When you work with a support agency like Evergreen Support, these escalation boundaries should be documented during onboarding. Your external team should know exactly which decisions they can make and which need your input. This is actually where an outsourced team shines—they follow the playbook consistently, without the fatigue or "just this once" exceptions that creep in when you're handling tickets yourself at 10 PM.
Sample Workflows and Response Templates
Workflow 1: Standard Lost Package (In Transit, Under $75)
Step 1: Receive ticket claiming package not received
Step 2: Pull order details, verify tracking status
Step 3: Confirm tracking shows delay (not "delivered")
Step 4: Check customer history (any previous claims?)
Step 5: If no red flags, create replacement order immediately
Step 6: Send confirmation to customer
Step 7: Log original tracking number for carrier claim if needed later
Response template:
Hi [Name],I'm so sorry your order hasn't arrived yet—that's frustrating, and I want to make it right.I've just shipped a replacement order, and here's your new tracking number: [TRACKING]. You should see movement within 24-48 hours.If your original package does eventually show up, no worries—enjoy the extra!Let me know if you have any questions.[Your name]
Workflow 2: "Delivered But Not Received" (Over $75)
Step 1: Receive ticket claiming non-receipt despite delivery scan
Step 2: Pull order details, verify tracking shows delivered
Step 3: Check customer history and order details
Step 4: Send verification request (see template below)
Step 5: Based on response, either replace or escalate
Step 6: If replacing, file carrier claim simultaneously
Initial response template:
Hi [Name],I'm sorry to hear this—tracking does show your package as delivered on [DATE], which is concerning.Before I send a replacement, could you help me check a few things?Have you asked neighbors if it was delivered to them by mistake?Does your building have a mail room or package locker?Sometimes carriers leave packages behind gates, bushes, or side doors—any chance it's tucked away somewhere?If you've checked those spots and still can't find it, just let me know and I'll get a replacement shipped out today.[Your name]
Workflow 3: High-Value Order ($150+) with Carrier Claim
Step 1: Receive ticket, verify it meets high-value threshold
Step 2: Acknowledge issue and set expectations
Step 3: File carrier claim immediately (don't wait)
Step 4: Offer replacement contingent on claim processing OR immediate replacement if customer history warrants trust
Step 5: Document everything in your records
Response template (with claim):
Hi [Name],I'm really sorry about this situation—I know how frustrating it is when an order doesn't arrive as expected.Because this is a higher-value order, I've filed a claim with [CARRIER] to investigate. These typically take 5-10 business days to process.I don't want you to wait that long, though. Based on your order history with us, I'm going to ship your replacement today while we sort things out with the carrier. Your new tracking number is: [TRACKING]Thank you for your patience, and please let me know if you have any questions.[Your name]
Preventing Lost Package Issues Before They Start
The best lost package email is the one you never have to send. A few operational adjustments can reduce claims significantly.
At checkout:
Address verification: Use address validation software to catch typos before shipping. Services like Lob, SmartyStreets, or built-in Shopify features can flag suspicious addresses [2].
Delivery options: Let customers choose signature confirmation for high-value orders (even if they pay extra).
During fulfillment:
Photography: For orders over a certain threshold, photograph the packed box before sealing. This takes 5 seconds and provides evidence if needed later.
Insurance: Automatically insure orders over $100 through your carrier or a third-party like Route or Shipsurance.
After shipping:
Proactive tracking alerts: Send tracking updates automatically so customers know exactly where their package is.
Delivery delay notifications: If tracking shows unusual delays, reach out before the customer contacts you.
For high-risk situations:
Signature required: Mandate signatures for orders over $200 or for customers with previous claims.
Alternate shipping addresses: If an address has multiple failed deliveries, offer to ship to a different location or a pickup point.
Frequently Asked Questions
How long should I wait before considering a package "lost"?
Most carriers consider packages lost if there's no tracking movement for 7 or more business days. However, your customer's patience typically runs out sooner. For domestic shipments, I'd recommend proactive outreach after 3-5 business days of no movement, with replacement or refund offered by day 7. International shipments need longer windows—customs delays can add weeks.
Should I always file a carrier claim, even for small orders?
Not always. Carrier claims require time to file and track, and for orders under $50-75, the administrative cost often exceeds the recovery. File claims on higher-value orders where the potential recovery justifies the effort. That said, if you notice patterns (same carrier, same region), filing claims creates documentation that may help negotiate better rates or service later.
What if a customer has multiple lost package claims?
Two claims in a 12-month period warrants closer attention. It could be legitimate (bad carrier service in their area, problematic building mail room), but it could also indicate fraud. For repeat claimants, require additional verification before replacing—a police report for "not received" claims, or shipping with signature required. If claims continue, you may need to refuse service or ship only with verified delivery methods.
How do I handle international lost packages differently?
International shipments have longer transit times, customs delays, and additional points of failure. Adjust your timelines accordingly—don't consider an international shipment "lost" until 3-4 weeks past estimated delivery. Also confirm whether duties/taxes were required; some packages are held in customs until the recipient pays. Carrier claims are more complex internationally, so factor that into your cost-benefit calculation.
Should I require customers to file a police report?
For "delivered but not received" claims on orders over $100, requesting a police report is reasonable and serves as both verification and fraud deterrent. Many customers with legitimate claims won't mind—it documents the theft for them too. However, understand that some customers will balk at this requirement and walk away, even if their claim is valid. Use your judgment based on order value and customer history.
The Bottom Line
Lost package support doesn't have to be a guessing game. With clear thresholds, documented workflows, and consistent escalation boundaries, your team can handle claims confidently and fairly.
The framework comes down to this:
Low-value orders with no red flags: Replace quickly, move on
Mid-value orders with verification: Gather information, then act decisively
High-value orders: Document everything, file claims, and communicate clearly with your customer
Most importantly, write down your specific thresholds and share them with anyone handling support—whether that's you, your team, or an outsourced partner.
If you're spending too many hours each week on support tickets like these—and you'd rather focus on growing your business—that's exactly what Evergreen Support handles for small ecommerce and SaaS teams. We follow documented playbooks like this one so every customer gets consistent, high-quality help.
Ready to hand off your support inbox? Book a call to see if we're the right fit, or check out our pricing to learn how the month-to-month model works.
About Evergreen Support
Evergreen Support is a US-based customer support agency built specifically for small SaaS and ecommerce businesses. Our team of real humans handles your day-to-day email support so you can focus on growing your business—without losing the personal touch your customers love. Founded by operators who've been in your shoes, we emphasize clear documentation, consistent processes, and honest communication. Every client works with two dedicated agents, receives guaranteed responses within 24 hours (Monday-Friday), and benefits from our month-to-month, no-contract model.
Works Cited
[1] Loqate — "Fixing Failed Deliveries: Improving Data Quality in Retail." https://www.loqate.com/resources/research/fixing-failed-deliveries/
[2] Shopify — "Address Verification for Ecommerce." https://www.shopify.com/blog/address-verification
