Seko and John Lewis Marketplace

Operational impact: When inventory updates from Seko fail to sync to John Lewis Marketplace in a timely manner, brands risk selling stock that the warehouse cannot fulfil. This directly leads to cancelled Sales Orders, which harms seller performance metrics and can result in financial penalties. The customer experience team is left managing negative reviews, while the operations team must dedicate time to manually reconciling stock levels instead of focusing on fulfilment.

Prevention / Action: The integration design must treat Seko as the definitive source of truth for stock levels. Inventory updates should be pushed to John Lewis on a frequent, scheduled basis, not just in response to an order. The sync logic must include robust error handling and a retry queue to ensure that failed updates are processed successfully, preventing stale inventory data from causing overselling.

Operational impact: John Lewis Marketplace has strict service level agreements for order dispatch. If the shipment confirmation from Seko is not successfully transmitted back to the marketplace, orders remain in an 'unfulfilled' state. This delays customer notifications, impacts payment settlement, and can lead to SLA breaches and account penalties, even when the item has physically left the warehouse.

Prevention / Action: Design the integration to use the 'Item Fulfilment' or equivalent shipment event from Seko as the sole trigger for updating the John Lewis Sales Order. The process must correctly map Seko's carrier data to the approved John Lewis carrier list. Implement monitoring to detect and alert on any orders that are shipped in Seko but not confirmed on the marketplace within an agreed time window.

Operational impact: If the SKU on an incoming John Lewis Marketplace order does not exactly match a corresponding SKU in Seko's system, the order will fail to be processed. This completely halts the fulfilment workflow for that order, requiring manual intervention from the operations or ecommerce team. At scale, this creates a constant stream of exceptions, increases the risk of SLA breaches, and diverts staff to tedious data correction tasks.

Prevention / Action: Establish a single source of truth for product master data before the integration goes live. A rigorous data alignment exercise must ensure every SKU published to John Lewis exists and matches in Seko. The ongoing process for creating new SKUs must be disciplined, ensuring data is created and matched in both systems before the item is made available for sale.

Operational impact: Dispatch confirmations will be rejected by John Lewis if the carrier service code sent from the integration does not exactly match their predefined list. This means that even if tracking data is correct and the parcel is in transit, the order status on the marketplace will not update. This failure mode directly affects seller metrics, delays payment, and requires the finance or operations team to manually investigate and correct the payload for each failed update.

Prevention / Action: The integration logic must include a maintained mapping table to translate the carrier names provided by Seko into the specific codes required by John Lewis Marketplace. This mapping should be treated as a core configuration item, with clear ownership within the operations team to update it when carriers are added or changed. Exception handling should specifically identify and alert on 'invalid carrier' errors from the marketplace API.