Shopify Email Automation: Flow Architecture Built Around Your Customers
Shopify email automation is the set of messages your store sends on its own, triggered by what a subscriber or customer does: signing up, viewing a product, starting checkout, placing an order, or going quiet. Most stores have some of these flows. Few have them designed as one system, where each flow knows what the others are doing, discounts do not stack, and nobody receives three emails in a day because they browsed, carted and bought within an hour.
We design, build and audit that whole flow architecture for Shopify and Shopify Plus stores on Klaviyo and Omnisend. This page is about the architecture as a whole. It sits inside our wider Shopify email marketing service, which also covers campaigns, list growth and deliverability.
What flow architecture means
Flow architecture is the plan for every automated message in your account: which store event triggers each flow, who is allowed in, what they receive and when, how they exit, and which flow takes priority when a customer qualifies for several at once. It turns a collection of separate automations into a lifecycle journey that follows a customer from first visit to repeat purchase, and back again if they lapse.
Why individual flows are not enough
Templates make it easy to switch on a welcome series or a checkout recovery flow in an afternoon. The trouble starts when six or seven template flows run side by side without rules between them.
| Symptom in your account | What is going on underneath | The architectural fix |
|---|---|---|
| Customers get a browse email after they already bought | Browse abandonment has no filter for recent orders | Exit conditions based on Placed Order since flow start |
| New subscribers receive the welcome discount and a checkout discount together | Welcome and recovery flows both issue codes with no shared rule | One incentive policy across the map, with flow filters that check for active codes |
| Repeat buyers are treated like strangers | No split between first-time and returning customers | Conditional splits on order count in welcome, recovery and post-purchase flows |
| Flow revenue is flat despite list growth | Triggers firing on only part of the audience because onsite tracking or events are incomplete | Event and integration check before any content changes |
| High unsubscribe rate from automations | Too many messages per profile per week across flows | Frequency controls and a priority order between flows |
| Old flows still live with outdated products and policies | No review cycle after launch | A quarterly flow audit with content and logic refresh |
The core flow map for a Shopify store
Most stores need the same backbone. What changes between stores is the timing, content and branching inside each flow.
| Flow | Trigger from your store | Job it does |
|---|---|---|
| Welcome series | Subscribes through a form or at checkout | Introduces the brand and converts a subscriber into a first order |
| Browse abandonment | Viewed Product with no cart activity | Brings back product-level interest while it is fresh |
| Cart and checkout abandonment | Added to Cart or Started Checkout with no order | Recovers high-intent sessions |
| Post-purchase | Placed Order or Fulfilled Order | Sets expectations, teaches product use, and moves toward the second order |
| Replenishment | Time since a consumable product was ordered | Prompts reorder when the product is likely running out |
| Win-back | No order within your normal repurchase window | Re-engages customers before they are lost |
| Sunset | No opens or clicks over a long window | Confirms interest, then suppresses inactive profiles |
Stores with the right catalogue add back-in-stock, price drop, birthday or anniversary, and VIP tier flows on top.
Welcome series
The welcome series is the flow most subscribers see first and the one that shapes whether they read anything else. We split it by source: a subscriber from a discount popup needs the offer delivered and reinforced, while someone who joined through a blog guide or quiz needs content that continues the conversation. Useful articles from your Shopify blog content programme often make better welcome emails than another product grid. The series exits as soon as the first order is placed and hands the customer to the post-purchase path.
Browse abandonment
Browse abandonment catches people who looked at a product but did not add it to cart. It depends on onsite tracking identifying the visitor, which usually happens after they have clicked an email or filled in a form. We keep it short, filter out anyone who has entered checkout recovery, and set a minimum gap so a customer who browses daily does not get a daily email.
Cart and checkout abandonment
This is the highest-intent automation in the map, and it needs its own rules for timing, SMS follow-up and incentives. In the architecture we decide where it sits in the priority order and how it hands off to other flows. The full build is covered on our abandoned cart and checkout recovery page.
Post-purchase and replenishment
After the order, the flow map splits by first-time vs repeat buyer and often by product category. Order updates, product education, review requests and cross-sell timing are detailed on our post-purchase flow service page. Replenishment flows are timed from the product, not a fixed delay. To give an illustrative example, a 30-day supplement and a 90-day skincare refill need different triggers, so we store usage intervals per product or collection and time the reorder prompt from those values.
Win-back and sunset
Win-back picks up customers whose gap since their last order has run past your normal repurchase cycle. Sunset is different: it deals with subscribers who have stopped engaging with email at all, and it protects your sender reputation. Our win-back email service covers lapse definitions, RFM segments and offer strategy in depth.
The logic layer: triggers, filters, splits and frequency
Most of the value in an automation audit comes from the logic, not the copy. These are the controls we set on every flow.
Triggers
Flows start from one of four trigger types: a store event (Placed Order, Started Checkout, Viewed Product), joining a list, entering a segment, or a date such as a birthday or a predicted next order date. We check that each event is actually arriving from Shopify with the product and order properties the flow needs, because a flow can only be as good as the data that starts it.
Trigger filters and flow filters
Trigger filters decide who enters, for example only orders containing a certain collection, or only checkouts above a value. Flow filters are checked before every message and remove people whose situation has changed, such as anyone who has placed an order since starting the flow. Missing flow filters are the most common cause of customers receiving recovery emails after they already paid.
Conditional splits
Splits let one flow behave differently for different people: first-time vs repeat buyers, customers in different Shopify Markets who need another language or currency, VIP tags written by Shopify Flow, or shoppers whose cart contains a specific product type. They keep the number of flows manageable while still personalising the path.
Frequency controls and priority
Every profile has a limit on how much automated mail it should get in a short period. We use Klaviyo's Smart Sending or the equivalent settings in Omnisend where appropriate, add quiet hours for SMS, and set a clear priority order so checkout recovery beats browse abandonment, and post-purchase messages pause promotional campaigns for recent buyers when that suits the brand.
Email flows and Shopify Flow are different tools
Email flows message customers. Shopify Flow automates work inside Shopify Admin: tagging customers, flagging high-risk orders, alerting your team or updating products. The two meet in the middle, because a tag written by Shopify Flow, such as a VIP tier or a wholesale flag, can decide which branch of an email flow a customer follows. If you need those back-office rules built, our Shopify workflow automation service handles them, and we connect the output to your email segments.
Klaviyo and Omnisend: how we build on each
The architecture is the same on both platforms. The build details are not.
- Klaviyo: metric, list, segment, date and catalogue-based triggers, detailed flow filters, conditional and trigger splits, and predictive properties such as expected date of next order once your order history is large enough. Our Klaviyo agency service covers integration, audits and migrations.
- Omnisend: prebuilt ecommerce workflows with email, SMS and web push steps in the same workflow, conditional splits and exit conditions. See our Omnisend management for Shopify stores for setup and migrations.
If you are on Shopify Email, its built-in marketing automations cover the basics. When you need the branching and filtering described here, that is usually the signal to move to a dedicated platform.
Where automation sits in your sales funnel
Automated email only works on people who have already given you an email address or phone number, and every click still lands on your storefront. If the audit shows that visitors drop off on product pages or in checkout, better flows alone will not fix it. Our funnel optimisation work looks at the full path from landing page to purchase, so email is tuned alongside the pages it sends traffic to.
How a flow architecture project runs
Flow audit and baseline
We export every live and draft flow and score each one on trigger volume, revenue per recipient, placed order rate, unsubscribe rate and overlap with other flows. We check the Shopify integration and onsite tracking so we know which events are complete. You get the written flow audit, a map of the current architecture and the baseline figures. For a typical account this takes one to two weeks, longer when there are many flows or several connected stores.
Flow map and scope
We draw the target flow map: which flows to keep, rebuild, merge, add or retire, with triggers, filters, splits and priority rules written out. Work is ranked by expected impact, and the scope is fixed before the build begins.
Build in draft, test before live
New flows are built with every message set to draft or manual. We push test profiles through each branch, check that filters remove the right people and that discount codes generate correctly, and send you previews of each email. Nothing is switched live until you approve it.
Go live and monitor
Approved flows go live in a planned order so we can see each one's effect. Performance is tracked in your private client portal, with a monthly report and a monthly call to agree the next round of changes.
What better flow architecture influences
We do not promise numbers, because results depend on traffic, list size and product. These are the measures the work is designed to move:
- Share of email revenue coming from flows vs campaigns
- Revenue per recipient and placed order rate per flow
- Conversion of new subscribers to a first order
- Time between first and second order
- Unsubscribe and spam complaint rates from automated messages
- Fewer duplicate or conflicting messages per customer
Is this the right service
Flow architecture work suits you if your flows were set up from templates and never revisited, you are adding SMS and need it to fit alongside email, you have moved or are moving platforms, or you run several stores or Shopify Markets and your flows need localised branches. If you only need a single flow fixed, the dedicated recovery, post-purchase and win-back pages cover those builds.
Pricing
Email automation is part of our email marketing retainer, which is scoped to your list size and the number of flows and campaigns in the plan. A flow audit and rebuild is often the first phase of that retainer. See how services are priced on our pricing page, or book a free email flow audit and we will scope the work from what we find.
Frequently asked questions
Most stores need five to seven core flows: welcome, browse abandonment, cart and checkout recovery, post-purchase, win-back and sunset, plus replenishment for consumable products. More flows are not better by themselves. The right number is the set that covers each lifecycle stage without overlapping.
A flow is sent automatically when someone meets a trigger, such as placing an order. A campaign is a one-off send to a chosen segment on a scheduled date. Flows run all the time in the background, while campaigns carry launches, promotions and news.
Yes, and that is usually the better route. We keep flows that perform, rebuild logic where filters or splits are missing, refresh outdated content, and only retire flows that duplicate others.
No. We build changes as new drafts or cloned versions, test them, and switch over once approved. Customers already partway through an old flow can finish it, or be moved deliberately if the old version is causing problems.
Yes, where it fits. SMS steps are added to high-intent flows such as checkout recovery and shipping updates, only for profiles with SMS consent, and with frequency rules shared with email.
We recommend a light review every month through reporting and a fuller audit every quarter, or whenever you change products, pricing, shipping policy or discount strategy.
Related services
- Shopify email marketing retainerthe full lifecycle programme that this flow architecture sits inside.
- Checkout and cart recovery emailsthe deep build of the highest-intent flow in the map.
- Shopify Flow and Zapier workflowsback-office automations that feed tags and data into your email segments.
Get your flows audited
If your flows were built once and left to run, there is a good chance they overlap, miss key filters or send the wrong message to repeat buyers. Request a free Klaviyo or Omnisend flow audit and we will map what you have, show where it breaks and rank the fixes.