Customer.io on Oliver POS
Customer.io's behaviour-triggered campaigns include Oliver POS counter purchases as native events through the WooCommerce + Customer.io sync.
How Customer.io works with Oliver POS for WooCommerce
Customer.io is the messaging-automation platform built around an event-and-attribute data model. Its WooCommerce connector pushes orders as events into Customer.io. When Oliver POS rings a counter sale and WooCommerce records the order, Customer.io receives the event in real time — and any campaign listening for it fires the same way it would for an online order.
What Customer.io pulls from WooCommerce
Customer.io's data model is people, events, and attributes. The Customer.io WordPress + WooCommerce connector posts an event for every WooCommerce action (order placed, order completed, order refunded, customer created) and updates the person's attributes (total revenue, last order date, lifetime orders). From there, every campaign, workflow, and broadcast inside Customer.io can be triggered or segmented by those events and attributes.
Why in-store sales matter for Customer.io
Customer.io is bought by teams that want to move past template-driven email and into precise behavioural messaging. That model demands complete behavioural data. If a campaign is set to fire 7 days after the last purchase, it has to know about every purchase — including the ones rung at the counter on the Oliver POS register.
Push Oliver POS sales through the WooCommerce connector and Customer.io receives them as Order Placed events. Workflows triggered by recent orders, by total spend, by purchased SKU, or by any other order property fire correctly. The behavioural segments that drive the whole platform finally reflect the whole customer.
How the WooCommerce + Oliver + Customer.io sync works
Cashier rings the sale, captures the customer, tenders. Oliver writes a WooCommerce order. The Customer.io connector sees the order, posts an Order Placed event into Customer.io with the customer ID, order ID, items, and totals attached. Customer.io campaigns triggered by Order Placed (or by a follow-up Wait + Send block) fire immediately. The same applies to refunds via Order Refunded.
Best fit for retailers who…
Customer.io on Oliver POS is the right call for retailers running sophisticated lifecycle messaging, for in-house data and engineering teams that prefer an event-and-attribute model over a list-and-tag model, and for brands with multi-channel sends (email, SMS, push) that need one orchestration layer. The WooCommerce + Oliver POS combination feeds Customer.io the in-store half of the events it needs to do its job.
What you get and how to set it up
Features Oliver surfaces from the Customer.io plugin, plus the 4-step install most merchants run through.
Features at the register
- In-store sales flow into Customer.io 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 Customer.io
- 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 Customer.io account, same lists, and same automations as your online store
Setup in 4 steps
- Install the Customer.io WordPress + WooCommerce connector on your WooCommerce site and connect your Customer.io account
- Enable the customer and order sync inside Customer.io 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 Customer.io within seconds
Common questions about Customer.io on Oliver POS
Does Customer.io receive Oliver POS sales as real-time events?
Yes. The WooCommerce connector fires Customer.io events the moment WooCommerce records the order, which means the Order Placed event lands in Customer.io within seconds of the cashier closing the sale.
Can a Customer.io campaign send a follow-up SMS after an in-store purchase?
Yes — provided the customer has opted into SMS. The Order Placed event from Customer.io can trigger a campaign that sends SMS, email, push, or any combination, with arbitrary delays and branches.
Does Oliver POS have a partnership with Customer.io?
No. Oliver doesn't partner with Customer.io or any other marketing platform. We support Customer.io 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 Customer.io.
Does Oliver charge extra to use Customer.io?
No. You pay Customer.io's standard published pricing directly to Customer.io. 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 Customer.io?
Yes — instantly. Every Oliver POS sale is written to WooCommerce as a standard order with the customer attached. The Customer.io 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.
Will my online and in-store customer profiles merge in Customer.io?
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. Customer.io 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 Customer.io on Oliver POS
A long-form walkthrough of running Customer.io alongside the Oliver POS register on a WooCommerce store.