Ecommerce Email Flows: Welcome, Basket, Post-Purchase
Which ecommerce email automations to build: welcome, abandoned basket, post-purchase and win-back flows. Order, timing and where to stop.
rabbitclip teamPublished: 7 min read
Short answer
An ecommerce email flow is a short series of automated emails sent when a customer does something specific. There are four core flows: a welcome flow for people who sign up, a basket flow for people who leave items behind, a post-purchase flow that informs buyers and prepares a second order, and a win-back flow for people who have gone quiet. They differ from a newsletter because they do not go to everyone at once; each person receives them at their own moment.
The value of a flow comes less from its volume than from its order. A shop that tries to build all four at once usually maintains none of them well. The sensible sequence starts closest to the point of highest intent: basket first, then post-purchase, then welcome, and win-back last.
This article is written for a small or mid-sized shop. It explains what each flow is for, how many emails it needs and where it should end. Consent and list building are a separate subject; here we deal only with design.
Which flow should you build first?
Start with the abandoned basket flow. The customer has chosen a product and perhaps reached checkout; something stopped them. Writing to that person is far more meaningful than writing to a stranger, because you already know what they wanted.
The post-purchase flow comes second. The customer has just trusted you with money, and their question is simply where the order is. These emails are read more than almost any other, because people are waiting for them. The welcome flow is third and win-back fourth.
This order is not a rule. If your site gains many new sign-ups each day but holds little basket data, the welcome flow can come first. The test is simple: begin where you have the most people and the clearest behavioural signal.
How many emails should a welcome flow have?
A welcome flow tells a new subscriber who the brand is, why it can be trusted and what to look at first. For most shops three emails are enough: the first goes out straight after sign-up with a short introduction and whatever was promised; the second follows a few days later with best sellers or the most common questions; the third arrives after about a week with delivery and returns reassurance and a gentle invitation to place a first order.
The most common mistake is putting a discount code in the first email and leaving the rest empty. A code alone builds no relationship; the person uses it and disappears. Trust should come before the offer.
- First email: who you are and what was promised at sign-up
- Second email: selected products or a short category guide
- Third email: delivery, returns and support reassurance, a calm invitation to a first order
- The person leaves the flow the moment they buy
When and how often should a basket reminder be sent?
In a basket flow, timing matters more than copy. The first email should go shortly after the basket is left, while the customer still remembers the product. Send it too early and the person is probably still on the page, so it feels intrusive; send it too late and the interest has faded.
The second email follows about a day later, usually with a photograph of the item and answers to likely questions: delivery time, returns, payment options. A third email is optional. Send it only if stock really is running low; invented urgency ends trust the moment a customer notices it.
Do not make a discount the opening move. What stops people is often not the price but the delivery charge, an unclear delivery date or doubt about payment. Remove the obstacle first, and keep the discount as a last resort, only if your margin allows it.
Why is the post-purchase flow the most neglected?
Most shops leave the order confirmation in the platform's default template and stop there. Yet the period after a purchase is when the relationship is most open. Confirmation, dispatch and delivery notices written in your brand's voice reinforce trust.
An email a few days after delivery can explain how to use or care for the product, and a review request can follow. The right moment to ask for a review is when the product has been tried, not when it arrived. Finally, a complementary product suggestion is fine, but only if it is genuinely related.
Do not hide returns and support information in this flow. A customer who finds the returns route easily will usually write to you before sending something back; one who cannot find it quietly leaves and does not return.
When does a win-back flow start, and when does it stop?
A win-back flow is for people who have not bought for a long time or have stopped opening your emails. The threshold depends on how often your product is bought: for something used monthly, silence means a few weeks; for something bought once a year, it means many months. Read the rhythm from your own order data, not from another shop's.
The flow has two or three emails. Begin with something useful rather than a plaintive message: new arrivals or a development they missed. Follow with an offer, and end with a polite goodbye and a question about preferences. Removing people who ignore that last email shrinks your list but protects your deliverability.
What mistakes are common in ecommerce email flows?
The commonest mistake is building flows and never opening them again. Prices change, products go out of stock, delivery times lengthen, and the copy keeps stating old facts. Once a quarter, live through every flow yourself: add a product to the basket, wait, and read what arrives.
The second is overlap. If one person receives a newsletter, a welcome email and a win-back email in the same week, they feel crowded and unsubscribe. A person should sit in one flow at a time; decide the order of priority in advance.
- Building flows and never testing them again
- Putting one person in several flows at once
- Adding a discount code to every email
- Leaving buyers inside the basket flow
- Using an image-heavy template that does not read well on a phone
When is an email flow the wrong choice?
For a shop with very few visitors, a handful of products or little chance of repeat purchase, elaborate flows are wasted effort. Writing good order and dispatch emails and setting up a single basket reminder is enough. You need enough people before four flows make sense.
Also, if product data, stock and order status do not flow reliably between systems, automation will send wrong information to hundreds of people. Fix the foundations first; flows are built on top of them. To check whether your domain is set up properly to send mail, you can use our email DNS checker.
Ecommerce email flows rest on four moments: basket, post-purchase, welcome and win-back. Begin where intent is highest, keep each flow short, never place one person in several flows at once, and test the whole thing yourself each quarter. If you would like to talk through which order suits your shop, you are welcome to arrange a discovery call with rabbitclip.
FAQ
What is the minimum number of email flows an online shop needs?
For a small shop, well-written order and dispatch emails plus one basket reminder flow make a good start. Add welcome and win-back flows once you have enough people on the list.
Should an abandoned basket email include a discount?
Not necessarily. What stops customers is often the delivery charge or an unclear delivery date, not the price. Answer those concerns first and keep the discount as a final step if your margin allows.
How long should a welcome flow run?
For most shops a week and three emails is enough. The person should leave the flow as soon as they make a purchase.
Who belongs in a win-back flow?
People who have not bought for longer than your product's normal buying rhythm and who have stopped opening your emails. Set the threshold from your own order data.
How often should flows be reviewed?
At least once a quarter. Prices, stock, delivery times and returns terms change, so go through each flow as a customer would and fix whatever has gone out of date.
