The best post-purchase emails do three things. They say what changed, what it means, and what happens next. They fire on real carrier events, not schedules, which is how they cut WISMO tickets instead of adding noise. That is it. This guide gives you four templates for the moments that matter most: shipped, delayed, delivered, and return started. Each one is short on purpose. A shipping update is not a newsletter. The delayed email is the one people get wrong, so we spend the most time there. Copy these, swap in your voice, and send them when a real event fires, not on a schedule.
The four emails at a glance
| Trigger (real event) | The job it does | |
|---|---|---|
| Shipped | First carrier movement scan | Confirms the promise, sets the arrival date |
| Delayed | Delay or exception scan | Owns the bad news before the customer notices |
| Delivered | Delivery confirmation scan | Closes the loop, opens the door to the next order |
| Return started | Return request created | Confirms the plan, keeps the exchange option alive |
What every post-purchase email needs
Every good post-purchase email answers three questions in order. What changed. What it means for me. What happens next. If your email covers those three things and nothing else, you are most of the way there.
Keep it short. These emails are utilities, not campaigns. The customer opened it to get one piece of information, so give it to them fast and let them close the tab.
Timing beats frequency. Send each email when a real event fires, not on a fixed clock. A shipped email that arrives before the package moves feels broken. Match each template to its trigger, and the emails feel like a service instead of clutter. Here is the map at a glance.
| Trigger event | Core message | |
|---|---|---|
| First carrier movement scan | Shipped | Your order is on its way, arriving around [date]. |
| Delay or exception scan | Delayed | Your order is running late. New estimate is [date]. Here is what we are doing. |
| Delivered scan confirmed | Delivered | Your order arrived. Here is what to do if anything is wrong. |
| Return request created | Return started | We got your return request. Here is your label and next steps. |
The shipped email template
The shipped email is your first real update, so make it feel good. The customer has been waiting since checkout, and this is proof things are moving.
Keep the subject clear and the body short. Lead with the fact, give an estimated arrival, and add one tracking link. That is enough.
Subject: Your [Brand] order is on its way
Hi [First name],
Good news. Your order [#1234] just shipped and is heading your way. You can expect it around [estimated delivery date].
Track your order: [tracking link]
We will let you know the moment it is out for delivery.
The delayed email template (the hard one)
This is the email most brands avoid, and that is exactly why it matters. A customer who hears about a delay from you trusts you more than one who finds out from an empty mailbox. Silence is what creates a support ticket, not the delay itself.
Get the structure right. Lead with the fact, not a paragraph of apology. Give a real updated estimate. Say what you are doing about it. Then offer an easy way to reach you if they need to.
Subject: A quick update on your [Brand] order
Hi [First name],
Your order [#1234] is running a little behind. The new estimated delivery date is [updated date].
Here is what happened: [one plain sentence, for example a carrier delay in transit]. We are keeping an eye on it and will update you the moment it moves.
If you need anything in the meantime, just reply to this email.
Send this the moment a delay scan is detected, not two days later. A delay should be a trigger, not something you review on Monday. For the wider approach, see how to reduce WISMO tickets.
The delivered email template
The delivered email closes the loop and opens the door to what comes next. It confirms the package arrived and gives the customer a path if something is wrong.
Keep it warm and short. Confirm delivery, then offer one clear next step, whether that is help with a problem or a gentle nudge to come back.
Subject: Your [Brand] order has arrived
Hi [First name],
Your order [#1234] was delivered. We hope you love it.
If anything is not right, you can start a return or reach us here: [support or returns link].
Thanks for shopping with us.
The return-started email template
A return is not a failure. It is a moment to keep the customer's trust. A clear, calm return-started email does that.
Confirm you received the request, give the label or next step, and set an expectation for what happens after. No guilt, no friction.
Subject: Your return is set up
Hi [First name],
We have started your return for order [#1234]. Here is your prepaid label: [label link].
Drop it off within [X days], and we will process your [refund or exchange] as soon as it reaches us. We will email you at each step.
Questions? Just reply here.
Which channel each of these goes through is its own decision. Detail and record suit email, urgency suits SMS. We break that down in email vs SMS for post-purchase.
The hard part is the trigger, not the copy
This is a live part of Pango, not a roadmap promise.
Templates only work if they fire at the right moment. Pango handles that by normalizing carrier data first. It maps the 10 to 115 statuses a carrier might send into clear milestones, so a shipped email fires on real first movement and a delivered email fires on a confirmed delivery. The delayed email is the important one. Pango turns a delay scan into a trigger, so your delay template can send before the customer notices the order is late.
You choose the delivery path. Pango sends through Klaviyo if that is your stack, or through its own email and SMS if you prefer to keep it in one place. The milestone triggers, the delay detection, and the return-started flow are all built and running today. Returns, exchanges, and claims are live parts of the platform, so the return-started email connects to a real returns flow, not a placeholder.
Custom triggers or branching logic, like flagging certain SKUs for a manual message instead of an automatic one, are build-to-fit. Pango reads your data and policies and builds that against your store, but it is scoped work, not a default setting. To see how this fits the wider product, visit order tracking. To tune the events behind each send, see proactive shipping notifications.
Editing the templates for your brand voice
These templates are a skeleton, not a finished voice. The structure is what does the work: what changed, what it means, what happens next. Keep that spine and change everything else.
Swap in your tone. A playful brand can loosen the shipped and delivered emails. A premium brand can keep them spare and calm. The delayed email is the one place to stay plain no matter your voice, because clarity beats cleverness when someone is worried about their order.
Test the subject lines and the timing, then leave the emails alone. Small, consistent, well-timed messages build more trust than a redesign every quarter.
The bottom line
Four short emails, each fired by a real event: that is the whole playbook. The hard part is the trigger, not the copy, because it requires normalized carrier data and a delay scan that actually reaches your email tool. Pango sends these messages automatically off live shipment events, through Klaviyo or its own email and SMS, on the same record that runs the delivery promise and the returns. See the post-purchase operations platform and book a demo.
