Email and Retention · focused work
Post-purchase email flows
The order confirmation is the most-opened message a store sends and usually the least thought about. The weeks after an order are where support load is decided, where a review is either earned or missed, and where the second purchase either happens sooner than it would have or does not happen at all.
This is the right work if
- The only message after an order is the platform's default receipt
- Review requests arrive while the parcel is still in transit
- Support answers the same setup, sizing and returns questions every week
- Consumable products have no reminder tied to how long they actually last
- Nobody has measured repeat purchase rate by the product a customer bought first
What it is
The sequences that follow an order
A complete post-purchase programme is several flows on different triggers, not one long sequence. Confirmation and shipping notifications, often left to the platform's defaults, carry high attention and should say something useful. A message timed to arrival helps the customer set up or use the product. A review request goes out once the item has been in use long enough to have an opinion about. A cross-sell suggests what genuinely goes with what was bought. A replenishment reminder reaches consumable buyers before they run out. A win-back reaches customers who have passed their normal gap between orders.
The difference between a programme that works and one that annoys is timing anchored to real events rather than to the order date, and content specific to the item purchased. A review request that arrives before delivery gets ignored at best. A replenishment reminder sent on a fixed monthly schedule reaches half the list too early. The measurement side is cohort based: group customers by the product they first bought, then read repeat purchase rate and time to the second order per cohort, because that tells the business which acquisitions are worth paying more for.
How it is done
The work, in order
What changes
- Every order begins a sequence instead of ending at a receipt
- Review requests arrive when the customer actually has the product
- Second orders come sooner because reminders match how long the product lasts
- The business knows which first purchase produces a returning customer
Decide who owns the transactional messages
Settle which notifications come from the platform and which from the email tool, then make each one carry something beyond the facts: care instructions, what happens next, or how to reach a person. Consistent sender, branding and tracking across all of them comes out of this decision.
Anchor timing to delivery
Connect shipment and delivery events so the arrival and review messages fire from what happened rather than from when the order was placed. Two orders placed the same day can arrive a week apart, and a fixed delay treats them identically.
Write what the product needs
Assembly, care, sizing adjustment, compatible accessories, the first thing to check if something looks wrong. Take the content straight from the questions that reach support for that product type, which is also how the flow starts reducing those tickets.
Ask for the review at first use
Time the request to when the customer has formed an opinion, which is days for some products and weeks for others. Ask about the specific item rather than the store in general, and give an easy route to support for anyone whose answer would be a complaint.
Build replenishment from real gaps
Measure the actual interval between first and second orders for each consumable, then send the reminder shortly before that interval closes. Where the product has a clear usage rate, say so in the message so the timing reads as helpful rather than as a sales prompt.
Read the results by cohort
Group customers by the first product they bought and track repeat rate, time to second order and value over the following year for each group. Acquisition decisions get much easier once the store knows which entry products produce customers who come back.
Platform notes
Shopify
Notification templates in the admin and flows in a connected email tool can both send after an order, so the split has to be decided explicitly or customers receive two versions of the same shipping update.
WooCommerce
Order status emails are triggered by status transitions, so a delivery-timed message depends on a shipping integration writing that status back, and the statuses used by the fulfilment plugin need mapping before the flow is built.
Should the receipt come from the store or from the email platform?
Either works. What matters is that one system owns it, that it is not sent twice, and that it reaches the inbox reliably, which usually favours whichever route has the better deliverability setup. Order confirmations are opened by nearly everyone, so it is worth putting real content in whichever version wins.
Do these messages need marketing consent?
Transactional messages about an order the customer placed sit on a different footing from promotional ones, but the boundary depends on jurisdiction and on how much selling the message does. Keep purely transactional content separate from offers, and take advice for the markets the store sells into rather than assuming one rule.
How do you avoid recommending something the customer already owns?
Feed purchase history into the flow and exclude previously bought items and their close substitutes. The most common failure is a cross-sell for the same product in a different colour sent to someone who bought both, which reads as though nobody is paying attention.
What if the product is bought once and never again?
Then the flow's job changes from repeat purchase to referral, reviews and accessories. A customer who will not rebuy can still recommend, review and add to the order, and measuring the programme on repeat rate alone would wrongly suggest it is failing.
Part of
Related work and answers
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.