Every order-status reply is the same three-part move: acknowledge → specifics → what happens next, with a date. Customers asking about orders aren't looking for warmth — they're looking for evidence that someone competent is at the wheel. Specifics are the evidence; dates are the reassurance.
Here are twelve templates for the situations every store hits, grouped by when you send them. Swap the {placeholders}, keep the structure, and say them in your own voice — a template that sounds like a template defeats itself.
Proactive (you email first — each one prevents an inbound)
1. Order confirmed, with the timeline stated
Thanks for your order, {name}! Order {number} is confirmed. It ships within {processing window}, and delivery typically takes {transit window} after that — so expect it around {date range}. You'll get tracking the moment it leaves. Questions before then? Just reply.
2. Shipped
Good news, {name} — order {number} shipped today via {carrier}. Track it live here: {link}. Estimated arrival: {date}. If anything looks stuck along the way, reply here and we'll chase it for you.
3. Delay announcement (send the day you know)
{name}, an honest update: your order is running about {X days} behind the timeline we gave you — {one-sentence reason, e.g. "our supplier missed a component shipment"}. New expected delivery: {date}. We're sorry, and we'd rather tell you now than surprise you later. Nothing is needed from you; tracking still updates automatically.
4. Delivered
{name}, tracking shows your order arrived today. If it's not in your hands or something's off, reply within a few days and we'll sort it fast. Enjoy — and if it's what you hoped, we'd love to hear it.
Reactive: "where is my order?" (the WISMO set)
5. In transit, on time
Hi {name} — good news, it's moving! Order {number} shipped {date} via {carrier}, is currently {plain-words status, e.g. "at the regional facility two stops away"}, and is expected {day}. Live tracking: {link}. Anything else, just reply.
6. Label created but not moving yet
Hi {name} — your order left our hands {date}; the carrier's first scan sometimes lags a day or two behind pickup, which is why tracking looks frozen. If there's no movement by {date}, reply here and I'll open a trace with {carrier} directly — you won't have to chase anyone.
7. Stuck in customs
Hi {name} — your order reached {country} customs on {date}, and clearance is running {typical window}. This stage is out of the carrier's hands, but it almost always resolves on its own. I've set a reminder to check on {date} and I'll email you either way. If customs contacts you about a fee, that's normal for {country} — reply here if anything about it looks unclear.
8. Genuinely stalled — you escalate first
Hi {name} — I checked and you're right: no scans since {date}, which isn't normal. I've opened a trace with {carrier} today. Here's the plan: if it doesn't move by {date}, I'll {reship / refund} — your call which you'd prefer. Either way you'll hear from me by {date} at the latest.
Problems (the trust-deciding set)
9. Lost in transit
{name}, I'm calling it: the carrier's lost your parcel, and waiting longer isn't fair to you. I'm {reshipping today with expedited service / refunding you in full} — {tracking follows tonight / expect the refund in 3–5 business days}. I'm sorry it took this route; the replacement is our cost, not yours.
10. Arrived damaged
{name}, I'm sorry — that's not how it should have arrived. Could you reply with a photo of the item and the packaging? The moment I have it, I'll ship a replacement (no return dance needed). If you'd rather have a refund instead, say the word.
11. Delivered, but the customer doesn't have it
Hi {name} — frustrating, and more common than you'd think: "delivered" scans sometimes land hours early or at a neighbor's door. Could you check {porch/mailroom/neighbors} today? If it hasn't surfaced by {tomorrow/date}, reply and I'll {reship / refund} — you won't be left holding the carrier's mistake.
12. Wrong address (customer's error, your grace)
Hi {name} — the order's heading to {old address}, and once it's with the carrier we can't redirect it mid-flight. Here's what I can do: {"if it bounces back to us, we'll reship to the right address free" / "I've submitted a carrier redirect request — not guaranteed, but worth trying"}. For next time, the address on file updates at {link}. I'll keep an eye on the tracking with you.
The rules that make these work
- Never send reassurance without data. "It's on the way!" generates a follow-up in three days; template 5 with real tracking closes the thread. If pulling the data per email is the bottleneck, that's the part worth automating — it's exactly what our WISMO automation does: the draft arrives with carrier, status, and dates already filled from ShipStation or Shippo, and you just approve.
- Dates, not adverbs. "By Thursday" beats "soon," "ASAP," and "shortly" every time — even when Thursday is further away than you'd like.
- Own problems in the first sentence. Templates 9–12 work because they skip the defense and go straight to the plan. Blame — of carriers, suppliers, customs — reads as excuse even when accurate.
- Send the proactive set and the reactive set shrinks. Templates 1–4 are the prevention; we've mapped the full prevention stack in how to reduce "where is my order?" email.
Common questions
Should these be automated or sent by hand?
Templates 1–4 should be fully automated — your platform and carrier tools do them without thought. Templates 5–12 are judgment-adjacent: automate the drafting (data lookup and personalization are the slow part) and keep a human on the send button, so a stuck-in-customs reply never goes to a lost-parcel customer.
How much should I personalize?
The first line and the specifics — name, order details, dates. The structure can repeat forever; customers never compare their emails with each other, but they instantly feel a reply that answered a question they didn't ask.
What about angry versions of these questions?
Same specifics, faster clock, and one extra beat of acknowledgment up front. We wrote a separate playbook of de-escalation scripts — written for crowdfunding, but the structure ports to any furious inbox.
Steal all twelve. The templates are a starting point; the discipline — specifics and dates, acknowledgment before defense, proactive before reactive — is the actual product. Your customers can't see your tooling. They can see whether Thursday meant Thursday.