Emarsys WooCommerce POS — Panduan Integrasi Oliver POS

Oliver POS doesn't have a partnership with Emarsys. It supports Emarsys (now part of SAP) because the WooCommerce + Emarsys connector already syncs customers, orders, and the product catalog from WooCommerce into Emarsys. Oliver writes every in-store sale into WooCommerce as a normal order, the connector pushes it into Emarsys, and the AI-driven Tactics — lifecycle, replenishment, win-back, recommendation — operate on the unified data. Emarsys does the omnichannel customer engagement. WooCommerce is the system of record. Oliver is the till on top.

What Emarsys is, exactly

Emarsys, now part of SAP, is an enterprise customer-engagement platform with pre-built "Tactics" tuned for retail — lifecycle programs, abandoned cart, replenishment, win-back, product recommendation. The platform is widely used by enterprise fashion, beauty, and lifestyle brands, and its strength is AI-driven personalisation across email, SMS, web, mobile, and ads with a unified customer profile.

The Emarsys + WooCommerce integration syncs contacts, orders, and product catalog data into the Emarsys platform via API connectors or middleware (typically Segment, MuleSoft, or a dedicated integration layer). The Tactics then operate on the synced data the same way they would for an enterprise retailer's own e-commerce platform.

How Oliver POS feeds in-store sales into Emarsys

The Emarsys 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 Emarsys connector (typically running as middleware or a dedicated integration layer) sees the order via WooCommerce hooks, pushes the contact and the order to Emarsys via its API, and updates the contact's lifecycle stage and engagement data.
6. Emarsys' AI programs run on the next evaluation cycle, with the in-store purchase folded into segmentation, recommendation, and lifecycle scoring.

The Emarsys + WooCommerce connector — what Oliver rides on

Oliver rides on whichever Emarsys + WooCommerce integration the retailer already runs. Enterprise integrations typically use middleware (Segment, MuleSoft, or a custom integration layer) rather than a single drop-in WordPress plugin. The pattern is consistent: WooCommerce is the source of truth, the integration layer pushes data to Emarsys, and Emarsys runs its programs on the unified data.

Why pushing in-store sales into Emarsys matters

Enterprise retailers running Emarsys typically take the majority of their revenue in physical stores. The AI Tactics that drive Emarsys' ROI — lifecycle, replenishment, recommendation — depend on a unified customer view that includes in-store activity. WooCommerce + Oliver POS gives smaller and mid-market retailers a path to that same unified view without the cost of an enterprise POS migration.

• Replenishment timers fire correctly because Emarsys knows about every purchase.
• Win-back exclusions exclude the right shoppers — including the regulars at the counter.
• Recommendation engines learn from in-store buying patterns alongside online.
• Smart Insight CDP aggregates in-store revenue into RFM and lifecycle segments.

What this is NOT

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

Setup in 4 steps

1. Configure your Emarsys + WooCommerce integration via your chosen middleware (Segment, MuleSoft, or a partner integration) and verify orders sync from WooCommerce to Emarsys.
2. Push the WooCommerce product catalog into Emarsys so Tactics that depend on catalog-aware personalisation have the data 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 contact and order reach Emarsys through the integration layer within the configured sync interval.

FAQ

Is there an official Emarsys plugin for WooCommerce?

Integration with Emarsys typically goes through middleware (Segment, MuleSoft, or a custom integration layer) rather than a single drop-in WordPress plugin. The pattern is consistent: WooCommerce is the source of truth, the integration layer pushes data to Emarsys, and Emarsys runs its programs on the unified data.

Does Emarsys' Smart Insight CDP get in-store revenue too?

Yes — once Oliver POS sales reach Emarsys through the WooCommerce sync, Smart Insight aggregates the in-store revenue into the same RFM and lifecycle segments it builds for online revenue.

Does Oliver POS partner with Emarsys?

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

Does Oliver charge extra to use Emarsys?

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

Will my online + in-store customers be one Emarsys contact?

Yes. Emarsys matches by your configured identifier (typically email); Oliver POS attaches the WooCommerce customer to every register sale, so the shopper has one Emarsys contact spanning online and in-store activity.

Try Oliver POS free for 30 days at /demo/ — bring your WooCommerce store and your Emarsys workspace and unify your enterprise customer view within an hour.