CGS Blue Cherry and John Lewis Marketplace
Integration Agency & Consultants
Our AI-powered delivery, guided by operators who have run these systems, connects CGS Blue Cherry to John Lewis Marketplace. The link is critical for synchronising inventory in real time to avoid overselling. This gives your teams accurate order data for fulfilment and removes the daily burden of manual processing.
Defining the master data ownership model
Utilize a CGS Blue Cherry and John Lewis Marketplace Integration to seamlessly connect with these platforms, enhancing your multi-channel and omnichannel retail strategy. Leverage Cogent's expertise to scale efficiently, improving operational performance and tech stack capabilities through expert consulting and training.
Solution Design
Our design for the CGS Blue Cherry and John Lewis Marketplace integration establishes clear ownership of data objects. In most implementations, Blue Cherry serves as the system of record for inventory and product master data, while John Lewis Marketplace functions as the primary sales channel. We typically prioritise the flow of sales orders from the marketplace into Blue Cherry to initiate fulfilment, while inventory levels are synchronised on a defined schedule. Choosing a scheduled sync for inventory rather than real-time updates provides a more stable environment for reconciliation at the cost of slight intra-day latency. This design ensures the warehouse team works from a single source of truth in the ERP, while the finance team can rely on consistent data for period-end reporting.
Mapping the bidirectional order fulfilment flow
This integration uses CGS Blue Cherry as the system of record for inventory and John Lewis Marketplace as the sales channel. Stock levels move from Blue Cherry to the marketplace on a defined schedule, ensuring that availability is accurately reflected to customers. When an order is placed on John Lewis, the integration captures the data and creates a corresponding sales order in Blue Cherry for the warehouse to process. After the order is marked as shipped in the ERP, the fulfilment status and tracking information are sent back to the marketplace. This loop ensures data integrity across the order-to-fulfilment lifecycle.
Architecting connectivity with an iPaaS layer
Cogent2 uses IPaaS to streamline integration between CGS Blue Cherry and John Lewis Marketplace, enhancing data flow and operational efficiency. Benefits include reduced integration time, improved scalability, seamless connectivity, and real-time data synchronization, leading to better decision-making and customer experiences.
Monitoring exceptions to protect data integrity
Effective visibility goes beyond checking if a sync is running. It requires identifying specific data mismatches between CGS Blue Cherry and John Lewis Marketplace before they affect operations. We monitor for common issues, such as orders that fail to post into the ERP or inventory levels that do not match across systems. By surfacing these exceptions early, teams can address the root cause, such as an unmapped SKU or a missing product attribute, rather than reacting to missing orders days later. This level of oversight ensures that the integration supports accurate reporting and timely fulfilment.
Operations and finance team handover protocols
Post-launch, we ensure your finance, operations, and ecommerce teams understand their roles within the new operating model. Handover includes clear documentation on where data objects reside and how to manage daily tasks like order monitoring and inventory verification. We define the process for handling common exceptions, such as synchronisation errors or data gaps, ensuring the team knows when to update Blue Cherry and when to adjust settings in John Lewis Marketplace. This documentation is designed as an operational reference for the staff managing the day-to-day business. By establishing these routines, your team can confidently manage the integration and maintain consistency across both systems.
Hypercare and long term integration governance
We provide ongoing support that focuses on maintaining the health of your integration. Our monitoring identifies potential issues, such as failed order transfers or inventory discrepancies between Blue Cherry and the marketplace. If a sync error occurs, we work to resolve it promptly and provide clarity on whether the issue requires a technical fix or a data adjustment in your ERP. This ensures that your operations continue to run smoothly and that your team can rely on the accuracy of the data flowing between your systems.
Common failures
Inventory latency causing overselling
Operational impact: CGS Blue Cherry often updates inventory levels in batch cycles, not in real-time. This creates a dangerous lag where sales on John Lewis are not immediately reflected in the ERP, leading directly to overselling. This impacts seller performance metrics and creates significant work for customer service teams managing order cancellations and for the finance team processing refunds.
Prevention / Action: The integration's inventory sync logic must be designed around Blue Cherry's specific batch processing schedule. A safety stock buffer, held either in the integration layer or on the John Lewis listings, should be used to mitigate risks from this sync delay. Integration rules must also filter CGS stock correctly, distinguishing sellable stock from categories like 'open work orders' to ensure only truly available inventory is published.
Failed dispatch and tracking notifications
Operational impact: If shipment confirmations and tracking numbers from CGS Blue Cherry fail to reach John Lewis promptly, strict dispatch SLAs can be breached, resulting in penalties. Failure to send this data also means customers do not receive automated tracking updates from John Lewis, increasing 'where is my order?' queries for the customer service team.
Prevention / Action: A definitive mapping table must be maintained between carrier names used in CGS Blue Cherry and the exact carrier codes required by John Lewis. The integration process for sending dispatch confirmations should be scheduled frequently, incorporate a retry mechanism for failed updates, and include exception alerts so the operations team can address sync failures before they breach marketplace SLAs.
Mismatched product identifiers
Operational impact: When a SKU on a John Lewis sales order does not exactly match the corresponding item record in CGS Blue Cherry, the order cannot be created automatically. This halts the pick, pack, and ship process for that order, requiring manual investigation by an operations or merchandising team member to identify and fix the data mismatch. At scale, this creates a constant and costly operational drag.
Prevention / Action: CGS Blue Cherry must be designated the master source for all product data, especially the SKU. The integration logic must enforce a strict, character-for-character match on SKUs when creating sales orders from John Lewis payloads. An exception queue should be used to hold any orders with unrecognised SKUs, with automated alerts sent to the responsible team to correct the underlying data without halting the entire order flow.
Complex financial reconciliation
Operational impact: John Lewis provides periodic payouts, net of commissions, that do not correspond one-to-one with the sales orders in CGS Blue Cherry. This forces the finance team to perform complex manual reconciliation using spreadsheets to match payouts to orders, calculate channel fees, and post journals correctly. This is a time-consuming process that delays the month-end close and obscures true channel profitability.
Prevention / Action: The integration must store the unique John Lewis order ID on every sales order created in CGS Blue Cherry. The integration can then be designed to fetch settlement reports from John Lewis and use this order ID as the key to automatically create the corresponding journal entries. This allows for accurate allocation of revenue, commissions, and fees against each order, providing a clear audit trail for the finance team.
Frequently asked questions
How does the integration prevent overselling if CGS Blue Cherry's inventory updates are not in real-time?
CGS Blue Cherry often processes inventory updates in batch cycles, creating a risk of inaccurate stock levels on John Lewis Marketplace. Our integration validates available-to-sell quantities, for example by filtering out stock allocated to 'Open Work Orders' in Blue Cherry. This ensures the inventory level pushed to John Lewis reflects only what is physically available to fulfil new marketplace orders, which prevents overselling.
How are sales orders from John Lewis Marketplace created in CGS Blue Cherry?
Sales orders from John Lewis Marketplace are automatically created in CGS Blue Cherry to begin fulfilment. A common failure point occurs if the integration does not correctly map warehouse locations to Blue Cherry's mandatory 'Division' and 'Warehouse' codes. Without this precise mapping in the integration logic, sales order creation will fail, delaying the entire order-to-cash process.
What happens if our team manually changes a John Lewis sales order inside CGS Blue Cherry?
While CGS Blue Cherry is the source of truth for fulfilment, manual changes to a sales order within its Order Processing module do not automatically update the order on John Lewis Marketplace. For example, changing a quantity in Blue Cherry will not be reflected on the customer's order status in their John Lewis account. This operational disconnect can create confusion for customer service teams and the end customer.
Our CGS Blue Cherry SKUs are complex. How do you ensure product data lists correctly on John Lewis?
This is a critical step, because CGS Blue Cherry serves as the product master record for your operations. The integration maps your CGS Blue Cherry SKU and other item data to the specific fields required by the John Lewis Marketplace catalogue. Incorrect mapping is a common reason for product listings to fail or display inaccurate information, so we centralise this logic to ensure data is consistent.
We are struggling with manual data entry for John Lewis orders into our ERP. How does this integration help?
This addresses the core commercial trigger for connecting the two systems, which is the high cost of manual administration. By automating the creation of each John Lewis sales order in CGS Blue Cherry, the integration removes a significant manual workload prone to data entry errors. This frees up your operations team to focus on fulfilment and exception handling, not clerical work.