When tracking says “delivered” and the customer says the parcel is missing, do not jump straight to either denial or refund: verify the carrier event, the delivery location, the address, the time window and the customer’s local checks, then escalate with a documented claim path.
The first 30 minutes after a missing-delivery ticket
Start by confirming the order number, shipping address and tracking number. Then look at the carrier’s own tracking page rather than relying only on a supplier dashboard. Record the delivery timestamp, scan description, city/postcode and any photo or location note.
Do not tell the customer that a delivered scan proves they received the parcel. It proves that the carrier recorded a delivery event. Your job is to find out whether the event matches the address and whether the parcel can still be recovered.
At the same time, do not issue an automatic refund solely because the customer writes “not received.” A consistent workflow protects legitimate customers and prevents avoidable losses.
Interrogate the carrier event
- Does the postcode or city match the order?
- Was the parcel left at a front door, parcel room, locker or neighbor?
- Is there a delivery photo, signature or GPS-supported event available to the merchant?
- Was the scan made before the stated delivery time window?
- Does the carrier recommend waiting until the end of the day because some scans appear before final drop-off?
- Can the merchant open a trace or proof-of-delivery request?
Capture what is available while the information is fresh. Carrier pages can change, links expire and supplier portals may overwrite status details.
Ask customer questions that can actually recover the parcel
A good message is specific and respectful. Ask the customer to check household members, building reception, safe places, parcel lockers and immediate neighbors if that is reasonable for the location. If tracking includes a delivery photo, share it through your normal support channel and ask whether the place looks familiar.
Avoid sending a giant checklist that sounds like you are trying to avoid responsibility. A short sequence works better: confirm address, identify the delivery clue, ask two or three local checks, then tell the customer exactly when you will update them.
If the parcel contains a time-sensitive item, raise the urgency. The right service decision for a $12 accessory is not necessarily the same as for a $600 product.
Escalate to the supplier and carrier in parallel
In dropshipping, the supplier may be the carrier’s contractual shipper, which means only the supplier can open certain claims. That is why your supplier agreement should define who opens a trace, how quickly they provide proof of delivery and how loss claims are credited.
Do not wait for this problem to discover that the supplier answers support emails once a week. Supplier economics and service quality should be considered together; a partner who looks cheap may not be cheap once claims and support are counted. This is one reason to read why supplier pricing can be misleading compared with marketplace prices through an operational lens.
Give the supplier a structured claim record: your order ID, their order ID, tracking, customer address, customer statement, delivery scan and requested action. Structured tickets get better answers than “customer says not received, please check.”
Refund, replace or wait: make the decision by policy
Create decision thresholds before the next ticket. A low-value item with weak proof may be cheaper to replace immediately. A high-value order may require a carrier investigation. A clear address mismatch usually points to a fulfillment error that should be escalated differently from a theft-after-delivery scenario.
Any decision must also comply with the laws and platform/payment rules that apply to your store. Internal risk policy does not override consumer rights.
Measure the cost of each resolution, but also measure repeat behavior. A store that approves every delivered-not-received claim instantly can attract abuse; a store that rejects every claim can lose legitimate customers and create payment disputes.
Build the evidence pack while handling the case
The ideal claim record contains the checkout address, order confirmation, supplier fulfillment record, carrier tracking, proof-of-delivery data, every customer message, your response timestamps and the final resolution.
That record should be exportable without rebuilding it after a dispute is filed. The article Dropshipping Chargebacks: Build the Evidence Pack Before the Dispute Happens explains the wider principle: evidence is strongest when it is collected during normal operations, not assembled from memory under a deadline.
If your payment provider starts reviewing the store after a rapid growth period, clean fulfillment evidence also helps you explain operations. See the related guide to Shopify Payments payout holds after scaling.
FAQ
How long should I ask the customer to wait?
Use the carrier’s documented guidance and the circumstances of the order rather than an arbitrary universal delay. Give the customer a specific next update time.
Does a delivery photo automatically defeat a claim?
No. It is evidence, not a complete conclusion. Check whether the photo matches the delivery location and consider the rest of the record.
Should I block a customer after one missing-delivery claim?
Usually not based on one event alone. Track patterns and use proportionate fraud controls rather than assuming every first claim is abuse.
admin
Author of practical guides to dropshipping, ecommerce, automation, and growing an online business.