Iterable on Oliver POS
Iterable's cross-channel campaigns include Oliver POS in-store purchases as native events through the WooCommerce + Iterable integration.
How Iterable works with Oliver POS for WooCommerce
Iterable is the cross-channel growth-marketing platform used by mid-market and enterprise consumer brands. Iterable's WooCommerce integration (native or via the Iterable API + a WooCommerce connector) pushes customers and orders into Iterable as users and events. Oliver POS writes counter sales into WooCommerce, and Iterable receives them — campaigns key off the same events, online or in store.
What Iterable pulls from WooCommerce
Iterable's data model centres on users, events, and catalog items. A typical WooCommerce + Iterable setup uses Iterable's server-side API (often via a connector or middleware) to push WooCommerce customers as Iterable users and WooCommerce orders as "purchase" events with line items and totals. Iterable's Studio (its journey builder) and its segmentation engine then operate on that data.
Why in-store sales matter for Iterable
Iterable customers are typically running cross-channel journeys — email, SMS, push, in-app, and web personalisation — orchestrated from one platform. The journeys are precise enough that missing in-store events causes immediate noise: SMS reminders to customers who just bought in store, win-back emails to regulars, push notifications to lapsed buyers who actually shop at the counter.
Push Oliver POS sales through the WooCommerce + Iterable pipeline and the cross-channel orchestration sharpens. Iterable's "purchased" events include in-store orders; journeys that branch on recent purchase, on cart abandonment vs. purchase, or on specific SKU activity behave correctly.
How the WooCommerce + Oliver + Iterable sync works
Cashier rings the sale, captures the customer, tenders. Oliver writes a WooCommerce order. The WooCommerce-to-Iterable connector (Iterable's official, a partner-built bridge, or a Zapier / Make pipeline depending on the merchant's stack) posts a purchase event to Iterable with the user identifier, order ID, items, total, and timestamp. Iterable journeys keyed off the purchase event fire immediately; segments referencing total spend or last purchase date refresh on the next evaluation.
Best fit for retailers who…
Iterable on Oliver POS is the right call for mid-market and enterprise consumer brands running heavy cross-channel marketing, for teams that prefer a journey-builder over a flow-builder, and for retailers where SMS, push, and in-app notifications need to be orchestrated alongside email. The WooCommerce + Oliver POS combination feeds Iterable the in-store events it needs to keep cross-channel orchestration honest.
What you get and how to set it up
Features Oliver surfaces from the Iterable plugin, plus the 4-step install most merchants run through.
Features at the register
- In-store sales flow into Iterable the moment a register sale closes
- Online and in-store customers share one WooCommerce profile and one segment list
- Real-time order, total-spend, and product-purchase data syncs to Iterable
- Cart, browse, and post-purchase automations fire on in-store orders too
- Cashier captures the customer email or phone at the register, with consent
- Same Iterable account, same lists, and same automations as your online store
Setup in 4 steps
- Install the Iterable for WooCommerce (via Iterable API + connector) on your WooCommerce site and connect your Iterable account
- Enable the customer and order sync inside Iterable and confirm the WooCommerce store is connected
- Install Oliver POS, sign in to the register, and confirm the customer-capture prompt is enabled at checkout
- Run a small live test sale at the counter and confirm the order, customer, and product purchases appear in Iterable within seconds
Common questions about Iterable on Oliver POS
Does Iterable have a native WooCommerce plugin?
Iterable's primary integration path is its server-side API, which works with WooCommerce via partner connectors or middleware (Zapier, Make, Segment, or a custom Node/PHP bridge). Either way, in-store sales from Oliver POS flow into WooCommerce first and then through that same connector into Iterable.
Can an Iterable journey send a push notification after an in-store sale?
Yes. Once the WooCommerce purchase event arrives in Iterable, any Iterable journey keyed off that event can send email, SMS, push, in-app, or any combination — the same way it would for an online order.
Does Oliver POS have a partnership with Iterable?
No. Oliver doesn't partner with Iterable or any other marketing platform. We support Iterable because its WooCommerce plugin already syncs customers and orders from your store — and Oliver writes every in-store sale into WooCommerce as a normal order, so the same plugin picks it up automatically. Your account, your data, and your contract stay between you and Iterable.
Does Oliver charge extra to use Iterable?
No. You pay Iterable's standard published pricing directly to Iterable. Oliver doesn't take a markup, doesn't insert itself into the data flow, and doesn't charge a per-contact or per-email fee on top.
Will in-store sales from the Oliver POS register show up in Iterable?
Yes — instantly. Every Oliver POS sale is written to WooCommerce as a standard order with the customer attached. The Iterable WooCommerce plugin treats that order the same way it treats an online order: it fires the same webhooks, updates the same customer profile, and triggers the same automations. There's no separate "POS sync" to configure.
How fast does a register sale reach Iterable?
Real-time. When the cashier closes a sale on the Oliver POS register, the WooCommerce order is created immediately, the Iterable plugin's webhook fires within seconds, and the customer's Iterable profile updates with the new order, total spend, and product purchases. The shopper can be on a post-purchase email flow before they've left the store.
Will my online and in-store customer profiles merge in Iterable?
Yes. Oliver POS attaches the WooCommerce customer to every register sale — either by looking up an existing customer by email or phone, or by creating a new WooCommerce customer at the counter. Iterable keys off the same WooCommerce customer ID, so a shopper who buys online on Monday and at the counter on Friday is one profile with one purchase history.
Read our full guide to Iterable on Oliver POS
A long-form walkthrough of running Iterable alongside the Oliver POS register on a WooCommerce store.