Email Marketing Automation Examples for Ecommerce: 15 Flows Worth Building

Most ecommerce brands already have automation.

What they usually do not have is:

• flows built around customer state
• correct timing
• sensible exit conditions
• product-level logic
• flows anyone has reviewed since launch

Automation is not a set-and-forget asset.

It is the part of your email program that runs every day without anyone watching it.

Here are the flows we think are worth building.

By Emiel Dingemans, Founder of Magicianly

The Order We Build Them In

For most established ecommerce brands:

First

Welcome, checkout abandonment, cart abandonment, post-purchase.

Second

Browse abandonment, replenishment or reorder, winback.

Third

VIP, cross-sell, review, back in stock, price drop.

Then

Segment-specific and subscription-specific lifecycle flows.

We explain the reasoning behind that sequence in which ecommerce email automations to prioritize.

1. Welcome Flow

Trigger: subscriber joins a list.

Job: turn a subscriber into a customer.

Useful content:

• brand reason for existing
• product guidance
• proof
• objection handling
• best sellers
• offer if you use one

This is the single highest-leverage flow for most brands. Examples live in welcome email examples.

2. Checkout Abandonment

Trigger: customer started checkout without purchasing.

Intent is high. Timing matters.

Useful content:

• reminder
• objection handling
• shipping or returns clarity
• support offer

Do not lead with a discount by default. Some customers were coming back anyway.

3. Cart Abandonment

Trigger: product added to cart without checkout.

Slightly lower intent than checkout abandonment. Message accordingly. Examples live in abandoned cart email examples.

4. Browse Abandonment

Trigger: customer viewed products without adding to cart.

Lower intent again. This flow works better as:

• education
• comparison
• proof
• product guidance

than as an urgent cart reminder.

5. Post-Purchase Flow

Trigger: order placed.

Job: reduce regret, increase usage and set up purchase #2.

Useful content:

• what happens next
• how to use the product
• what to expect
• support access
• brand story
• relevant next product later

Details in our ecommerce post-purchase flow guide.

6. Review Request

Trigger: enough time after delivery for the customer to form an opinion.

Timing depends on the product:

Fast-result products

Ask sooner.

Slow-result products

Ask later.

Asking before the customer has used the product produces weak reviews.

7. Replenishment / Reorder

Trigger: customer is approaching the expected reorder point.

Base the timing on actual consumption behavior, not a default 30-day timer. See replenishment emails.

8. Cross-Sell

Trigger: purchase of a specific product or category.

Good cross-sell logic uses:

• product affinity
• usage sequence
• customer need
• typical next purchase

Not: "here is our whole catalog."

9. Winback

Trigger: customer is meaningfully overdue relative to their buying cycle.

Examples in winback email examples.

10. VIP Flow

Trigger: customer crosses a value, frequency or order-count threshold.

Useful content:

• recognition
• early access
• exclusive products
• personal contact
• support

Your best customers should not receive only the same promotions as everyone.

11. Back in Stock

Trigger: a product the customer wanted becomes available.

Relevance is inherent. Keep it fast and simple.

This is often a good SMS candidate.

12. Price Drop

Trigger: a product the customer showed interest in decreases in price.

Use carefully. Frequent price-drop signals teach customers to wait.

13. Re-Engagement

Trigger: subscriber has stopped engaging.

Job: decide whether they still want the relationship.

This is a deliverability tool as much as a revenue tool. See our email deliverability checklist.

14. Quiz or Preference Follow-Up

Trigger: customer submits preference data.

Use the data. If a customer tells you their goal, concern or category:

• segment
• recommend
• educate
• merchandise accordingly

Collecting preference data and ignoring it is worse than not asking.

15. Subscription Lifecycle Flows

For subscription brands, add:

Onboarding

Get the customer to a successful first renewal.

Upcoming charge

Reduce surprise and failed payments.

Failed payment recovery

Recover involuntary churn.

Cancellation

Understand the reason and leave the door open.

Reactivation

Return later when the need returns.

See subscription onboarding and subscription cancellation emails.

Bonus Flow 1: Shipping and Delivery Education

For brands with long production or shipping windows, proactive updates reduce support load and cancellations.

This is retention work even though it looks like operations.

Bonus Flow 2: First-Time vs Repeat Customer Split

The same trigger can justify different messaging:

First-time customer

Needs reassurance and product education.

Repeat customer

Needs relevance, not the brand introduction.

Splitting on customer state is often more valuable than adding new flows.

Exit Conditions Matter

A flow should stop when it becomes wrong. Examples:

• cart flows exit on purchase
• winback exits on purchase
• replenishment exits on reorder
• subscription flows exit on cancellation or reactivation

Klaviyo documents flow filters and triggers in its flow triggers and filters documentation.

Watch for Flow Collisions

A customer can qualify for several flows at once. Common overlaps:

• welcome plus browse abandonment
• cart plus checkout abandonment
• post-purchase plus campaign promotions
• replenishment plus winback

Decide which message should win rather than letting the customer receive all of them.

Product-Level Logic Beats Generic Flows

One generic post-purchase flow for 400 SKUs is a compromise.

Where volume justifies it, split by:

• category
• product
• use case
• price band
• customer type

Flow Tests We Like

• delay timing
• discount vs no discount
• plain text vs designed
• number of emails
• product-specific vs generic
• objection-led vs product-led
• SMS added at a specific step
• customer-state splits

Test one meaningful change at a time and judge it on customer behavior, not the attributed number. See Klaviyo attribution.

A Note on AI Features

Klaviyo offers AI features that can assist with content and workflow tasks, documented in its AI documentation.

These can save time. They do not decide which flows your business needs, when a customer becomes late, or what your margin allows.

Review Flows on a Cadence

Flows send every day. Review them like a live asset:

Monthly

Performance, deliverability signals, obvious breakage.

Quarterly

Copy, offers, product references, timing, exit logic.

After any change

New products, pricing changes, shipping changes, platform migrations.

Our Verdict

The list of flows is not the hard part.

The hard part is:

triggering the right message at the moment the customer's state actually changes.

Most brands do not need twenty new flows. They need the eight that matter to be built around real behavior and reviewed regularly.