Customer.io WooCommerce POS — Oliver POS Integration Guide

Oliver POS doesn't have a partnership with Customer.io. It supports Customer.io because Customer.io's WordPress and WooCommerce connector already syncs people, events, and attributes from WooCommerce into Customer.io. Oliver writes every in-store sale into WooCommerce as a normal order, the connector posts the resulting Order Placed event to Customer.io, and every behaviour-triggered campaign keys off the unified data. Customer.io does the messaging automation. WooCommerce is the system of record. Oliver is the till on top.

What Customer.io is, exactly

Customer.io is the messaging-automation platform built around an event-and-attribute data model. The platform's data model is people, events, and attributes — every shopper has a Customer.io person record, every meaningful action (Order Placed, Cart Abandoned, Order Refunded, Page Viewed, Custom Event) is an event with arbitrary properties, and every campaign, workflow, and broadcast keys off those events and attributes.

Customer.io is bought by teams that want to move past template-driven email and into precise behavioural messaging across email, SMS, push, in-app, and webhook channels. The 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.

How Oliver POS feeds in-store sales into Customer.io

The Customer.io 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 consent.
3. The cashier takes payment through whatever WooCommerce payment gateway the store uses.
4. Oliver writes a standard WooCommerce order.
5. The Customer.io WordPress + WooCommerce connector sees the order, posts an Order Placed event into Customer.io with the customer ID, order ID, items, and totals attached.
6. 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.

The Customer.io WooCommerce connector — what Oliver rides on

Oliver rides on Customer.io's own WooCommerce connector — the integration that any Customer.io customer with a WooCommerce store would already be running. Setup follows Customer.io's standard documentation: install and configure the connector, point it at your Customer.io workspace, and let it post WooCommerce events as Customer.io events on a real-time basis.

Why pushing in-store sales into Customer.io matters

Customer.io campaigns are precise. The platform shines when workflows branch on properties that are accurate and current. With online-only data, the workflows are guessing. Push in-store sales through and the workflows sharpen:

• Workflows triggered by recent orders, by total spend, by purchased SKU, or by any other order property fire correctly.
• Behavioural segments that drive the whole platform reflect the whole customer.
• Cross-channel orchestration (email + SMS + push) reaches in-store buyers the same way it reaches online buyers.
• Webhook actions (e.g. notify Slack on a VIP purchase) fire on in-store sales too.

What this is NOT

Oliver POS is not a Customer.io partner. There's no co-marketing agreement, no revenue share, and no special pricing. Oliver doesn't insert itself between WooCommerce and Customer.io; the data path is the same one any WooCommerce store uses. Oliver doesn't charge a markup or per-message fee. Your Customer.io workspace is entirely between you and Customer.io.

Setup in 4 steps

1. Configure the Customer.io WordPress + WooCommerce connector and point it at your Customer.io workspace.
2. Verify Order Placed events arrive in Customer.io from a recent online order.
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 an Order Placed event appears on the matching Customer.io person within seconds.

FAQ

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, in-app, or any combination, with arbitrary delays and branches.

Does Oliver POS partner with Customer.io?

No. Customer.io is supported because its WooCommerce connector is the standard integration any Customer.io customer with a WooCommerce store would already be running.

Does Oliver charge extra to use Customer.io?

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

Will my online + in-store customers be one Customer.io person?

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

Try Oliver POS free for 30 days at /demo/ — bring your WooCommerce store and your Customer.io workspace and unify your behavioural data within an hour.