The flow map
A store needs a small number of flows, and most of the value comes from having them all in place and triggered correctly rather than from any one of them being elaborate. The table is the map; the sections that follow take each group in turn.
| Flow | Trigger | Goal | Stage |
|---|---|---|---|
| Welcome | Email or SMS sign-up without a purchase | Introduce the store, set expectations, earn the first order | Consideration to first purchase |
| Abandoned cart | Items added to the basket, no order within a set time | Recover the order; remove the obstacle | Conversion |
| Abandoned browse | Product viewed by a known contact, no basket | Bring the shopper back to what they were considering | Consideration |
| Abandoned checkout | Checkout started, not completed | Recover the order; usually the highest-value abandonment | Conversion |
| Back-in-stock | Customer requested notification; stock returns | Convert pent-up demand immediately | Conversion |
| Price-drop | Price reduced on a saved or viewed item | Convert a shopper waiting on price | Conversion |
| Post-purchase | Order placed, then delivered | Reassure, help, request a review, show the next purchase | First purchase to repeat |
| Replenishment | Time since order approaches the product's re-order cycle | Prompt the re-order before the customer runs out or shops elsewhere | Repeat |
| Cross-sell | Purchase of a product with a known next purchase | Introduce the complementary item | Repeat |
| Win-back | No order for longer than the customer's usual gap | Bring a lapsing customer back | Retention |
| Sunset | No engagement across a long period | Reduce sending to protect deliverability; final attempt before suppression | Retention |
The stage column maps the flows onto the funnel: the abandonment flows work on conversion rate (CVRShare of visits or clicks that convert.) in the middle, and the later flows work on retention at the end. Transactional messages — order confirmations, dispatch and delivery notifications — are not marketing flows and are governed by different rules, though they are the most-opened messages a store sends, and the post-purchase flowAutomated messages that follow a customer from the order to a successful first use and towards a second order, alongside the order emails. should be designed around them rather than in competition with them.
Welcome and first purchase
The welcome flowThe automated sequence of emails sent to a new subscriber in the days after sign-up. is for people who have given the store their address but not their money. Its job is to turn interest into a first order, and it does that by setting expectations and removing doubt rather than by repeating the sign-up discount in every message. A good sequence introduces what the store sells and why, shows the products most new customers start with, answers the questions first-time buyers ask (delivery, returns, sizing, provenance), and delivers whatever incentive was promised at sign-up once, clearly, with its expiry.
The flow should stop when the person buys, and the first-purchase experience then takes over through the post-purchase flow. Welcome sequences that keep sending the sign-up offer to someone who has already ordered are the most common sign of a flow map built without exit conditions. The welcome series tutorial covers the message-by-message build; the store-specific design decisions are what to lead with (the best-selling first product, usually) and how the welcome ties into the loyalty programme's first reward.
Sign-up sources deserve attention here too. A pop-up offering a discount collects addresses from people who want a discount; a sign-up tied to something useful — size guides, restock alertsA message a shopper asked to receive when an unavailable item, size or colour returns, sent as soon as stock is live and with urgency only where it is true., a waiting list — collects people who want the products. The second group converts better and unsubscribes less, and the welcome flow can be tailored to the source.
Cart, browse and back-in-stock
The abandonment flows recover demand the store has already paid to attract. They are the highest-return flows in most stores and the ones most often set up badly.
Abandoned cartShare of shopping carts created that did not become an order. and checkout. The trigger is a basket or a started checkout with no order within a set time, and the first message should arrive while the intention is still warm — within hours rather than the next day — showing the exact items with a direct route back. Later messages can address the likely obstacle: delivery cost, sizing doubt, a question about returns. A discount in the first message teaches shoppers to abandon on purpose; if one is used at all it belongs late in the sequence and only for first-time customers. The abandoned cart flows tutorial covers the build, the timing options and the discount decision in detail. For abandoners the store cannot email, paid remarketing is the other route, and the comparison of abandoned cart emails and remarketing ads sets out how the two divide the work.
Abandoned browse. A known contact viewed a product, perhaps several times, and did not add it to the basket. This flow is lighter and lower-intent than cart recovery; one message showing what was viewed with related items, sent once per period rather than after every visit, is enough. Over-triggering browse abandonment makes the store look as though it is watching.
Back-in-stock and price-drop. These are the simplest and often the best-converting flows because the customer asked for them. The message should go out as soon as stock is live, with a direct link and a sense of urgency that is true, such as a genuinely limited quantity. Price-drop notifications on saved items work the same way for shoppers who were waiting on price. The tutorial on back-in-stock and price-drop alerts builds both, including who is told first when the restock is smaller than the queue.
The click-through (CTRShare of impressions that result in a click.) and conversion of these flows are the ones to watch most closely, because they are the earliest sign that something in the store has changed: a delivery charge added at checkout, a size guide removed, a stock problem.
Post-purchase and replenishment
The post-purchase flow begins when the order is placed and runs through delivery and first use. It is the flow with the greatest effect on lifetime value (LTVTotal value a customer brings over time.) and the one most stores reduce to a single review requestThe message or prompt that asks a customer to leave a review, sent once the product has been used and offered to every customer on the same terms..
A full sequence does several jobs in order. Before delivery: reassure and inform — what happens next, how to track it, what to do if something is wrong. On delivery: care and use instructions, especially for products that are easy to get wrong the first time. After a period of use: the review request, timed to when the customer has an opinion. Then the next purchase: the complementary item for what was bought, the loyalty balance and the distance to the first reward, and — for consumables — the beginning of the replenishment cycle. Each message should be specific to the product bought; a post-purchase flow that sends the same sequence regardless of product is a missed opportunity to be useful. The tutorial on building a post-purchase email flow builds this sequence step by step, triggered from delivery and kept clear of the order emails.
Replenishment flowsAutomated messages that remind a customer to re-order a consumable, timed to the product's re-order cycle from the store's own data, not a fixed delay. are timed to the product's re-order cycle rather than to a fixed delay. The cycle comes from order data — the median gap between consecutive orders of the same product — and the prompt lands slightly before it, when the customer is running low but has not yet bought elsewhere. For products with a predictable cycle, the replenishment message is also the natural place to offer a subscription. The repeat purchase and loyalty guide covers finding the replenishment and cross-category paths that these flows carry; this guide assumes those paths are known and sends them. Where the gaps have never been measured, the tutorial on finding what customers buy after their first order reads the median gap and its spread for each first product from the order history.
A skincare store maps its flows and finds the gaps
A skincare store with 60,000 contacts has a welcome flow, an abandoned cart flow with a 10% discount in the first message, and a review request 3 days after dispatch. Nothing else. An audit of order data shows the median re-order gap for its best-selling moisturiser is 47 days, that 22% of first-time customers return within 90 days, and that the cart flow's discount is used on 31% of recovered orders, including by repeat customers who have learned to wait for it. The team rebuilds the map: the discount moves to the third cart message and is restricted to first-time customers; the review request moves to 12 days after delivery; a post-purchase flow adds care instructions and a cross-sell to the matching serum; a replenishment flow fires at day 40 for the moisturiser; and a win-back flow starts at 95 days without an order. Over the following quarter, recovered-cart revenue falls by 8% but recovered-cart margin rises, the 90-day second-order rate climbs to 29%, and replenishment orders account for 14% of all repeat orders.
Win-back
The win-back flowMessages aimed at customers who have stopped buying or engaging, sent once they pass their usual gap between purchases. targets customers who have passed their usual re-order point without ordering. Its trigger should be relative — a multiple of the customer's own gap or of the category's typical cycle — rather than a fixed number of days applied to everyone, because a customer who buys monthly and one who buys yearly lapse on different clocks.
The sequence should start with a reason rather than a discount: what is new since the customer last ordered, what they bought and what goes with it, a reminder of a loyalty balance about to expire. An incentive can follow for customers who do not respond, sized to their past value. The sequence should end. Customers who ignore the whole win-back run should move into a sunset flow that reduces sending frequency and eventually suppresses them, which protects deliverability for everyone else and respects the fact that they have stopped wanting to hear from the store. The design of win-back — when lapse begins, what to offer whom — belongs to the loyalty guide; the flow here executes it.
Before the flow's offer becomes a fixture, the win-back offer experiment separates the value of the win-back message from the value of its discount, using a holdout and a message-only arm. If the flow is already live and few lapsed customers come back, the diagnosis for a win-back campaign that is not working reads the run against a holdout and separates reason, timing, exit, reach and ending faults.
Email or SMS for each flow
Email and SMS are not interchangeable. Email carries detail, images and several products; it is cheap per message and tolerated at higher frequency. SMS is read almost immediately, carries very little, costs more per message, and is tolerated rarely. Those properties decide the split.
SMS suits moments that are time-sensitive and simple: back-in-stock, a price drop, the first abandoned-checkout nudge, delivery-day information, a replenishment reminder with a one-tap re-order. It does not suit the welcome sequence, the post-purchase education, or anything that needs more than a sentence. Many stores use SMS as the first touch in an abandonment flow and email for the rest, or SMS for the single most urgent message in each flow and email for everything else.
Consent is the other half of the decision. SMS requires its own explicit consent in most markets, separately from email, and the consent has to say what the person is agreeing to receive. Frequency expectations are higher for SMS and unsubscribe handling has to work by reply. The SMS and WhatsApp automation guide covers the mechanics of messaging automation across channels; the decision for a store is to use SMS sparingly, for the messages a customer would want immediately, and to earn the consent honestly.
Governance and frequency
Flows run without anyone watching them, which is their strength and their risk. Governance is the set of rules that keeps them from colliding with each other and with campaigns.
Priority and suppression. When a customer qualifies for several flows at once — a replenishment prompt, a cross-sellOffering a customer a related product alongside the one they are buying; upselling offers a higher-value version instead. and a campaign on the same day — one rule decides which sends and which waits. Most stores give transactional messages absolute priority, then abandonment flows, then post-purchase, then campaigns, with a daily cap across all marketing messages per contact.
Exit conditions. Every flow needs a condition that stops it: a purchase ends the cart flow and the welcome flow, a re-order ends replenishment and win-back, an unsubscribe ends everything. Flows without exits send the wrong message at the wrong time and are the main source of embarrassing automations. The email automation flow launch checklist checks exits, the cap across flows and consent for each new email flow before it is switched on.
Consent and the rules. Direct marketing by email and SMS is regulated, and the direction is consistent across markets: consent that is specific and recorded, a working unsubscribe in every message, respect for the channel the person agreed to, and care with the existing-customer exceptions that some regimes allow for marketing similar products to recent buyers. The ICO's direct marketing guidance, linked in the sources, sets out the UK position in detail and is a useful general reference for the principles; this page describes the direction, not the legal position in any market.
Review cadence. Flows should be reviewed on a schedule — a monthly look at each flow's volume, click-through, conversion, revenue and unsubscribe rate, and a quarterly rebuild of anything that has drifted. A flow built years ago around products the store no longer sells is still sending. Order value (AOVAverage revenue per order.) by flow is worth tracking too, because the cross-sell and replenishment flows should move it and the discount-led cart flow often lowers it.
The retention hub sets these flows alongside the metrics and cohort view that show whether they are working.
To organise these flows into a managed programme, the lifecycle email programme playbook covers sequencing, ownership, testing and reporting across the whole customer lifecycle.
When the target is online orders, the email channel page for online sales sets out which of these flows to build first, how to cap campaign pressure and how to read revenue per recipientEmail-attributed revenue divided by the number of emails delivered. against a holdout.
Whether the cart email should carry an offer at all is settled by the abandoned cart discount experiment, which judges the incentive on margin per abandoner rather than recovered revenue.
Common mistakes
- Discount in the first cart message. Shoppers learn to abandon on purpose; move any incentive late and restrict it to first-time customers.
- One review request as the whole post-purchase flow. The flow with the biggest effect on lifetime value reduced to a single message.
- Fixed replenishment delays. The re-order cycle comes from order data per product, not from a default setting.
- Flows without exits. A welcome offer sent to someone who bought last week, a cart reminder for an item already ordered.
- SMS for everything. It is tolerated rarely and read immediately; spend it on the messages a customer would want now.
- Separate consent ignored. Email consent does not cover SMS; the channels need their own, and the message must match what was agreed.
- No daily cap across flows and campaigns. Customers who qualify for several things at once receive all of them on the same day.
- Never auditing. Flows drift as the catalogue changes; a monthly review and a quarterly rebuild keep them honest.
