Fulfil and John Lewis Marketplace
Integration Agency & Consultants
Manual processing of John Lewis Marketplace orders creates operational risk as sales volumes grow. Because John Lewis Marketplace requires strict fulfilment timelines, any delay in order processing or mismatch in inventory levels leads to stock discrepancies and potential marketplace penalties. This integration ensures Fulfil acts as the system of record, pushing accurate stock levels to John Lewis while importing order data for immediate fulfilment. Grounding your operations in this flow prevents overselling and protects your account health during peak trading periods.
Auditing system logic and data mapping
We connect your Fulfil and John Lewis Marketplace integration quickly and effectively. Our consulting services are invaluable for businesses using ERP and Marketplaces, including Fulfil and John Lewis Marketplace, by providing in-depth system audits. These audits empower our consultants and your team to identify and resolve inefficiencies, ensuring your ERP and Marketplaces integrations operate smoothly. This proactive approach helps your technology ecosystem run efficiently, so you can deliver an excellent customer experience and maintain a competitive edge.
Solution Design
We design this integration with Fulfil as the unquestioned system of record for inventory and order fulfilment. A primary design decision involves the trade-off between real-time inventory updates and API stability. For John Lewis Marketplace, we typically prioritise frequent, batched inventory pushes to prevent overselling while respecting marketplace rate limits. Orders are sequenced to flow into Fulfil for processing, ensuring complex fulfilment rules are applied before tracking data is batched back to John Lewis. We often defer automated returns handling until order volumes reach a specific threshold, maintaining manual control over early reconciliation. This opinionated design ensures finance closes the month based on Fulfil records, while operations manages the John Lewis requirements without leaving their primary ERP environment. This structure prevents the data drift common in loosely mapped marketplace connections.
Mapping order flows and identifier requirements
The integration establishes a flow where Fulfil governs inventory and order processing. Orders from John Lewis Marketplace are typically fetched on a defined schedule and injected into Fulfil for picking, packing, and dispatch. By using Fulfil as the system of record, inventory levels are pushed to the marketplace to reflect availability. We prioritize specific marketplace requirements, such as approved carrier codes and the 13-digit EAN identifiers required by John Lewis. Fulfil manages the fulfilment logic and once a shipment is confirmed, the tracking status is pushed back to update the marketplace. This reduces manual overhead and helps maintain data integrity across both systems.
Orchestrating the integration via IPaaS layers
Cogent2 uses IPaaS to streamline integration between Fulfil and John Lewis Marketplace, enhancing data flow, reducing manual errors, and improving efficiency. IPaaS offers scalability, real-time data processing, and seamless connectivity, enabling faster deployment and better management of complex integrations.
Detecting synchronisation gaps and EAN mismatches
Standard dashboards often mask the slow accumulation of mismatched stock levels or orphaned orders. Our approach provides visibility into the operational gaps that matter, such as when a John Lewis order fails to import due to an EAN mismatch. We monitor the integration to surface communication failures or API rate limit issues before they result in overselling. By tracking the flow between Fulfil and the marketplace, we identify where manual intervention is required for gift message mapping or carrier code errors. This early detection prevents small technical glitches from becoming large reconciliation problems for your finance and operations teams.
Defining operational routines for internal teams
Handover ensures finance, operations, and ecommerce teams own the new operating model. We define clear routines for monitoring the sync, moving beyond technical settings. Your operations team learns to manage John Lewis Marketplace order flows within Fulfil, while finance typically reviews how to reconcile payouts against marketplace fees. We document which team owns specific exception types, such as identifier mismatches or tracking update failures. This documentation serves as a practical operational reference for the people running the business. Training ensures your team can interpret integration alerts and act on them before they impact customer delivery or marketplace standing.
Managing technical exceptions and reconciliation gaps
Post-launch support focuses on maintaining operational trust through active monitoring and clear escalation paths. We handle technical exceptions such as API failures or sync errors, but we also monitor for broader issues like reconciliation gaps between Fulfil and John Lewis Marketplace. Our team provides ongoing ownership of the integration layer, catching tracking update failures or inventory drift before they reach your customers. Escalation is direct and focused on operational impact. This ensures your team can focus on shipping orders while we maintain the integrity of the data flow and system connectivity.
Common failures
Inventory latency and overselling
Operational impact: When inventory updates from Fulfil are not sent to John Lewis Marketplace in near real-time, fast-selling SKUs can be sold after stock has already been depleted. This forces order cancellations, which harms the customer experience and negatively impacts seller performance metrics on the marketplace. The customer service team is left to manage disappointed buyers, while the operations team must reconcile the oversold Sales Orders.
Prevention / Action: The integration's design must treat Fulfil as the definitive source of truth for stock levels and prioritise low-latency updates to the marketplace. Inventory synchronisation should be triggered by stock-changing events in Fulfil, not based on a slow, scheduled batch process. A robust strategy includes using a stock buffer for volatile SKUs and monitoring the sync queue for delays, with alerts for the operations team.
Dispatch confirmation and carrier mapping errors
Operational impact: John Lewis requires a specific 'Carrier Code' from an approved list with every dispatch notification; failure to provide this correctly can delay payouts and damage seller ratings. The fulfilment team may dispatch an order correctly, but if the integration passes the wrong carrier name from Fulfil, the confirmation is rejected. This forces the finance team to manually track down failed confirmations and chase delayed payments.
Prevention / Action: Build a strict mapping table within the integration logic that translates the carrier services used in Fulfil to the corresponding, exact John Lewis carrier codes. This mapping must be treated as critical configuration, with processes to update it if either system changes its naming convention. The integration should also have a clear exception handling process that flags failed dispatch confirmations for immediate review by the fulfilment team.
Mismatched order and return references
Operational impact: If the 'Customer Order Number' from John Lewis is not stored in a persistent, searchable field on the Fulfil Sales Order, cross-referencing transactions becomes a highly manual task. Customer service teams cannot find marketplace orders in Fulfil when handling a query, and the finance team struggles to reconcile returns and refunds against the original sale. This creates significant operational drag, especially during peak trading and returns periods.
Prevention / Action: The integration must map the John Lewis Customer Order Number to a dedicated external ID field on the Fulfil Sales Order from the outset. This unique identifier must be carried across all related records, including item fulfilments and subsequent credit notes for returns. This ensures a consistent reference key exists for operational teams and any automated reconciliation processes, making lookups fast and reliable.
Incorrect financial reconciliation
Operational impact: John Lewis Marketplace settlement reports contain commissions, fees, and other charges that are difficult to allocate against individual Sales Orders in Fulfil without a clear data strategy. The finance team is often forced into manual spreadsheet work to reconcile payouts, calculate VAT correctly, and analyse SKU-level profitability. This slows down the month-end close process and obscures the true net margin of the marketplace channel.
Prevention / Action: Design the order-to-cash process to account for marketplace fees by creating dedicated fields in Fulfil to store commission and other costs passed via the integration. The integration should be designed to pull John Lewis settlement reports and automatically allocate the costs back to the relevant Fulfil Sales Orders. This provides the finance team with the data needed to create accurate journal entries and automate most of the reconciliation.
Frequently asked questions
How do we prevent overselling on John Lewis Marketplace when our stock is managed in Fulfil?
Fulfil will act as the master system of record for all inventory. The integration updates the stock level for each SKU on John Lewis Marketplace whenever a change occurs in Fulfil, such as a sale on another channel or a delivery of new stock. This ensures your John Lewis listings are always accurate, protecting your seller performance by preventing you from selling inventory you do not have.
My team is manually entering John Lewis orders into Fulfil. How does the integration fix this?
Manually keying orders is a primary cause of fulfilment delays and errors. The integration automatically creates a new Sales Order in Fulfil as soon as a customer completes their purchase on John Lewis Marketplace. This removes the manual step, ensuring the order-to-cash process starts immediately with the correct data.
John Lewis requires specific carrier codes for dispatch updates. How does the integration handle this?
A common failure point is a mismatch between carrier names used in an ERP and those required by a marketplace. This integration maps the carrier service used on the Item Fulfilment in Fulfil to the exact carrier code required by John Lewis. This ensures tracking information syncs correctly, which is essential for getting paid and keeping the customer informed.
What happens if our SKUs in Fulfil don't perfectly match the listings on John Lewis Marketplace?
This is a frequent cause of order synchronisation failures and stock level discrepancies. The integration logic requires an exact match between the SKU on the John Lewis listing and the corresponding Item record in Fulfil. Any mismatch, including extra spaces or special characters, will cause data to stop flowing, so establishing a clean mapping is a critical part of the implementation.
How are customer returns managed between Fulfil and John Lewis Marketplace?
Handling returns requires a clearly defined process to maintain accurate inventory and financial records. When a return is initiated on the John Lewis portal, the integration can be configured to create a corresponding return authorisation in Fulfil. This provides the warehouse with visibility of the incoming return and ensures stock levels are only updated after the item has been physically received and inspected.