Operations
How to Handle Late Shipping for Your Shopify Dropshipping Store
Your supplier is behind. The customer is emailing every 24 hours asking where their order is. You do not have a real update to give them. Late shipping is the most common operational crisis in Shopify dropshipping — and how you handle it determines whether you lose the customer or keep them. Here is the process we use when managing dropshipping inboxes.
Why late shipping destroys dropshipping stores that are not prepared
Most dropshipping stores have no written process for shipping delays. The founder handles each angry email differently, makes inconsistent promises, and either over-refunds or ignores customers until chargebacks arrive. A consistent delay response process prevents all three problems.
Step 1 — Contact your supplier before the customer contacts you
When you place an order with a supplier, set a reminder for the expected dispatch date. If it passes without a tracking update, chase the supplier immediately — before the customer notices.
What to ask your supplier:
- Confirmed dispatch date
- Tracking number and carrier
- Any batch delays affecting multiple orders
Getting ahead of the delay by even 24 hours gives you something to tell the customer instead of silence.
Step 2 — Send a proactive delay notification
If the order is more than two days past its estimated dispatch window, email the customer before they contact you. A proactive message reduces complaints by more than half.
Template:
"Hi [Name], I wanted to reach out personally about your order [#]. We are experiencing a short delay with dispatch — your order is now scheduled to ship by [date]. I apologise for the inconvenience and will send your tracking details as soon as they are available. Please reply to this email if you have any questions."
Step 3 — Handle the 'Where is my order' email without panicking
When a customer emails asking about a delayed order, your goal is to acknowledge, give a concrete date, and close the loop.
Do not:
- Promise a date you cannot confirm with the supplier
- Offer a refund immediately without checking if the customer wants to wait
- Go silent while you chase the supplier
Template for an active delay:
"Hi [Name], thank you for reaching out. Your order is currently with our supplier and is scheduled to dispatch by [date]. I will send your tracking details as soon as they are available. I appreciate your patience and am sorry for the wait."
Step 4 — Know when to refund vs. reship
If the delay passes the threshold your policy sets — typically 14 to 21 days for dropshipping — offer the customer a choice: wait with a confirmed new date, or receive a full refund.
Giving the customer the choice prevents most chargebacks. A customer who chooses to wait rarely files a dispute. A customer who chooses the refund is satisfied. The only customer who files a chargeback is the one who felt ignored.
How to write a supplier delay SOP for your support agent
If you outsource your support, your agent needs a written supplier delay SOP before this happens — not during. Your SOP should cover:
- The email address and response time SLA for each supplier
- The delay threshold before offering a refund
- The script for each stage: proactive notice, WISMO response, refund offer
- Who to escalate to if the supplier goes unresponsive
Frequently asked questions
- Am I liable if my supplier causes the delay?
- To your customer, yes. They bought from your store, not your supplier. Your refund policy applies regardless of the cause of the delay.
- Should I always offer a refund for late orders?
- Not automatically. Offer the customer a choice once the delay passes your policy threshold. Many customers prefer to wait once they have a confirmed new date.
- How do I handle a supplier who goes completely unresponsive?
- Refund the affected customers immediately and do not dispatch any new orders to that supplier until you have confirmation they can fulfil. Document everything in case of a payment dispute with the supplier.
Want to see how this would look for your brand?
We'll walk through your current support stack, ticket categories, and tooling — and show you what an operationalized version looks like inside Zendesk, Gorgias, or Help Scout.