Cin7 Core and John Lewis Marketplace
Integration Agency & Consultants
The operational demands of John Lewis Marketplace leave no room for error. Cogent2 uses AI-powered integration delivery and experienced operators to connect Cin7 Core correctly. This establishes reliable inventory control and accurate order data, protecting your supplier score and preventing costly penalties for compliance or fulfilment failures.
Mapping retail compliance and stock logic
Discovery for the Cin7 Core and John Lewis Marketplace integration focuses on the strict compliance demands of premium retail. We diagnose the source of truth for available-to-sell stock and examine current manual workarounds that often lead to data contradictions. We specifically map the ownership of order data against fulfilment responsibilities in Cin7 Core. Before any technical work begins, we decide on the logic for specific shipping documentation and the timing for dispatch updates. Skipping this diagnosis usually results in design flaws that lead to supplier penalties and stock drift. This process ensures finance and ops agree on a single operating model for dropship fulfilment before implementation starts.
Solution Design
Our design for Cin7 Core and John Lewis Marketplace is opinionated regarding inventory accuracy. We establish Cin7 Core as the authoritative master for stock and shipping status, while John Lewis remains the source of truth for order capture. A key trade-off we manage is sync frequency. While high-frequency inventory updates protect against overselling, they are typically balanced against system reliability to ensure stability during peak trading. We prioritise the automated generation of branded packing slips within Cin7 Core to meet strict delivery standards. This design ensures the warehouse team works off accurate pick lists while finance relies on verified dispatch triggers for marketplace reporting and month-end reconciliation.
Enforcing SKU matching and shipment sequencing
This integration establishes Cin7 Core as the master for inventory and shipping status, while John Lewis Marketplace holds the primary customer and order record. Orders flow into Cin7 Core on a defined schedule, creating a Sale Task that serves as the trigger for fulfilment.
We prioritise data integrity by enforcing exact SKU-to-SKU matching; any mismatch is flagged at the integration boundary before it reaches the warehouse. Sequencing is critical for compliance. Once the warehouse confirms a shipment, dispatch status and tracking data must flow back to the marketplace within John Lewis's non-negotiable windows. Our monitoring agents track these fulfilment events in real-time, surfacing sync failures or documentation gaps before they impact your supplier standing or lead to financial penalties for late shipping.
Orchestrating data flow with active governance
A controlled integration layer governs the data flow between Cin7 Core and John Lewis Marketplace, moving orders, inventory updates, and fulfilment manifests. This layer acts as governance rather than a passive pipe. It manages data requirements for premium retail compliance at the boundary. If a sync fails, through a SKU mismatch or malformed payload, the layer triggers a defined retry schedule and alerting to the operations team. We use full payload logging and validation to prevent corrupt data from reaching Cin7 Core. This infrastructure is designed to high security standards consistent with retail enterprise requirements. Cogent consultants and operational monitoring agents actively manage the layer day to day to ensure compliance and stock reliability.
Surfacing fulfilment gaps and sync illusions
A dashboard that merely shows a successful sync is not enough to manage a premium retail account. Operational intelligence requires visibility into the specific compliance gaps that lead to penalties, such as missing tracking numbers or incorrect documentation formats. Errors often hide where an order is accepted by Cin7 Core but fails to trigger an update back to the marketplace. Our platform surfaces these hidden failures early, distinguishing between a temporary timeout and a critical data error. This allows your team to fix a mapping error before the dispatch window closes. High-volume operations cannot rely on manual audits; they need proactive monitoring that prioritises the exceptions truly threatening the retail relationship.
Handing over the new operating model
Adoption begins by defining how finance, operations, and ecommerce teams interact with the new data flow. We hand over an operating model that explains where data originates and who owns exception handling when a marketplace order fails to map correctly. Training covers daily checks required to maintain stock integrity and explains how to read alerts from the integration layer. We document specific processes for handling returns and marketplace-specific arrivals. This documentation is operational, not a technical archive. It is written for the people running the business, ensuring they can manage the strict dispatch windows and document requirements needed to maintain account compliance.
Managing long term compliance and reconciliation
Ongoing support focuses on maintaining fulfilment compliance and eliminating reconciliation debt. We monitor the flow between Cin7 Core and John Lewis to catch common failure modes, such as SKU mapping errors or tracking update delays that could lead to account penalties. When exceptions occurs, we provide the technical and operational oversight needed to keep your marketplace account in good standing. This includes monitoring for instances where stock levels appear accurate but have failed to update on the marketplace. Support typically includes tracking the health of your stock sync and order-to-cash reconciliation processes to ensure warehouse activity is reflected accurately in your financial reporting.
Common failures
Inventory latency and overselling
Operational impact: Stock level updates from Cin7 Core that are slow to reach John Lewis Marketplace result in overselling, particularly on fast-moving SKUs. This directly breaches supplier agreements, leading to financial penalties and negative performance scores which risk account suspension. The customer service team is left to manage cancelled orders, while fulfilment teams must manually adjust stock records, creating a cycle of untrustworthy data.
Prevention / Action: The integration must be designed for high-frequency stock synchronisation, treating Cin7 Core as the definitive source of truth for inventory. Implement robust queueing, retry logic, and error handling to manage API rate limits or transient connection issues. A deliberately managed stock buffer can be configured in Cin7 Core, but it must be an intentional policy, not a workaround for poor integration reliability.
Incorrect carrier mapping and despatch non-compliance
Operational impact: John Lewis enforces a strict list of approved carrier codes for despatch notifications. If the carrier service description in Cin7 Core does not map exactly to the required John Lewis code, every despatch confirmation will fail compliance checks. This results in direct financial penalties per order and damages the supplier's performance rating, forcing the finance team to process and dispute charges.
Prevention / Action: A definitive translation map must be maintained in the integration layer to convert Cin7 Core's carrier names into the specific codes John Lewis requires. This logic must be applied to every fulfilment update pushed to the marketplace, triggered when a Sale Task is completed in Cin7 Core. Design monitoring to catch and hold any despatch advice that contains an un-mapped carrier, preventing compliance failures before they occur.
Missing John Lewis order reference
Operational impact: If the unique John Lewis Customer Order Number is not captured on the corresponding Cin7 Core Sales Order, financial reconciliation is impossible at scale. The finance team cannot automatically match orders to the payout reports provided by John Lewis, forcing laborious manual lookups. This delays the month-end close process and can mask payment discrepancies or missing funds.
Prevention / Action: The integration must be configured to systematically map the John Lewis Customer Order Number to a dedicated field on the Cin7 Core Sales Order, such as 'External ID'. This must be a mandatory part of the order creation process. Using this field as a unique key for matching allows the finance team to automate the reconciliation of payout reports against fulfilled Sales Orders.
SKU mismatch and order processing failures
Operational impact: When SKUs in Cin7 Core and John Lewis do not have an exact one-to-one match, all automation breaks. Incoming orders from the marketplace fail to create Sales Orders in Cin7 Core, and inventory updates from Cin7 Core do not sync to the correct product listing. This forces daily manual data correction by operations teams, delays order processing, and can lead to overselling or despatch delays that breach John Lewis's strict SLAs.
Prevention / Action: Define Cin7 Core as the single source of truth for all product master data, including the SKU. The integration logic must enforce a strict SKU matching rule and prevent new listings from being created on John Lewis without a corresponding SKU in Cin7 Core first. Implement an exception queue to hold any orders containing an unrecognised SKU, alerting an administrator to resolve the data issue before the order is processed.
Frequently asked questions
How does the integration handle John Lewis's strict fulfilment and branded document requirements?
The integration maps John Lewis's specific requirements to actions within Cin7 Core, such as ensuring the correct, approved carrier code is used for a shipment. It can also help automate the generation of correctly branded packing slips directly from the Item Fulfilment record in Cin7 Core. This avoids manual work and protects against compliance failures that risk supplier penalties.
What is the most common reason for stock level errors between Cin7 Core and John Lewis?
The most frequent cause of stock sync failures is a mismatch between SKUs in Cin7 Core and the corresponding product listings on John Lewis Marketplace. Cin7 Core requires an exact SKU-to-SKU match to synchronise inventory levels correctly. Any discrepancy will break the link for that item, leading to inaccurate stock on the marketplace and a high risk of overselling.
We are just starting with John Lewis using spreadsheets; when does this approach typically become a problem?
Manual spreadsheet processes usually become unsustainable once your John Lewis order volume grows beyond a few orders per day. Teams find they cannot update stock levels in Cin7 Core quickly enough, causing overselling, or fail to get dispatch confirmations back into John Lewis within the required window. These compliance failures and stock inaccuracies are the most common commercial trigger for automating the process.
Which system should be the master for inventory and orders in this setup?
For this integration, the standard operating model uses John Lewis Marketplace for order capture and Cin7 Core as the system of record for inventory and fulfilment. Sales Orders from John Lewis are automatically created in Cin7 Core. Cin7 Core then acts as the master source of truth for stock levels, pushing regular updates to the marketplace to prevent overselling.
How do you ensure specific John Lewis order data is correctly handled in Cin7 Core?
A key part of the integration is mapping specific John Lewis data points, like their unique 'Customer Order Number', to the correct field on the Sales Order in Cin7 Core. The integration must also correctly interpret channel-specific statuses to prevent orders being dispatched from Cin7 Core prematurely. Incorrectly mapping these details is a common failure point that leads to reconciliation and fulfilment errors.