John Lewis Marketplace and Klaviyo

Operational impact: If a customer's marketing consent status from their John Lewis account is not accurately synced, the business risks sending marketing to users who have opted out, creating compliance issues. Conversely, a failure to sync new opt-ins means the marketing team cannot target new customers with welcome flows, leading to immediate revenue loss and poor initial customer experience.

Prevention / Action: The integration must treat the customer record from John Lewis Marketplace as the source of truth for marketing consent. Logic should be designed to synchronise the 'accepts marketing' status to the Klaviyo profile upon creation and listen for any subsequent changes. This is typically handled by a frequent, scheduled job that queries for recent customer updates, not just relying on order-triggered syncs.

Operational impact: Post-purchase automations in Klaviyo, like shipping confirmations and review requests, depend on timely dispatch data. When the 'Order Dispatched' event from John Lewis is delayed, customers receive notifications late, increasing 'where is my order?' queries for the CX team. This lag also misaligns the timing of review requests, asking for feedback before a product has even arrived.

Prevention / Action: Design the integration to process dispatch confirmations from John Lewis as near to real-time as the platform's APIs allow, rather than using a slow, periodic batch schedule. The process must be instrumented with monitoring to detect and alert on delays or failures in this specific data flow. A robust retry policy is essential to manage transient API connection issues and ensure events are not dropped.

Operational impact: If a customer returns an order but this information does not update their Klaviyo profile, they will continue to be included in irrelevant marketing campaigns. This can involve asking for a review of a returned product or cross-selling accessories for an item they no longer own. This creates a confusing customer experience and reduces the effectiveness of marketing segmentation and spend.

Prevention / Action: The integration must map the 'Return' and 'Refund' events from the John Lewis order lifecycle to specific events in Klaviyo. This enables the creation of dynamic suppression segments, excluding recently returned customers from certain campaigns. The synchronisation should be triggered on return confirmation to ensure Klaviyo data is accurate before the next marketing cycle executes.

Operational impact: When an order is cancelled in John Lewis but the corresponding `Placed Order` event is not removed or updated in Klaviyo, reporting becomes inaccurate. Marketing and finance teams see inflated revenue and customer lifetime value metrics within Klaviyo, leading to misinformed decisions. It also risks triggering post-purchase automations for orders that will never be shipped, damaging customer perception.

Prevention / Action: Establish a process to sync `Cancelled Order` events from John Lewis to Klaviyo with the same priority as `Placed Order` events. This allows for the creation of reporting dashboards that correctly filter out cancelled transactions from performance metrics. This process must account for different cancellation scenarios, such as customer-initiated versus seller-initiated, and ensure the status is updated reliably.