Which email flows should an online store set up first?

Start with welcome, abandoned checkout and post-purchase flows, then choose their build order from the gap your store needs to fill. Welcome serves new subscribers; checkout recovery serves reachable shoppers who have not bought; post-purchase serves buyers. Add replenishment, win-back or browse recovery when the product, audience and tracking support them. Verify entry and stop rules before sending.

A store collecting email signups without delivering its promised welcome has a different first job from a store whose buyers receive no help using their purchase. A template library can supply both flows. It cannot decide which gap you should close first.

Choose the customer moment you need to serve, check that you can identify and email those people, then build the smallest useful version. This guide makes that choice across flows; the linked explainers cover each flow in detail.

Which flows belong in the starting set?

Welcome, purchase recovery and post-purchase give you a starting set spanning signup, an unfinished purchase and a completed order. Email agency Flowium’s foundational-flow guide puts those categories in its high-priority group. Treat that as practitioner advice, rather than a promise that the same flow will earn the most for every store.

Use this table to choose the first gap to close:

This is a build-priority table, not a ranking of expected revenue. The reason to choose a flow is that it serves a real audience with a relevant message and reliable data.

Keep essential order and shipping messages working throughout. Klaviyo’s post-purchase setup guide recommends keeping those confirmations in separate transactional flows. A receipt answers whether an order went through; an additional marketing sequence should have its own job. See the post-purchase flow explainer for that distinction.

How should your store change the build order?

Start with welcome if signups are the unserved moment. Test the form through to the subscriber record and the promised email. Write the message around what the person signed up for. If the first-purchase offer no longer applies after an order, decide how the welcome path should change when that person buys. The welcome flow guide covers those trigger and audience choices.

Start with checkout recovery if you already have reachable unfinished checkouts and no working follow-up. Verify the event before writing the sequence. Klaviyo’s abandoned-cart documentation says its most common trigger is Started Checkout, whose firing point depends on the store integration. A flow called “abandoned cart” therefore does not necessarily reach everyone who added an item to a cart.

The distinction is explicit in Shopify’s automation documentation: product browsing, adding to cart without starting checkout, and starting checkout without completing an order have separate recovery templates. Decide which event you actually have. The abandoned-cart guide explains why the label can conceal different audiences.

Bring post-purchase forward if buyer guidance is the gap. Start with the useful next step for the purchased product, rather than an automatic request to buy something else. Decide whether the message belongs after the order, fulfillment or delivery. Agency Logical Position’s email-flow guide recommends sending its customer thank-you after the product is in the customer’s hands. That is a different clock from an immediate order confirmation.

Before adding any of these, inventory what already sends. Record the store’s built-in messages and every connected email app. Choose which system owns each job so the new flow does not duplicate an existing one.

When should you add replenishment, win-back and browse recovery?

Add them when you can name both the customer need and the information that makes the timing credible.

Replenishment belongs early for a suitable repeat-purchase product. Logical Position recommends prioritizing it for consumable or repeat-purchase products and using purchase data to estimate when customers may run low. You need the product and a plausible reorder interval, rather than a store-wide delay chosen because it looks tidy. The replenishment guide covers timing and the limits of a reminder.

Win-back needs a defensible definition of lapse. Shopify’s win-back template uses elapsed time since the last order. Before activating that logic, decide what “late to return” means for your products and past buyers. A new store without that history should not label customers inactive using an arbitrary delay. See win-back emails for the difference between a lapsed buyer and an unengaged subscriber.

Browse recovery needs a reliable handoff to later actions. A product-view reminder should stop being the relevant message when the shopper moves to a cart, checkout or purchase. Add it after you can test those transitions. The browse-abandonment explainer covers the audience; the overlap guide covers the stop rules.

Consider two illustrative stores whose core flows already work. A refill-skincare store with usable purchase histories can make replenishment its next project. A sofa store should not copy that routine refill reminder; it can first check whether its existing post-purchase guidance serves the buyer. The product and the unserved need change the next build, even when both stores have the same templates available.

What should you check before turning a flow on?

Write a short launch record for the selected flow: trigger, eligible audience, message job, timing and exit. Then test the paths, including the ones where no email should send.

The stop rule needs to work after entry, too. Klaviyo’s cart guide documents a Placed Order zero times since starting this flow filter, checked before each message. Entering a recovery flow does not itself mean the shopper still needs recovery at send time.

For the wider handoff, Klaviyo’s flow-audit checklist recommends excluding checkout starts and purchases from cart recovery, and cart additions, checkout starts and purchases from browse recovery. Confirm the corresponding events from your own integrations, including any separate checkout system.

Keep marketing eligibility explicit. The commerce platform sends marketing automations to subscribers by default, but offers an All customers setting for abandoned-checkout email. A setting is not a decision about permission. Resolve the consent question before changing the audience.

For a concrete draft-and-preview route in Shopify Messaging on desktop, go to Apps → Messaging → Automations → Create automation, select a template and edit the email. Recovery templates also ask for a channel. Use Send test and Save without turning on while preparing the message. A test email checks the message you receive; separately verify the event, audience and exclusion paths in the table.

Retain the test contact, event timestamps, expected result and observed result. Preview the email on mobile, check its product details and links, and confirm that another app is not sending the same reminder.

How much should you build before moving on?

Build enough to serve the selected moment correctly. Flowium’s bare-minimum recommendation is a single email in each core flow before extending the sequences. That is a useful starting constraint, not a requirement to limit every flow to one message.

After launch, inspect real entrants, sends and skips. A purchaser skipped from recovery can be the correct outcome; a missing purchase event is a setup defect. Confirm the distinction before adding more emails or treating a flow report as evidence of success.

Your next build should close another identifiable gap. If a flow cannot reliably recognize who should enter, what they need or when they should leave, fix that foundation before expanding it.

Frequently asked questions

Which email flow should a new online store build first?

Choose welcome when new subscribers are receiving no promised introduction or signup offer. Choose checkout recovery when you have reachable unfinished checkouts and verified purchase exclusions. Bring post-purchase forward when buyers lack useful product guidance. Welcome, recovery and post-purchase form a starting set; the unserved audience determines the order.

Are abandoned-cart and abandoned-checkout flows the same?

Check the trigger. Some abandoned-cart flows use a checkout-started event. Other systems distinguish adding to cart from starting checkout and provide separate automations. Use the event and its eligibility rules to identify who the flow can reach.

Should win-back come before replenishment?

There is no fixed order. For consumable or repeat-purchase products with usable purchase data, replenishment can be the next useful flow. Win-back needs a definition of lapse based on the product and buying history. Do not activate either using an arbitrary delay just to fill a template slot.

Does a post-purchase flow replace order confirmations?

Keep order and shipping confirmations working independently of the additional marketing sequence. A post-purchase marketing email should serve a separate need, such as useful product guidance, with an audience and timing appropriate to that message.