Bloomreach WooCommerce POS — Oliver POS Integration Guide

Oliver POS doesn't have a partnership with Bloomreach. It supports Bloomreach (which absorbed Exponea) because the WooCommerce + Bloomreach integration already syncs customers, orders, and events from WooCommerce into Bloomreach Engagement. Oliver writes every in-store sale into WooCommerce as a normal order, the integration pushes the purchase event into Bloomreach, and every personalisation, recommendation, and lifecycle journey keys off the unified data. Bloomreach does the commerce-experience cloud. WooCommerce is the system of record. Oliver is the till on top.

What Bloomreach is, exactly

Bloomreach is the commerce-experience cloud combining customer-data, search-and-merchandising, and content tools. The Engagement half of the platform (the Exponea origin) is a customer-data platform plus omnichannel-orchestration tool — it ingests customer profiles, order events, product catalog data, and on-site behavioural events, then powers personalisation, segmentation, journey orchestration, and AI-driven recommendations across email, web, mobile, and in-store channels.

Bloomreach's value proposition is unified commerce experiences, which means in-store data isn't an afterthought — it's essential. Enterprise retailers running Bloomreach typically use it to bridge online and offline behaviour and trigger experiences that follow the customer across channels.

How Oliver POS feeds in-store sales into Bloomreach

The Bloomreach 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 Bloomreach connector (running as middleware or via Bloomreach's server-side ingestion API) sees the order, posts a purchase event into Bloomreach Engagement with the customer identifier, items, and totals, and updates the customer profile.
6. Journeys, segments, and recommendation models update immediately.

The Bloomreach + WooCommerce connector — what Oliver rides on

Oliver rides on whichever Bloomreach + WooCommerce integration the retailer already runs — typically a partner-built connector, a Segment-style CDP, or a custom integration layer that posts events to Bloomreach's server-side API. The pattern is consistent across enterprise integrations: WooCommerce is the source of truth, the integration layer pushes events to Bloomreach, and Bloomreach runs personalisation on the unified data.

Why pushing in-store sales into Bloomreach matters

WooCommerce + Oliver POS extends Bloomreach's unified-commerce capability to mid-market merchants without enterprise POS systems. Push Oliver POS sales through WooCommerce into Bloomreach Engagement and the unified profile becomes truly unified:

• Personalised email content reflects the products bought in store.
• Web personalisation on the next visit references the counter purchase.
• Recommendation models train on the full purchase data.
• Cross-channel journeys (email, SMS, push, on-site) follow the customer across channels with the right context.

What this is NOT

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

Setup in 4 steps

1. Configure your Bloomreach + WooCommerce integration (via partner connector, CDP, or custom middleware) and verify purchase events arrive in Bloomreach from a recent online order.
2. Push the WooCommerce product catalog into Bloomreach so personalisation and recommendation models have the catalog metadata they need.
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 Bloomreach customer within seconds.

FAQ

Does Bloomreach replace Algolia or WooCommerce's native search?

Bloomreach Discovery (the search-and-merchandising half of the platform) can replace WooCommerce's native search for the online store. Oliver POS doesn't use Bloomreach search at the counter — the in-store product lookup happens against the WooCommerce database directly — but Bloomreach Engagement still receives Oliver POS purchase events for personalisation and segmentation.

Can Bloomreach personalise the WooCommerce online store based on in-store activity?

Yes. Once Oliver POS sales reach Bloomreach Engagement, the customer's next online visit can be personalised based on what they bought in store — for example, surfacing complementary products or excluding categories the customer has already covered at the counter.

Does Oliver POS partner with Bloomreach?

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

Does Oliver charge extra to use Bloomreach?

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

Will my online + in-store customers be one Bloomreach customer?

Yes. Bloomreach matches by your configured identifier; Oliver POS attaches the WooCommerce customer to every register sale, so the shopper has one Bloomreach customer record spanning online and in-store activity.

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