Odoo and John Lewis Marketplace
Integration Agency & Consultants
Scaling on the John Lewis Marketplace demands strict adherence to dispatch windows and inventory accuracy. When Odoo remains disconnected from the marketplace, teams often struggle with manual order entry and the risk of missing lead-time SLAs. We automate the connection between Odoo and John Lewis to protect your seller performance rating. This ensures fulfilment data flows correctly to preserve your commercial standing on the platform.
Auditing the Odoo ecosystem and marketplace gaps
Cogent2 connects Odoo with John Lewis Marketplace, ensuring your ERP and marketplace systems work efficiently. Our consulting services, particularly our system audit, are invaluable. They provide a thorough analysis of your tech ecosystem, identifying inefficiencies and integration gaps. This enables our consultants and your team to take decisive action, ensuring your Odoo and John Lewis Marketplace integrations run smoothly. By optimising your ERP and marketplace connections, we help you deliver an exceptional customer experience, maintaining operational efficiency and reducing costs.
Solution Design
Design for the Odoo and John Lewis Marketplace integration prioritises compliance with John Lewis fulfilment windows. In this setup, Odoo acts as the authoritative source for inventory and order processing. We typically favour a scheduled sync approach for inventory to maintain system stability, which requires a safety buffer to prevent overselling on the marketplace. Orders flow into Odoo to trigger pick and pack workflows, while courier-specific tracking data must be synchronised back to John Lewis digital systems. This ensures the marketplace record updates within required dispatch windows, protecting the seller rating. This architecture allows finance teams to treat Odoo as the source of truth while operations maintains compliance with marketplace performance standards.
Mapping data flows and carrier code logic
The integration establishes Odoo as the central source of truth for inventory and order processing. Availability is pushed to John Lewis on a scheduled basis to protect against overselling. One essential requirement is mapping Odoo delivery carriers to specific John Lewis carrier and service codes. Without this mapping, order updates can fail. Once fulfilment is confirmed in Odoo, tracking data is pushed back to the marketplace. This includes handling specific metadata like Product Safety attributes to ensure your catalogue remains compliant with John Lewis standards.
Orchestrating workflows via secure IPaaS infrastructure
Cogent2 leverages IPaaS to integrate Odoo with John Lewis Marketplace, ensuring secure and efficient connections. IPaaS platforms, with ISO 27001 and SOC 2 compliance and above, facilitate ERP and marketplace integrations, enhancing data flow and security. This approach benefits businesses by providing a reliable framework for connecting Odoo and John Lewis Marketplace, supporting ERP systems, and maintaining high security standards.
Surfacing sync errors before ratings drop
Standard dashboards often mask the true state of an integration. An issue can occur when Odoo shows a completed shipment, but the tracking data failed to reach John Lewis due to a carrier code mismatch. Our visibility layer surfaces these discrepancies before they impact your seller rating. We monitor for stuck orders and metadata rejection errors that would otherwise lead to manual work. This ensures that when a sync fails, the team is alerted to the specific cause, such as missing marketplace attributes or API throttles during peak periods.
Operating the integration and managing inventory drift
Handover ensures operations, finance, and CX teams own the daily flow between Odoo and John Lewis. Warehouse teams manage tracking synchronisation and dispatch updates, while finance handles order reconciliation against marketplace reports. Teams are trained to read alerts from the integration layer to identify inventory drift or sync errors before they impact seller performance. We provide operational documentation that details the daily checks required to maintain marketplace compliance. This manual is a practical guide for the people running the business rather than a technical archive, anchored in the specific design decisions of your Odoo configuration.
Maintaining connection stability after go-live
After launch, we maintain the connection between Odoo and John Lewis. We monitor the integration for issues, such as when the marketplace updates its approved carrier list or API requirements. Our support prioritises resolving sync errors that could lead to late dispatch marks. We oversee the data flow to ensure inventory remains accurate and that any sync failures are identified and fixed before they impact your seller rating.
Common failures
Dispatch confirmation latency
Operational impact: John Lewis's strict marketplace rules mean that failing to provide timely dispatch notifications with valid tracking data leads to poor seller performance ratings. At scale, this can result in temporary account suspension and lost revenue. Fulfilment and customer service teams are forced into urgent manual data entry via the John Lewis portal, which is inefficient and error-prone.
Prevention / Action: The integration's logic must treat the dispatch confirmation as a high-priority, event-driven process. The workflow should ensure that when an Odoo Delivery Order is validated, it immediately triggers an API call to John Lewis with the correct carrier name and tracking number. A robust mapping between Odoo carrier records and the John Lewis-approved carrier list is critical. Implement exception handling and alerting to flag any failed dispatch updates for immediate investigation by the operations team.
Inventory latency and overselling
Operational impact: When Odoo is the inventory master, delays in synchronising stock levels to John Lewis result in overselling. This creates cancelled orders, which damages the seller rating, harms the customer experience, and creates manual work for customer service teams handling complaints. The finance team must process refunds for these failed Sales Orders, and fulfilment teams waste time on pick lists for items that do not exist.
Prevention / Action: Establish Odoo as the single source of truth for all channel inventory. The integration should be configured to push stock level updates from Odoo to John Lewis on a very frequent, scheduled basis. To mitigate risks from minor sync delays, a stock buffer quantity can be configured in the integration logic, where the level advertised on the marketplace is slightly lower than the actual on-hand quantity recorded in Odoo.
Incorrect mapping of order references
Operational impact: If the unique John Lewis Order ID fails to be stored in a searchable field on the Odoo Sales Order, customer service teams cannot locate orders using the reference provided by the customer. This significantly increases support resolution times and frustrates customers. It also complicates financial reconciliation, as payout reports from John Lewis reference this ID to identify transactions.
Prevention / Action: Define a clear source-of-truth policy during implementation. The John Lewis Order ID must be mapped to a dedicated, indexed field in Odoo, typically the 'Customer Reference' field on the Sales Order object. This ensures the reference is consistently captured and searchable by all teams. The integration process should include validation to ensure this field is populated before the Sales Order is confirmed and processed in Odoo.
Frequently asked questions
Which system holds the master record for inventory and pricing, Odoo or John Lewis?
For a scalable operation, Odoo must act as the central source of truth for all catalogue data, including inventory levels and price lists. The integration then synchronises this information to the John Lewis Marketplace, preventing overselling and pricing errors. This model centralises merchandising and stock control within Odoo, simplifying the management of your item records across all sales channels.
John Lewis has strict SLAs for dispatch confirmation. How does the integration ensure we meet them?
The integration automates the round-trip of fulfilment data, which is critical for meeting John Lewis's standards. When a Sales Order from John Lewis is processed in Odoo and dispatched, the integration must pass the correct carrier code and tracking number back to the marketplace. Failure to map these fields precisely will cause the dispatch confirmation to fail, forcing manual updates and risking account suspension.
We were just approved to sell on the marketplace. Can't we just use a basic connector to start?
While tempting for speed, a basic connector often fails to handle John Lewis's specific operational rules, creating significant manual work later. For instance, it may not map the unique John Lewis Order ID to the 'ExternalID' field on the Odoo Sales Order, causing problems for customer service and returns handling. This can jeopardise your seller performance rating before you have even properly started.
How are refunds and returns handled between John Lewis and our Odoo system?
Returns require careful process mapping because a single event on John Lewis must trigger multiple actions in Odoo. When a refund is processed, the integration must create both a Credit Note for the financial transaction and a separate Stock Return record for the inventory. If only the Credit Note is created, the item is not booked back into available stock in Odoo, leading to inaccurate inventory levels.
Our Odoo products use variants. Will this cause issues when syncing to John Lewis Marketplace?
Yes, this is a common failure point that requires specific mapping logic to handle correctly. The integration must be configured to synchronise Odoo's individual product variants (`product.product`), not just the parent product template. If the logic is incorrect, or if variant SKUs in Odoo do not exactly match the format John Lewis expects, the product listings on the marketplace will fail to create or update.