Centerpiece commerce

Choose an integration path

Keep one Centerpiece customer experience while adapting installation, credentials, and order operations to the retailer's commerce stack.

Customer experienceShared components

Browser authorityConfig + rate only

Server authorityLead creation

Insurance paymentCenterpiece domain

Same journey, different delivery model

The distinction is operational: who installs the experience, owns credentials, observes order events, and runs recovery jobs.

Managed adapter

WooCommerce plugin

A private WordPress plugin connects WooCommerce checkout and order events to Centerpiece with minimal retailer application code.

WooCommerce checkout WordPress proxy Centerpiece API

Install: Private plugin ZIP and WordPress configuration
Credentials: Partner secret stored in protected WordPress options
Order lifecycle: WooCommerce hooks, order metadata, and HPOS support
Retries: Action Scheduler and periodic reconciliation
Retailer owns: Plugin installation, catalog mapping, and staging approval

Read the WooCommerce guide

Composable integration

React and headless

Shared React components connect to a retailer-owned server layer that maps authoritative cart, customer, and order data.

React storefront Retailer server Centerpiece API

Install: Commerce React package plus server SDK or REST
Credentials: Partner secret stored in the retailer server environment
Order lifecycle: Retailer APIs, webhooks, or platform-specific events
Retries: Retailer-owned jobs, observability, and reconciliation
Retailer owns: Component mounting, server mapping, and operational recovery

Read the React and headless guide

Shared Centerpiece layer Configuration and rate contracts Checkout decision components $200,000 journey classification Idempotent lead creation Secure post-purchase handoff

Start with the retailer's architecture

The customer flow can be selected independently in the Experience Lab.

Use WooCommerce when

WordPress owns checkout and orders

The plugin can use native checkout extensions, order hooks, metadata, and scheduled actions.

Use headless when

The retailer owns a custom storefront and server

The retailer maps its cart and order contracts while Centerpiece supplies components and APIs.

Start with discovery when

The platform or order lifecycle is unclear

Confirm checkout surfaces, authoritative order events, staging access, and server extension points first.

Compare customer experiences Review all implementation options