Email Triggers and Workflows for Ecommerce Automation

Email automation gets messy when the trigger is vague.

A flow called “cart abandonment” sounds simple until you start asking real questions. Did the person add to cart or start checkout? Are they already a customer? Did they buy after entering the flow? Did they abandon a product they already purchased yesterday? Should VIP customers get the same incentive as first-time shoppers?

Triggers and workflows answer those questions. They are the logic behind ecommerce automation.

In Omnisend’s analysis of 2025 activity across 150,000 brands, behavior-based automated emails generated 30% of email revenue from 2% of sends. Those messages performed out of proportion to their volume because they responded to a specific action. A trigger is what gives the email that context.

What an email trigger is

An email trigger is the condition that starts an automation.

In ecommerce, triggers usually come from customer behavior, store data, or timing rules. They tell your email platform when someone should enter a flow.

Common ecommerce triggers include:

• Subscribed to email
• Viewed a product
• Viewed a category
• Added item to cart
• Started checkout
• Placed an order
• Purchased a specific product
• Purchased from a specific category
• Has not purchased in a set number of days
• Joined a loyalty tier
• Requested a back-in-stock alert
• Is likely due for replenishment

The trigger should match the reason for the email. If the reason is weak, the flow will feel random.

Trigger vs. filter vs. segment

These terms often get blurred, but they do different jobs.

A trigger starts the workflow. A filter decides whether someone is allowed to enter or continue. A segment groups people based on shared traits or behavior.

For example, “started checkout” might be the trigger for a checkout abandonment flow. “Has not placed order since starting this flow” might be a filter. “VIP customers” might be a segment that gets a different branch.

Logic type	Question it answers	Example
Trigger	What starts the flow?	Started checkout
Filter	Should this person enter or stay in?	Has not purchased since starting checkout
Segment	What group does this person belong to?	First-time buyer, VIP, discount-sensitive, lapsed

When those pieces are clear, automation becomes easier to control.

What a workflow is

A workflow is the path someone follows after entering an automation.

It can include emails, wait times, splits, filters, updates, tags, suppression rules, and exit conditions. A simple workflow might send three emails with delays between them. A more advanced workflow might branch based on product type, customer value, engagement, or purchase behavior.

The workflow is not just the email copy. It is the decision system around the copy.

The basic workflow structure

Most ecommerce workflows include the same building blocks: entry trigger, entry filter, delay, email, behavior check, another delay or split, and an exit.

A simple cart workflow might look like this:

1. Trigger: customer starts checkout.
2. Filter: customer is subscribed and has not purchased.
3. Wait: one hour.
4. Email 1: reminder with cart items.
5. Check: did customer purchase?
6. Wait: 24 hours.
7. Email 2: reviews, shipping, returns, or objection handling.
8. Check: did customer purchase?
9. Wait: 48 hours.
10. Email 3: final nudge or incentive.
11. Exit.

That structure is easy to understand because every step has a job.

Now picture the person behind it. Jordan starts checkout on a train, loses signal, and finishes the order from a laptop that evening. The one-hour reminder may be useful; emails two and three are not. The purchase check is not technical housekeeping. It is what keeps a helpful nudge from becoming an irritating one.

Entry rules

Entry rules protect relevance.

For a welcome flow, you may want new subscribers who have not purchased yet. Existing customers who join the newsletter may need a different welcome path.

For a cart flow, you may want shoppers who started checkout but did not buy. You may exclude customers who already received a cart email in the last few days.

For a winback flow, you may want customers who have not purchased in 120 days, but you may exclude recent support complaints or people already in a replenishment flow.

The goal is not to make rules complicated. The goal is to avoid sending emails that make no sense.

Delays

Delays determine how long the workflow waits before taking the next step.

Timing should reflect intent. A welcome email should usually send immediately because the subscriber expects something. A cart reminder often works best close to abandonment because the purchase is still fresh. A post-purchase education email may need to wait until the product ships or arrives. A replenishment reminder should line up with expected product usage.

Do not use the same delay pattern for every flow. The customer’s situation should decide the timing.

This applies especially to replenishment. A generic 30, 60, or 90-day window is easy to configure, but the right timing is usually specific to the product category and sometimes the exact SKU. Pull order history and use the real median repurchase window rather than a round number. Get it wrong and the email lands while the customer still has product left, or after they have already reordered somewhere else. Review requests have the same problem: too early and the customer has not used the product; too late and the experience is no longer fresh.

Conditional splits

A conditional split sends people down different paths based on behavior or data.

Useful ecommerce splits include:

• New customer vs. returning customer.
• Purchased vs. did not purchase.
• High cart value vs. low cart value.
• Product category viewed or purchased.
• VIP vs. standard customer.
• Clicked vs. did not click.
• Discount used vs. no discount used.
• Domestic vs. international shipping.

Splits are useful when the message should actually change. Do not branch just because the software makes it possible.

One split worth building early, even though it’s easy to skip is the order count split. A post-purchase sequence for a first-time buyer should look different from one for someone on their third order, since the first-timer needs reassurance and product education while the repeat customer already trusts the brand and responds better to relevance and recognition. It’s a structural decision worth making before you write any copy, not a refinement to add later.

Exit rules

Exit rules are where many automations fail.

If a customer buys, they should leave the abandonment flow. If they unsubscribe, they should stop receiving marketing emails. If they enter a higher-priority flow, they may need to leave a lower-priority one. If they no longer meet the conditions that made the email relevant, the workflow should stop.

Good exit rules prevent awkward emails like:

• “Complete your purchase” after the customer already bought.
• A discount after the customer paid full price.
• A winback offer to someone who ordered yesterday.
• A browse reminder for a product that is now out of stock.

Automation should feel attentive. Bad exit rules make it feel careless.

Suppression and frequency caps

Suppression rules prevent certain people from receiving certain emails. Frequency caps limit how often a person can receive marketing messages.

Controls like these matter because customers can qualify for multiple flows at once.

Someone could browse a product, add to cart, receive a campaign, and qualify for a winback sequence in the same week if the account logic is sloppy. That does not mean they should receive every email.

This is one of the most common gaps agency marketers flag when reviewing an ecommerce account for the first time. Not a missing flow, but no plan for what happens when several flows qualify a contact at once. A shopper can land in browse abandonment, then trigger the cart flow, then enter a post-purchase sequence, all inside the same week, with no flow deferring to another. The fix is a global frequency cap that applies across every automation, not just within each flow individually, plus a clear priority order for which flow wins when two trigger at the same time. Someone actively in a cart-recovery sequence, for example, generally shouldn’t also be getting a browse abandonment email for the same product.

A practical hierarchy might prioritize checkout abandonment over browse abandonment, post-purchase over promotional campaigns, and transactional messages over marketing messages.

Automation also cannot repair every problem by itself. Nadeef Bidet’s founder noticed that shoppers were dropping out when they reached shipping options. His recovery emails converted roughly 5-10% in typical months, but direct conversations revealed the questions customers were struggling with; in his best month, the automated emails reached a 20% recovery rate. His account of the process is a useful warning: when a workflow underperforms, inspect the customer experience that created the trigger instead of endlessly rewriting the subject line.

The bottom line

Triggers decide when automation starts. Workflows decide what happens next.

For ecommerce, the strongest flows are built from clear behavior, sensible timing, useful branching, and strict exit rules. That is how automation stops feeling like a generic drip campaign and starts feeling like a relevant response to what the customer is doing.