How many email automations should you run? The honest answer is not a neat number like five, 10, or 20. It is the number of automated customer journeys your business can support with clear triggers, genuinely useful messages, reliable data, and evidence that they create incremental value.

A recent Reddit discussion in r/Emailmarketing put that question into focus by highlighting Callie’s Hot Little Biscuit, a Charleston food brand reported to run more than 20 distinct automations. The example is compelling because two of its flows were based not on a standard browse or cart event, but on purchase count: customers who made a second purchase within a year were welcomed into a “Very Important Biscuiteer” status, while a third purchase unlocked free shipping. The strategic goal was straightforward: move customers beyond an average of two orders per year by recognizing momentum at exactly the right moment.

According to Klaviyo’s published case study, Callie’s launched loyalty-oriented flows in June 2023 and later reported 157.8% year-over-year growth in revenue attributed to flows, plus a 77.2% increase in flow placed-order rate. Those figures are worth studying—but not blindly copying. The more useful lesson is not “build 20 flows.” It is “find the customer moments where a specific, well-timed nudge can change behavior.” (klaviyo.com)

The 20-flow example: what Callie’s Hot Little Biscuit actually teaches

The Callie’s example has become attention-grabbing because it challenges the usual view of lifecycle marketing. Many ecommerce teams stop after implementing a welcome sequence, abandoned cart, post-purchase follow-up, and perhaps a win-back series. That foundation matters, but it can leave a substantial gap between what the brand knows about a customer and what its automated messaging actually does with that knowledge.

Callie’s approach was different. Rather than treating loyalty as a separate app, the brand used Shopify purchase data and Klaviyo flows to create progressive recognition and incentives. Its reported customer baseline was two purchases a year. That gave the team a concrete behavioral constraint to work on: what could encourage an existing customer to make one more purchase, sooner? (klaviyo.com)

Why purchase-count triggers are strategically interesting

A purchase-count trigger is not just another segment. It is a statement about where a person is in the relationship with the brand.

A first purchase can mean curiosity, a gift purchase, or a promotion-driven transaction. A second purchase is often a stronger signal: the customer came back after the initial experience. A third purchase is stronger still, because it begins to look like a repeat habit rather than a one-off decision.

That makes purchase milestones useful moments for messages such as:

Recognition: “You’re now one of our most loyal customers.”
Status: “You’ve unlocked an insider tier.”
Friction removal: free shipping, priority support, easier reordering, or early access.
Education: product combinations, storage guidance, replenishment reminders, or new use cases.
Advocacy: referral invitations or review requests after a successful repeat purchase.

The key is that the offer should fit the economics and the customer’s stage. A third-order free-shipping offer may make sense for a high-margin food brand with a repeat-purchase model. It may be a poor choice for a low-margin retailer, a brand with expensive fulfillment, or a business whose best customers already qualify for free shipping through normal cart thresholds.

The important distinction: distinct journeys, not duplicate emails

A healthy flow library contains distinct customer problems and business objectives. An unhealthy one contains the same “buy now” idea repeated across dozens of overlapping branches.

For example, a replenishment flow for customers approaching a normal consumption window is distinct from a win-back flow for customers who have become inactive. Both may target someone who has not ordered recently, but they answer different questions:

Is the customer likely to need the product again now?
Or has the customer drifted away and needs a reason to reconnect?

That difference affects timing, content, incentive levels, exclusions, and success metrics. The same principle applies to VIP recognition, review requests, back-in-stock notices, subscription recovery, referral prompts, and customer-service follow-ups.

Why the reported 157.8% result deserves scrutiny

The top reactions to the Reddit post were sensible. Commenters did not necessarily reject the case study; they challenged the leap from an attractive percentage to a causal conclusion. That is exactly how marketers should read vendor case studies.

One commenter questioned the precision of the 157.8% figure and asked whether the two purchase-count flows had been measured with a holdout group or a credible before-and-after design. Another pointed out that flow revenue can rise whenever a brand adds flows, which makes it risky to assign the whole increase to two particular automations. A third raised the base-rate question: percentage growth sounds dramatic, but moving from $4,000 to $10,000 is very different from adding six figures of contribution margin.

Those criticisms are not nitpicking. They identify the difference between attributed revenue and incremental revenue.

Attributed revenue is useful, but it is not proof of causality

Most email platforms attribute an order to a message when a customer clicks or opens within a defined conversion window. This is useful operationally: it helps teams see which messages are associated with downstream purchases. But it can overstate a message’s causal effect when the recipient was already likely to buy.

Klaviyo itself notes that attribution depends on configurable timing windows and that messages and channels can interact within those windows. In other words, a purchase can be associated with an email even when other influences—such as a paid ad, direct site visit, seasonal demand, a discount, or brand loyalty—also contributed. (help.klaviyo.com)

Consider a customer who was already planning to reorder biscuits for a holiday weekend. If they receive a “you’ve unlocked free shipping” email shortly before buying, the platform may attribute the purchase to the flow. That may be directionally correct, but it does not establish that the email created the purchase rather than merely appearing before it.

This does not make attribution useless. It means teams should use it as one layer of evidence, not the final verdict.

What stronger measurement looks like

The ideal test isolates the incremental effect of the automation. A randomized holdout group is the cleanest approach: some eligible people receive the flow while a small, comparable group does not. Compare revenue, order rate, margin, and customer outcomes between the two groups over a meaningful period.

Klaviyo’s global holdout functionality is built for this sort of question, although it requires at least 400,000 total profiles and recommends running for at least three months. That threshold will put the feature out of reach for many smaller brands, but the underlying discipline still applies: compare like with like, document timing, and resist declaring victory based on one dashboard number. (help.klaviyo.com)

For smaller businesses, practical alternatives include:

A flow-level randomized split: Send a control branch without an incentive or with a less aggressive message, then compare outcomes.
A phased rollout: Launch the automation for one eligible cohort or product category before expanding it.
A matched-cohort analysis: Compare recipients with similar historical purchase behavior to eligible non-recipients, while acknowledging the limitations.
Pre/post measurement with guardrails: Track results before and after launch, but adjust interpretation for seasonality, promotions, inventory changes, and acquisition mix.
Margin analysis: Measure gross profit after discount and shipping cost, not revenue alone.

The central question is not “Did this flow generate revenue in the dashboard?” It is “Did this flow cause enough additional profitable customer behavior to justify its cost, complexity, and inbox pressure?”

How many email automations should you run? Start with coverage, not a target number

There is no universal normal flow count because ecommerce businesses have different purchase cycles, product catalogs, margins, data quality, and customer expectations.

A single-product brand that sells a durable $500 item may need fewer automations than a consumables company with replenishment cycles, gifting seasons, subscriptions, local events, and multiple customer tiers. A B2B software company might require trial onboarding, activation, lifecycle education, product-usage alerts, renewal nurture, payment recovery, and expansion motions that have little resemblance to a direct-to-consumer store.

Instead of asking for a benchmark number, evaluate automation coverage across the customer lifecycle.

A practical maturity model for flow count

Stage 1: Essential coverage — roughly 4 to 7 flows

At this stage, the goal is to avoid obvious leakage. A lean ecommerce program often includes a welcome series, cart abandonment, browse abandonment, post-purchase education, review request, customer win-back, and transactional messages. Not every brand needs every one immediately, but these journeys address common high-intent moments.

Stage 2: Lifecycle depth — roughly 8 to 15 flows

The next layer uses actual customer behavior. Examples include product-specific replenishment, back-in-stock notifications, price-drop alerts, subscription dunning, first-to-second purchase nurture, cross-sell after a defined product purchase, VIP recognition, and seasonal gifting reminders.

Stage 3: Behavioral orchestration — 15 to 30+ flows

This is where a 20-flow program can make sense. The brand has sufficient volume, clean event data, clear customer patterns, and a team that can audit the system. Flows become more granular: category-level replenishment, high-value customer recovery, store-visit follow-up, education for complex products, customer anniversary moments, referral activation, local-market messaging, and loyalty triggers.

The count is not the maturity signal. The quality of the decision-making is. A brand with six well-measured automations can be more sophisticated than a brand with 25 unmaintained flows, conflicting discounts, and no suppression rules.

The core flows most brands should refuse to turn off

If a team had to rebuild from scratch, it should prioritize flows that respond to high-intent actions or protect essential customer experiences. These flows usually earn their place because they solve a customer need as well as a revenue objective.

1. Welcome series

A welcome flow reaches people at the moment they explicitly ask to hear from the brand. It should introduce the value proposition, set expectations, address common objections, and, where appropriate, offer a first-purchase incentive.

Do not treat it as only a discount delivery mechanism. A strong welcome series can explain hero products, social proof, shipping policies, product differentiation, founder story, and the best next action for a new subscriber.

2. Abandoned cart

Cart abandonment is a high-intent event, but it is also easy to mishandle. A good flow checks whether the person actually purchased before sending, uses a sensible delay, respects frequency caps, and avoids stacking unnecessary discounts.

Klaviyo’s current guidance still treats abandoned-cart messaging as a core automation category, alongside welcome, post-purchase, replenishment, and transactional flows. (help.klaviyo.com)

3. Post-purchase education

The first order is the beginning of retention, not the end of acquisition. Post-purchase automation can answer questions, reduce buyer’s remorse, help customers get better results from the product, and pave the way for a repeat order.

For food and consumables, this might include storage instructions, recipes, serving ideas, or a reminder of when to reorder. For skincare, it could explain a routine. For software, it should focus on activation and the first valuable outcome.

4. Replenishment or reorder reminder

This flow is particularly effective when the product has a predictable consumption cycle. The best timing should come from purchase data, not a generic 30-day delay copied from a template.

For example, if customers typically repurchase coffee every 28 to 40 days, a message at day 21 may be premature and a message at day 60 may be too late. Build around the distribution of real reorder intervals, then test the timing and message.

5. Win-back or lapse prevention

A win-back flow should target a customer who is overdue relative to their own expected purchase cycle. “Has not bought in 90 days” is only meaningful if 90 days reflects the category.

A mattress seller, a biscuit brand, and a cosmetics subscription business should not use identical inactivity definitions. Use product lifespan, historical reorder behavior, and customer value to determine when someone is truly at risk.

6. Transactional and service messages

Order confirmations, shipping updates, password resets, and other operational messages have a different job from marketing email. They must be dependable, timely, and easy to understand. If your product or commerce stack sends these events through an API, your team should treat the transactional email setup documentation as part of the customer experience—not as a technical afterthought.

The overlooked cost of adding more flows

Every additional automation creates a potential new revenue opportunity. It also creates operational debt.

That debt appears in subtle ways: customers receive two offers in one day, a VIP gets a generic “we miss you” coupon, an out-of-stock product is promoted in a cross-sell, an order-count flow fires after a refunded purchase, or an international customer receives a shipping benefit that cannot be fulfilled in their market.

More flows are only better when the system has governance.

The five failure modes of automation sprawl

Audience overlap: The same person qualifies for several flows at once, producing too much email or contradictory messages.
Incentive leakage: Discounts are offered to shoppers who would have bought anyway, reducing margin and training customers to wait.
Data fragility: Flows depend on incomplete catalog data, unreliable event tracking, or fields that no one maintains.
Content decay: Product details, policies, branding, links, and legal language become outdated after launch.
No clear owner: Nobody is accountable for reviewing performance, fixing errors, or deciding when a flow should be retired.

A useful operating principle is this: every live flow needs a named owner, a documented purpose, an entry condition, an exclusion strategy, a primary success metric, and a review date.

Build automations around moments of truth

The best automation opportunities are rarely found by browsing a platform’s flow template gallery. They are found by examining the friction, uncertainty, and motivation that customers experience before and after buying.

Start with the question: What changes in the customer’s situation that makes a message useful right now?

For Callie’s, the answer was a purchase milestone. The second order suggested a customer had begun to form a repeat relationship. That was a logical moment to introduce a named status. A third purchase was a logical moment to remove a known purchase barrier with free shipping.

Other brands may find different moments of truth:

A customer buys a camera but not a memory card.
A subscriber reaches a meaningful usage threshold in a software product.
A customer’s normal replenishment date is approaching.
A shopper has viewed the same product several times but has not added it to cart.
A subscriber’s payment fails.
A buyer receives an order and is likely ready to share a review or referral.
A customer places a gift order near the same seasonal date each year.

These moments create automation ideas that are behavior-led rather than template-led.

Use a simple opportunity score before building

Before launching a flow, score it from one to five on the following dimensions:

Customer value: Is the message genuinely helpful or relevant?
Intent strength: Does the trigger indicate a meaningful need or likelihood to act?
Reach: How many qualified people will enter the flow each month?
Economic upside: What is the likely incremental margin, not just attributed revenue?
Data confidence: Can the trigger and exclusions be trusted?
Operational complexity: Can the team maintain this flow without creating risk?

A flow with high intent but a tiny audience may still be worthwhile if it serves valuable customers. A flow with massive reach but weak relevance may damage engagement at scale. This framework helps prevent teams from building automation merely because the platform makes it easy.

A better way to measure flow performance

Revenue is important, but it should be one metric in a wider scorecard. A flow can have excellent revenue attribution while lowering long-term engagement, damaging margin, or cannibalizing future full-price orders.

The flow scorecard to review monthly

For each live automation, track:

Entrants and delivered messages
Conversion rate or placed-order rate
Revenue per recipient
Average order value
Gross margin after discounts, shipping subsidies, and variable costs
Unsubscribe and spam-complaint rates
Repeat-purchase rate for recipients
Time to next purchase
Incremental lift, where testing is possible
Flow conflicts or frequency-cap suppressions

The right primary metric depends on the journey. A review-request flow should not be judged only by direct revenue. A post-purchase education series may be valuable because it reduces returns or support tickets. A payment-recovery sequence may be measured by recovered recurring revenue. A VIP flow may be measured by higher annual value and retention.

Audit the denominator as carefully as the numerator

A common reporting error is celebrating a high conversion rate without checking whether the flow has enough volume to matter. Another is celebrating large attributed revenue while ignoring the cost of a 20% discount and free shipping.

Always ask:

How many people entered?
How many would probably have bought anyway?
What did the incentive cost?
Did the flow change the timing, frequency, or margin of purchases?
Did it create additional customer value or simply shift credit from another channel?

That last question matters especially when email, SMS, paid retargeting, and onsite personalization are all active. The customer sees one brand, not a collection of reporting channels.

How AI changes the flow-count conversation

AI tools make it easier to draft subject lines, generate message variants, summarize customer feedback, classify support tickets, suggest segments, and accelerate creative production. That can lower the production cost of adding automations.

But AI does not solve the harder problems: choosing a meaningful trigger, defining an ethical incentive, preventing audience overlap, validating data, and measuring incrementality. In fact, AI can make automation sprawl worse by making it cheap to produce more messages before a team has proven it needs them.

The productive role for AI is as an analyst and production assistant, not an excuse to automate every possible event. Use it to identify patterns in repeat behavior, generate hypotheses for testing, create content variants for approved flows, and flag inconsistencies during audits. Keep humans responsible for strategy, customer judgment, and measurement standards.

A 90-day plan for expanding your automation program

You do not need to jump from five flows to 20. A disciplined rollout creates better learning and avoids configuration mistakes.

Days 1 to 30: audit and repair the foundation

Inventory every live flow. Document its trigger, filters, delays, audience size, owner, incentive, monthly revenue, engagement, and known dependencies.

Then check for technical and customer-experience issues: broken links, stale promotions, duplicate sends, missing purchase exclusions, inventory conflicts, unsubscribed contacts, mobile rendering, and tracking gaps. Platform testing tools can help preview both individual messages and a profile’s path through a flow before a journey goes live. (help.klaviyo.com)

Days 31 to 60: launch one behavioral flow

Choose one automation based on a documented opportunity, not a generic best-practice list. For a consumables brand, that might be a smarter replenishment reminder. For a repeat-purchase store, it could be a first-to-second-order flow. For a high-AOV brand, it may be a post-purchase education series that reduces hesitation around complementary products.

Define a hypothesis in advance: “Customers who receive this message at day 45 will produce a higher 60-day repeat-order rate than comparable customers who do not.” Decide what result would justify keeping, changing, or retiring the flow.

Days 61 to 90: optimize and add guardrails

Review early performance, but do not overreact to a small sample. Improve timing, content, offer design, and eligibility rules based on the data.

Add a flow priority system and frequency caps so customers do not receive a welcome message, browse reminder, cart reminder, and win-back email in a compressed window. Once the first new behavioral flow is stable, identify the next highest-value moment of truth.

The real benchmark is confidence, not flow count

The Reddit discussion began with a provocative number: more than 20 automations. That number is useful because it prompts teams to look beyond the basic welcome-and-cart setup. But it becomes harmful if marketers interpret it as a quota.

Callie’s Hot Little Biscuit offers a better model than “more is more.” The brand reportedly connected a concrete customer pattern—two purchases a year—to a targeted loyalty hypothesis, then used purchase milestones to encourage another order. The result is a reminder that retention programs improve when they respond to behavior, not when they merely increase send volume. (klaviyo.com)

Build the flows your customers need. Measure whether they create profitable incremental behavior. Audit them often. And when a flow no longer has a clear job, turn it off without regret.

FAQ

How many email automations should a small ecommerce business have?

Most small ecommerce businesses should begin with four to seven essential flows: welcome, cart abandonment, post-purchase, transactional messaging, win-back, and—where relevant—browse abandonment or review requests. Add more only when you have a clear behavioral use case and reliable data.

Is 20 email automations too many?

Not necessarily. Twenty flows can be appropriate for a brand with multiple products, repeat-purchase behavior, enough customer volume, clean data, and strong lifecycle operations. It is too many if the flows overlap, go unmeasured, rely on stale content, or create excessive inbox frequency.

What is the most important automation after abandoned cart?

For many brands, post-purchase education is the highest-leverage next step because it improves the customer experience after the first sale and can support repeat purchase. Consumables brands should also prioritize replenishment reminders based on real reorder behavior.

How do you prove an email automation generated incremental revenue?

Use a randomized holdout or control group whenever possible, then compare order rate, revenue, and margin against recipients who did not receive the flow. If that is not feasible, use phased launches, matched cohorts, and careful pre/post analysis while accounting for seasonality and other marketing activity.

Should VIP flows always include a discount or free shipping?

No. VIP recognition can include early product access, exclusive education, faster support, gifts, community benefits, or personalized recommendations. The best reward depends on margin, customer preferences, and whether the benefit motivates profitable repeat behavior.

How Many Email Automations Should You Run? The Case for Fewer, Smarter Flows