On Omnisend?

Omnisend ecom flows or SMS compliance off? We clear the backlog.

Omnisend is a solid ecom email and SMS platform right up until a cart-recovery automation stops firing on half your customers, a Shopify product-view trigger silently loses the referenced item, or the TCPA compliance review pauses an SMS campaign an hour before launch. We follow a real customer through the automation canvas and the sync, then tune segmentation and SMS consent so the next send actually reaches the inbox and the phone.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

omnisend.log

still broken

What it is

Omnisend at a glance

Omnisend is an ecommerce marketing platform founded in 2014 and headquartered in London, with a focus on Shopify, BigCommerce, WooCommerce and Wix. It combines email, SMS and web-push in one automation builder, with native integrations to the big ecommerce platforms and ecosystem tools like Judge.me, Loox and Smile.io.

DTC brands tend to pick it as a lower-cost alternative to Klaviyo. The automation builder covers welcome, cart-abandon, browse-abandon, post-purchase, win-back and transactional flows. SMS is a first-class channel with opt-in forms, segmentation and compliance support for US and international numbers.

Type
Ecommerce email, SMS and push platform
First released
2014
License
Proprietary, per-contact and per-SMS pricing
Maintained by
Omnisend Ltd.
Typically used for
DTC email flows, SMS marketing, cart recovery, post-purchase sequences

The honest version

Omnisend pros and cons

No technology is all upside. This is where Omnisend earns its place and where it tends to cause trouble.

Where Omnisend is strong

  • Ecommerce-shaped out of the boxAutomation templates for cart abandonment, browse abandonment, post-purchase and win-back are tuned for DTC rather than dressed up from a generic tool.
  • Email and SMS in one builderA journey can send an email, wait, then send an SMS in the same canvas, which removes the dual-tool coordination problem.
  • Lower cost than KlaviyoFor brands at the small and mid-market end, the per-contact pricing works out meaningfully cheaper, and the SMS costs are itemized predictably.
  • Shopify integration is directOrder, customer and product data arrive at the contact without needing a third-party sync. Flows can trigger on specific product or collection events.
  • Reasonable segmentationSegments can combine purchase, engagement and signup signals, and the preview counts update as you build, which is still not universal.
  • Reporting covers revenueAutomation and campaign reports attribute revenue in line with how ecom teams actually measure success, down to a single flow's contribution.

Where Omnisend bites

  • SMS compliance is yours to managePlatform guardrails catch the obvious issues, but TCPA, CTIA and carrier compliance for your specific brand is still on you. Mistakes can result in paused campaigns or carrier filtering.
  • Deliverability has shared-IP constraintsStandard plans use shared IPs, which means your sending reputation is partially linked to other senders. Dedicated IPs exist but add cost.
  • Deep segmentation gets slowCombining many purchase-history and engagement conditions on larger lists noticeably lags, and segment rebuilds after a bulk edit can take hours.
  • Reporting outside of revenue is lightCohort behavior, retention curves and attribution models are better served by exporting to a warehouse than by the built-in dashboards.
  • Non-Shopify integrations varyThe Shopify experience is smooth; BigCommerce and WooCommerce work well, while custom carts need API work to match.
  • Short-code throughput caps biteScheduled SMS sends above the allocated throughput queue up and deliver in windows, which affects time-sensitive campaigns.

Sound familiar?

Common Omnisend problems we fix

The Omnisend problems that bring people to us, and what you have once each one is fixed.

Automation step: condition returned null

A flow silently skips the wrong customers

A cart-total condition evaluating null because the customer entered the flow before the cart was captured, or a product-attribute filter looking at a field that is missing on some items.

Flow fires for the intended customers

SMS campaign paused: TCPA review

An SMS campaign is held for compliance review

Content that triggers carrier filters, a missing consent record for a segment of recipients, or a sender id change that needs re-approval by the carrier.

Campaign approved and delivering

Shopify sync behind by 3 hours

Order and customer data lag behind the store

A Shopify API version migration that silently dropped a webhook topic, or a sync paused by a rate-limit incident that never auto-resumed.

Store data current in Omnisend

Product-view trigger: product not found

Browse-abandon flows refer to a missing product

A product deleted or archived in Shopify while an abandoned browse was still held in the queue, leaving the automation unable to render the item card.

Browse-abandon handles archived products

Opt-in capture rejected

Signups appear in reports but not in flows

A double opt-in email that never got confirmed, often because it landed in the promotions tab on Gmail or was blocked by a carrier.

Opt-ins confirmed and entering flows

Campaign send failed: segment empty

A scheduled campaign fails because the segment is empty

A segment whose conditions no longer match any contact after a tag rename or a bulk unsubscribe, leaving the campaign without recipients at send time.

Segments populated at send time

Deliverability: complaint rate high

Complaint rate crosses the warning line

A re-engagement send to very old contacts, or a marketing campaign that reused a list purchased for a different context.

Complaint rate down, lists cleaned

Webflow form: field mapping missing

Signups from a form do not include phone number

A Webflow or landing page form where the phone field was never mapped on the Omnisend side, so SMS consent is captured but not stored.

Phone opt-ins land correctly

What we do

Omnisend help, from rescue to upkeep

Call us for one failing flow, or pass the whole email-and-SMS setup to our team.

Rescue
Flows stalled, SMS campaigns paused, or sync lagging behind the store. We stabilize the account first and write a short postmortem second.
Flow redesign
Welcome, cart, browse and post-purchase flows rebuilt with real conditions, named branches and reports a merchandiser can read.
SMS compliance
Opt-in forms, consent records, sender registration and content review handled so campaigns clear carrier filtering.
Segmentation and reporting
Segments rebuilt to match your merchandising plan, and revenue reports exported to Looker, BigQuery or Snowflake for cross-channel analysis.
Migration
Moves from Klaviyo, Mailchimp or an internal tool onto Omnisend, with flows mapped and historic events brought over cleanly.
Managed Tech
Monthly flow audits, sync health watchers, SMS throughput tracking and a US engineer on call when a flow misfires.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Omnisend alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Omnisend questions

Something else? Call+1 737 727 7327

Why is my Omnisend cart-abandon flow not firing on some customers?

The three common causes are cart data that arrives at Omnisend after the customer enters the flow, a condition on cart total or item count that evaluates null for a subset of carts, and a customer who was already unsubscribed from the specific message category. Walking a real customer through the automation history pins it down quickly.

How do we stay compliant with TCPA on Omnisend SMS?

The essentials are explicit consent captured at signup with the right disclosures, a stored record of when and how consent was given, honoring stop and help keywords automatically, and avoiding sending to numbers whose carrier has flagged the content category. We set up the opt-in flows and the record-keeping so a compliance review ends quickly.

Should we move from Klaviyo to Omnisend?

For brands at the small and mid-market end where Klaviyo's price is outpacing the value, yes. For large DTC operators with sophisticated predictive segmentation, product recommendations and deep CDP needs, Klaviyo still earns its premium. We walk through both before recommending a move.

Why is our Shopify sync lagging in Omnisend?

Usually a Shopify API version change that disabled a webhook topic, a sync paused during a rate-limit incident and never resumed, or a store with many apps writing to the same resources and generating event noise. Reconnecting the integration and backfilling the affected window generally catches it up.

Can we trigger Omnisend flows from a custom cart or app?

Yes. The REST API accepts events, contact updates and SMS consent, and the webhooks cover the responses most apps need. We build the event pipeline so custom carts and mobile apps trigger the same flows as the Shopify storefront does.

How much does Omnisend help cost?

The estimate is free of charge. Send us the store, the flows in question and the current numbers, and we come back with a price before any production change.

Free estimate

Omnisend giving you trouble?

Share the store, the flows in question and what customers are seeing, and a Hawkins.Tech engineer replies with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.