E-commerce
June 28, 2026
Tracking shows "delivered". The customer swears they received nothing. Your agent responds "contact the carrier". Three days later: 1-star review, chargeback, public tweet.
The lost e-commerce parcel is not a classic WISMO. It is an ops + legal + customer relations issue. Metapack estimates that in Europe, missing parcels cost an average of £125 per incident (product, reshipment, customer service) (PowerCommerce, missing parcels).
This #202 guide formalizes the lost parcel support procedure: statuses, proof, messages, carrier claims. Distinct from tracking clarity (#181) and WISMO bot (#184): here, resolution when the parcel is truly lost.
Summary
Why treat the lost parcel as a separate case?
A lost package combines customer urgency, merchant cost, and carrier delays. Treating it as a simple delay multiplies follow-ups and errors.
Three hidden costs
Product + shipping: immediate replacement or refund
Agent time: 20-45 min per poorly managed case
Trust: 85% of buyers hesitate to buy again after a bad delivery experience (Ship Veho, cited EcomHint 2026)
Shipink recalls the golden rule: customer resolution and carrier claim are two separate processes. Never make the customer wait for the carrier investigation (Shipink, lost parcels 2026).
Kase estimates that 0.5 to 1% of shipments face issues (loss, breakage, theft), impacting margins by 1 to 3% once customer service and reshipment are included (Kase, porch piracy 2025).
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does it differ from WISMO and order tracking?
Four related contents, four levels of gravity.
Tracking Clarity (#181)
Clear tracking (#181) reduces follow-ups before an incident. The #202 comes into play when tracking is no longer enough.
WISMO Bot (#184)
Tracking Bot (#184) replies "in transit, delivery Thursday". The #202 covers blocked, lost, or delivered but not received statuses.
Address Errors (#201)
Address Prevention (#201) avoids upfront undeliverable mail. Here: package left with correct address but cannot be found.
Wrong Item Received
Wrong item (#177): the package has arrived, wrong content. The #202: package missing or cannot be found.
Promise #202
7-step procedure, proof matrix, message macros, DNR, carrier claim, refund/replace thresholds.
Which tracking statuses trigger a lost parcel procedure?
Codifying lost package triggers prevents each agent from improvising.
Scenario A: Stuck in transit
No tracking update for 3 business days (domestic FR) or 7 days (international). Status unchanged after promised delivery date. Action: open carrier investigation + inform customer of 5-10 business days delay.
Scenario B: Return to sender / Address unknown
Colissimo "returned to sender", "unknown address". Action: contact customer for address, reship or refund according to policy.
Scenario C: Delivered but not received (DNR)
Tracking "delivered" or "left in mailbox". Customer claims non-receipt. Wait 24-48 h (neighbor, building manager, delayed scan) then launch DNR procedure section 7.
Scenario D: Declared theft (porch piracy)
Delivered + photo proof of carrier drop-off but theft reported. Omnisend estimates ~30% of US households affected in 2025 (Omnisend, package theft 2025). Treat as DNR with reinforced evidence.
What is the 7-step internal procedure?
The after-sales lost package procedure consists of 7 reproducible steps in Gorgias or Notion.
Authenticate: order email, order #, name, shipping address
Read tracking: status, last scan, date, carrier, POD if available
Classify: A blocked, B NPA (Address Unknown), C DNR, D theft (section 3)
Communicate timeframe: Day 0 macro with status + dated next step
Collect evidence: according to section 5 scenarios
Resolve client: replace or refund based on section 9 thresholds
Carrier claim: in parallel, without blocking the client (section 8)
Helpdesk tags
lost_in_transit, dnr_delivered_not_received, npa_returned, carrier_claim_filed, lost_resolved_replace, lost_resolved_refund.
Internal SLA
First response < 4 business hours. Client resolution < 72 hours if case is qualified as lost. Ticket escalation to Tier 2 if AOV > €200 or repeat lost client.
What evidence should be requested depending on the scenario?
The collection of lost package evidence protects against fraud without humiliating the honest customer.
DNR (Delivered Not Received)
Declaration of honor : chat or email checkbox
Address verification : confirm number, door code, mailbox name
Neighbor/building manager inquiry : "Have you checked?"
Carrier claim : Colissimo/Chronopost inquiry number if required
Theft after delivery
Photo of delivery location if carrier provides POD. Online complaint filing if value > insurance threshold. Theft attestation for internal file (not always mandatory for B2C).
Lost in transit
Merchant side: tracking screenshot, purchase value invoice (not retail price for carrier claim), proof of shipping label. Sendcloud list: proof of shipment, POD, damage photos if applicable (Sendcloud, freight claims).
Simplified threshold
Order < €40 + high LTV customer: minimal evidence, immediate replacement. Order > €150 or 2nd DNR same address: complete process + fraud review.
What messages should be sent at each stage?
Consistent lost package macros reduce customer stress and agent time.
Day 0 Macro: inquiry opened
"Hello [First Name], we understand your concern regarding order #[X]. Tracking [carrier] [number]: status [STATUS] as of [date]. We are opening an inquiry with the carrier within 24 hours. Next update before [date+48h]. If the package cannot be found, we will offer you a replacement or refund according to your preference."
Day+2 Macro: carrier inquiry in progress
"Inquiry #[carrier ref] in progress. Carrier delay: 5 to 10 business days. We follow up daily and will keep you informed. Please confirm that the address [address] is correct and accessible."
Resolution Macro: replacement
"Package officially declared lost by [carrier]. We are shipping a replacement for order #[X] today at no charge. New tracking within 24 hours. We are sorry for this inconvenience."
Resolution Macro: refund
"Lost package confirmed. Refund of [amount] € to your initial payment method within 5 to 10 business days. Confirmation email sent."
What not to write
"It is not our fault, contact Colissimo directly." "We will refund when the carrier accepts." See actionable responses (#178).
How to handle the "delivered but not received" (DNR) case?
E-commerce DNR (Delivered Not Received) represents a growing share of lost parcel files.
5-step DNR process
Verify carrier POD: photo, signature, "left in parcel locker"
Request a 24-48 h wait + check with neighbors
Confirm exact address and instructions if applicable
Open carrier claim "disputed delivery"
After carrier delay (often 7-15 days) or if VIP customer: replace/refund
Pick-up point / locker
Check if parcel is awaiting collection at Mondial Relay or InPost locker. Macro: "Your parcel may be at the pick-up point [address]. Collection code: [X]. Collection deadline: [date]."
DNR Fraud
Signals: 3rd DNR same customer, identical address, high value, new account. Fraud escalation, reinforced evidence, no automatic replacement. See escalation matrix (#193).
How do I file a carrier claim without blocking the customer?
The lost parcel carrier claim is made in parallel with the customer resolution.
Standard carrier documents
Tracking number and shipping date
Purchase invoice (merchant cost, not retail)
Proof of deposit: post office scan or 3PL manifest
Incident description: dates, statuses, inquiry ref
Filing deadlines (check contract)
Colissimo / Chronopost: often 21 to 60 days after shipping. Shipink: claim day 20 = value; day 90 = often zero. Weekly ops calendar: review of all lost, unclaimed files.
Recover shipping + product
Request reimbursement for the value of the goods AND the shipping costs paid to the carrier. Internal log: deposit date, amount claimed, amount received, processing time.
What refund, replacement, and escalation thresholds should be applied?
Clear lost parcel resolution thresholds avoid ticket-by-ticket negotiation.
Typical DTC Grid
< €50: replacement or refund at customer's choice, without a lengthy investigation
€50-150: carrier investigation for 48-72 hours, then priority replacement
> €150: mandatory investigation, lead validation, signed declaration
VIP / top 10% LTV: immediate replacement, background investigation
Replacement vs Refund
Replacement if stock is available and customer is loyal (margin preserved). Refund if out of stock, customer prefers cash, or 2nd incident on the same order. Gift voucher: only if customer refuses replacement and policy allows it.
Insurance / Delivery Protection
If the customer purchased checkout protection (Extend, Corso, InsureShip), route to the insurer's process in parallel (InsureShip, claims 2026).
What support mistakes make lost packages worse?
Five lost package customer service errors turn a logistics incident into a relationship crisis.
Error 1: Resending the tracking link
Customer says "delivered but not received", agent sends the same link. Fix: acknowledge the problem, open a case.
Error 2: Conditioning refund on the carrier claim
Customer waits 3 weeks. Fix: resolve first, claim later.
Error 3: Forgetting the claim deadline
Investigation drags on, carrier window expires. Fix: weekly ops calendar.
Error 4: Messages with no return date
"We will get back to you" without a deadline. Fix: precise date for each macro.
Error 5: Treating DNR as systematic fraud
Refusal without investigation = public review. Fix: balanced process section 7.
How does Qstomy handle lost packages?
Qstomy refers to lost parcel files qualified before human escalation.
Lost parcel flows
Lookup live tracking: status + last scan + carrier
Auto classification: blocked, DNR, NPA according to section 3 rules
Proof collection: confirmed address, DNR declaration
File handoff: summary + tags + AOV for agent
Dynamic macro: personalized Day 0 message based on actual status
Quantified DTC Scenario
Accessories brand, 980 orders/month, 14 lost tickets/month, average resolution time 5.2 days, lost CSAT 3.1/5. Deployment of Qstomy lost flows + macros + section 9 thresholds. After 8 weeks: resolution time 1.8 days, lost CSAT 4.4/5, carrier claims filed 100% on time (vs 60% before), repeat contact lost -47%.
Explore AI customer support, Shopify integration, request a demo.
Which operational playbooks should be deployed in 30 days?
Playbook 1: map statuses (1 d)
Export 20 lost tickets 90 d. Classify A/B/C/D. Map Colissimo, Chronopost, DHL carrier statuses to scenarios.
Playbook 2: write macros (2 h)
4 section 6 macros in Gorgias. Agent training 30 min: never send only the tracking.
Playbook 3: threshold grid (1 h)
Document section 9 in Notion Support Policy. Validate automatic refund caps with finance.
Playbook 4: claims calendar (ongoing)
Monday review: lost cases without a filed claim. Goal: filing < 10 d after lost status qualification.
Playbook 5: KPI dashboard
Lost tickets/month, resolution time, lost CSAT, carrier recovery rate. Monthly ops + support review.
Useful links
A well-managed lost package can prove that your brand takes responsibility even when logistics go wrong.
Enzo
June 28, 2026
