A shopper starts checkout at 9:40pm, gets distracted, and finishes the order the next morning from their phone. At 10:40 the same morning they receive “You left something behind”, followed by a text message with a discount code for the product they already bought. They now know the discount existed, and they paid full price.
Nobody misconfigured anything dramatic. The abandoned checkout workflow had no instruction to stop when an order arrived, and that one missing exit turned a happy full-price customer into an irritated one. A lot of our Omnisend work looks like this: the platform is capable, the event data is there, and a few settings decide whether customers get sensible messages or awkward ones.
How Omnisend sees your store
Omnisend is built for online stores on platforms like Shopify, WooCommerce and BigCommerce, and its automation is driven by store and messaging events. The events that matter most for lifecycle work are:
- Started checkout, added product to cart and viewed page or product, for intent
- Placed order, paid for order, ordered product, order fulfilled and order canceled, for purchase state
- Subscribed to marketing, for the start of the relationship
- Opened and clicked message, for engagement
Workflows can also start when a contact enters or exits a segment, and trigger filters let you narrow an event, for example only orders above a certain value or only a specific product. Inside the workflow, the event data is available to message blocks such as an order summary or the abandoned products.
That is the raw material. The design question is which customer state each event should change, and what should happen as a result.
- Started checkout
- Audience filter: opted in?
- Wait 1 hour
- Exit if order placed
- Email, then SMS if no click
The settings behind most problems
- Exit conditions. An exit condition cancels the workflow when a defined event happens. Any workflow that asks for a purchase, whether abandoned checkout, browse abandonment or a winback, should exit on an order. We still find accounts where none of them do.
- Frequency, meaning who can re-enter and when. Omnisend lets you control whether a contact can enter a workflow again, and within what window. Set it too loosely and a frequent browser gets the same “still thinking about it?” email every few days. Set it too tightly and a returning customer never sees a reminder again.
- Segment-based audience filters. Profile-based filters such as tags, country or custom fields are evaluated reliably at entry. Segment-based filters can lag behind the event that triggered the workflow, so a contact may be filtered out or exit before the segment has updated. Omnisend’s own guidance is to add a short delay when you rely on them. We prefer to avoid them where a profile filter will do.
None of these is complicated on its own. Together they explain a large share of “why did this customer get that?” questions.
Email, SMS and push in one workflow
The appeal of Omnisend is that one workflow can send an email, then an SMS, then a push notification, without stitching tools together. The detail to understand is that consent is per channel. A contact who enters a workflow but is not subscribed to SMS will be skipped at the SMS step, unless the message block is set to pass non-opted-in contacts to the next step.
That has real consequences. If your abandoned checkout relies on SMS as its second reminder and most of your list only consented to email, the workflow quietly does less than you think. We review channel opt-in rates, then design each workflow with the fallback path in mind. SMS also carries cost and stricter consent rules, so we use it where timing genuinely matters, not as a louder email.
Workflows live but results feel thin?
We will check triggers, exits, filters and channel settings across your Omnisend workflows and tell you what is misfiring.
Segmentation for retention, not just campaigns
Most Omnisend accounts we see segment campaigns well enough: VIPs, recent buyers, people who have not opened lately. Fewer use segments to drive the lifecycle itself. A customer who has bought twice is in a different state from a first-time buyer, and a customer whose usual reorder window has passed is in a different state again.
We define those states from order history, then use segment entry and exit to start and stop the right workflows. A first purchase starts a post-purchase series focused on product use rather than another sale. A second purchase moves the customer into a repeat-buyer path. Passing the expected reorder date without an order starts a gentle winback, which exits the moment an order comes in.
Beyond the abandoned cart
Cart and checkout recovery is where most stores start, and for good reason. Retention is where the longer-term revenue sits: welcome series that lead to a first order, post-purchase education, replenishment reminders, review requests after fulfillment rather than after order placement, and winback for lapsing customers.
If you are deciding between Omnisend and another platform, we will give you a straight comparison based on your data and team. Our ecommerce lifecycle work covers the same thinking across Klaviyo and other tools.
Why did a customer get an abandoned checkout email after ordering?
Usually because the workflow has no exit condition on order placed, or because the order arrived under a different email or phone number than the checkout. We check both.
Should we use SMS for every workflow?
No. SMS works best where timing matters, such as checkout recovery or shipping updates, and only for contacts who opted in. Using it for every message raises cost and opt-out rates.
How do we stop people receiving the same workflow over and over?
Set the workflow frequency so contacts can re-enter only after a sensible window, and add exit conditions. The right window depends on how often your customers browse and buy.
Can Omnisend use custom events from our own systems?
Yes, Omnisend accepts custom events through its API, which is useful for things like subscription renewals or loyalty milestones. We define what each event should carry before anyone builds it.
Are Omnisend’s pre-built workflows a good starting point?
Yes, as long as you treat them as drafts. Before switching one on, check its exit conditions, re-entry window, audience filters and which channels each step uses. The templates assume a generic store, and your reorder cycle and consent mix probably aren’t generic.