Clarus WMS and John Lewis Marketplace
Integration Agency & Consultants
Overselling on John Lewis Marketplace usually signals that Clarus WMS is no longer the master of inventory truth across your channels. When marketplace orders fail to transmit or stock levels lag during peak periods, the resulting SLA breaches put your vendor rating at risk. This integration ensures that inventory availability in Clarus WMS is reflected accurately on the marketplace, preventing stockouts and protecting your reputation through automated fulfilment flows.
Audit of tech ecosystems and inefficiencies
Cogent will efficiently connect your Clarus WMS with the John Lewis Marketplace, ensuring your WMS/3PL and Marketplaces operate optimally. Our consulting services, particularly our system audit services, are invaluable. They provide a comprehensive analysis of your tech ecosystem, enabling our consultants and your team to address inefficiencies. This ensures your Clarus WMS and John Lewis Marketplace integrations run smoothly, enhancing your WMS/3PL and Marketplaces operations. Ultimately, this allows you to deliver an exceptional experience to your customers.
Solution Design
We architect the Clarus WMS and John Lewis Marketplace integration with a clear logic: Clarus serves as the master for inventory and fulfilment. Orders from the marketplace typically post to the WMS on a defined schedule to meet John Lewis's strict fulfilment SLAs. A key design decision involves the inventory sync: we prioritze pushing accurate stock levels from Clarus to the marketplace to prevent overselling, accepting the trade-off that frequent updates increase API load during peak periods. Finance usually requires daily order totals for reconciliation, while operations relies on the real-time pick-face data. This design ensures that dispatch confirmations flow back to John Lewis once orders are processed, maintaining marketplace performance scores without requiring manual status updates or double-keying data.
Data synchronisation and order status loops
Clarus WMS serves as the master for inventory and fulfilment data. When an order is placed on John Lewis Marketplace, it is transmitted to Clarus to enter the pick-and-pack workflow. Upon dispatch, Clarus pushes the fulfilment status back to John Lewis to close the order loop. The integration synchronises 'Available to Sell' levels from the warehouse to the marketplace on a defined schedule to prevent overselling. Monitoring is used to identify orders that fail to transmit, allowing for intervention before they breach marketplace fulfilment timelines.
Secure orchestration via compliant middleware platforms
Cogent2 leverages IPaaS to deliver Clarus WMS and John Lewis Marketplace integrations securely and efficiently. Using an IPaaS platform with ISO 27001 and SOC 2 compliance and above ensures secure data handling. This approach benefits WMS/3PL and marketplaces by providing reliable, scalable integration solutions. Clarus WMS and John Lewis Marketplace benefit from streamlined operations, while WMS/3PL and marketplaces enjoy enhanced data security and connectivity.
Monitoring exceptions to protect marketplace scores
Dashboards only show part of the story; real visibility requires knowing where data has stalled between Clarus and John Lewis. We focus on surfacing hidden exceptions, such as orders that are stuck in a 'partially fulfilled' state or inventory syncs that have failed due to SKU mismatch. The Cogent platform monitors these integration flows, alerting you to failures so your team can act before John Lewis penalises your account for late shipping. It transforms technical logs into operational insights, showing exactly which orders require attention and why.
Operational handover for internal business teams
Training identifies clear ownership for operations, ecommerce, and finance teams. We hand over an operational guide that explains where stock levels and order statuses live, ensuring teams know which system handles specific exceptions. Operations learn to monitor dispatch triggers, while finance is trained on how to reconcile marketplace payouts against Clarus fulfilment records. We define what needs checking on a defined schedule, such as order sync errors and inventory reconciliation. This isn't a technical manual; it is an operational reference written for the people running the business. It ensures that if a John Lewis order fails to transmit, your team knows how to respond.
Governance of warehouse and API uptime
Ongoing support focuses on operational uptime between the warehouse floor and the John Lewis Marketplace. We monitor for API disruptions and warehouse exceptions that could stall order flow. Our approach ensures that if a sync fails, the breakdown is identified before it impacts customer SLAs. We provide visibility into sync health and reconciliation accuracy to maintain marketplace performance and keep operations running without manual data fixes.
Common failures
Inventory latency causing overselling
Operational impact: A delay between a stock movement in Clarus WMS and the corresponding update on John Lewis Marketplace leads to overselling popular SKUs. This results in cancelled Sales Orders, negative customer experiences, and harms seller performance metrics. The customer service team is occupied with managing disappointed customers, while the fulfilment team must manage exceptions for orders that cannot be shipped.
Prevention / Action: Design the integration to treat Clarus WMS as the definitive source of truth for all inventory levels. Stock updates pushed to John Lewis should be event-driven or run on a very frequent schedule, triggered by any change in sellable stock within Clarus. A small safety stock buffer can be configured within the marketplace listing as a fallback, but the primary goal of the integration is to achieve near-real-time accuracy to minimise reliance on it.
SKU data mismatch halting order processing
Operational impact: Orders from John Lewis fail to be created in Clarus WMS because the SKU does not exactly match the item record in the warehouse system. Differences in case-sensitivity, special characters, or leading zeros cause these orders to fall into an error queue. This effectively stops the pick, pack, and ship process until a member of the operations team manually investigates and corrects each failed order, causing significant dispatch delays.
Prevention / Action: Implement a strict data governance process where Clarus WMS acts as the master for all SKU and product identifier data. The integration logic should include a transformation step to normalise incoming SKUs from John Lewis before attempting to create the Sales Order in Clarus. This process should handle whitespace trimming and case conversion to ensure consistency. A robust monitoring and alert system should be in place to flag any SKU mismatches for immediate review.
Failed dispatch notifications due to carrier mismatch
Operational impact: Clarus confirms an order as shipped, but the dispatch notification fails to update John Lewis because the carrier name does not precisely match the marketplace's approved list. This failure can lead to late shipment penalties, delayed customer notifications, and puts the seller account at risk of suspension. The operations team is forced to manually enter tracking details into the John Lewis portal, which is inefficient and prone to error, and it can delay the release of funds.
Prevention / Action: The integration must include a rigid mapping table to translate the carrier descriptions used in Clarus to the specific 'Carrier Codes' required by John Lewis Marketplace. This mapping should be actively maintained and reviewed whenever courier services are added or changed. The integration's error handling should immediately flag any shipment where the carrier cannot be mapped, preventing silent failures and allowing for a quick operational fix.
Mismatched order identifiers complicate reconciliation
Operational impact: John Lewis payout reports are difficult to reconcile against company financial records because the unique marketplace order number is not stored on the corresponding Sales Order in Clarus. This forces the finance team to perform time-consuming manual matching of transactions, which slows down the month-end close process. Without a shared identifier, it becomes difficult to accurately trace payouts to specific Item Fulfilments and calculate per-order profitability.
Prevention / Action: Ensure the integration is configured to capture the John Lewis 'Customer Order Number' during order ingestion and store it in a persistent, indexed field (such as an 'External ID' or custom field) on the Sales Order record in Clarus WMS. This creates a reliable link between the two systems. This identifier should then be referenced in all financial reporting to enable automated reconciliation between John Lewis payout statements and internal journal entries.
Frequently asked questions
What happens if our SKUs in Clarus WMS don't perfectly match those on John Lewis Marketplace?
If a SKU on a John Lewis Marketplace Sales Order does not exactly match the corresponding Item record in Clarus WMS, the order transmission will fail. This requires manual investigation to find and correct the SKU data in either system, which delays the entire fulfilment process for that order and can impact seller metrics.
How does this integration stop us overselling on John Lewis during busy sales periods?
The integration establishes Clarus WMS as the master system for all inventory, creating the source of truth for stock levels. When stock is allocated to an Item Fulfilment in Clarus WMS, the integration automatically pushes an updated quantity to the corresponding SKU on John Lewis Marketplace. This near real-time stock sync is the primary mechanism to prevent overselling items you do not have.
How do we ensure John Lewis accepts our despatch notifications from Clarus WMS?
When Clarus WMS processes a shipment, the integration sends a despatch confirmation to John Lewis Marketplace that must use the specific carrier name from their approved list. For example, if your WMS record just says 'DPD' but John Lewis requires 'DPD UK' for that service, the notification will be rejected. This failure risks breaching your seller performance SLAs and delays important customer updates.
How do we prevent duplicate orders from being created in Clarus WMS?
To prevent duplicate records, the integration maps the unique John Lewis 'Customer Order Number' from each Sales Order to a corresponding 'External ID' field in Clarus WMS. This allows the system to check if an order already exists before creating a new one. Without this unique reference, you risk creating multiple fulfilment jobs for the same sale, causing significant stock and reconciliation problems.