Iterable WooCommerce POS — Oliver POS Integration Guide

Oliver POS doesn't have a partnership with Iterable. It supports Iterable because Iterable's WooCommerce integration (via Iterable's server-side API plus a connector or middleware) already syncs customers and orders from WooCommerce into Iterable as users and events. Oliver writes every in-store sale into WooCommerce as a normal order, the connector posts the resulting purchase event into Iterable, and every cross-channel journey keys off the unified data. Iterable does the cross-channel orchestration. WooCommerce is the system of record. Oliver is the till on top.

What Iterable is, exactly

Iterable is the cross-channel growth-marketing platform used by mid-market and enterprise consumer brands. The platform orchestrates email, SMS, push, in-app, and web personalisation from a single Studio (journey builder), with segmentation that operates on users, events, and catalog items. Iterable's customers are typically running heavy lifecycle and onboarding programs where one tool needs to coordinate across many channels.

A typical WooCommerce + Iterable setup uses Iterable's server-side API (often via a connector, Segment, Zapier, or custom middleware) to push WooCommerce customers as Iterable users and WooCommerce orders as "purchase" events with line items and totals. Iterable's Studio and its segmentation engine then operate on that data.

How Oliver POS feeds in-store sales into Iterable

The Iterable WooCommerce POS flow inside Oliver:

1. The cashier rings the sale on the Oliver register and taps Charge.
2. Oliver prompts to attach a customer with marketing + SMS consent.
3. The cashier takes payment through whatever WooCommerce payment gateway the store uses.
4. Oliver writes a standard WooCommerce order.
5. The WooCommerce-to-Iterable connector posts a purchase event to Iterable with the user identifier, order ID, items, total, and timestamp.
6. Iterable journeys keyed off the purchase event fire immediately; segments referencing total spend or last purchase date refresh on the next evaluation.

The Iterable WooCommerce integration — what Oliver rides on

Iterable's primary integration path is its server-side API, which works with WooCommerce via partner connectors or middleware. The common patterns are:

• A dedicated WooCommerce → Iterable connector built by an Iterable solutions partner.
• Segment (or another CDP) with WooCommerce as a source and Iterable as a destination.
• A custom Node/PHP bridge that listens to WooCommerce webhooks and posts to Iterable's API.

Whichever pattern an Iterable customer uses, the data path is the same: WooCommerce is the source of truth, the integration layer pushes events to Iterable, and Iterable runs its journeys on the unified data. Oliver POS feeds the source by writing in-store sales as WooCommerce orders.

Why pushing in-store sales into Iterable matters

Iterable customers run cross-channel journeys — email, SMS, push, in-app, 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.

What this is NOT

Oliver POS is not an Iterable partner. There's no co-marketing agreement, no revenue share, and no special pricing. Oliver doesn't insert itself between WooCommerce and Iterable. Oliver doesn't charge a markup or per-message fee. Your Iterable workspace is entirely between you and Iterable.

Setup in 4 steps

1. Configure your WooCommerce → Iterable integration (via Iterable's partner connector, Segment, or custom middleware) and verify Order Placed events arrive in Iterable from a recent online order.
2. Map WooCommerce products to Iterable catalog items if your journeys depend on catalog-aware personalisation.
3. Install Oliver POS, sign in to the register, and confirm the customer-capture prompt with marketing + SMS consent is enabled at checkout.
4. Run a small live test sale at the counter and confirm the purchase event appears on the matching Iterable user within seconds.

FAQ

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 partner with Iterable?

No. Iterable is supported because WooCommerce + Iterable is a standard integration pattern any Iterable customer with a WooCommerce store would already be running.

Does Oliver charge extra to use Iterable?

No. Oliver's pricing is a flat monthly POS software fee. You pay Iterable directly.

Will my online + in-store customers be one Iterable user?

Yes. Iterable matches by email or by your configured user ID; Oliver POS attaches the WooCommerce customer to every register sale, so the shopper has one Iterable user spanning online and in-store activity.

Try Oliver POS free for 30 days at /demo/ — bring your WooCommerce store and your Iterable workspace and unify your cross-channel data within an hour.