OroCommerce B2B and John Lewis Marketplace
Integration Agency & Consultants
Cogent2 connects OroCommerce B2B and John Lewis Marketplace using AI-powered delivery, overseen by operators who have run these systems commercially. We focus on unifying product catalogues and inventory data, a common failure point for these projects. This gives your team a single, accurate view of stock, enabling confident marketplace expansion.
Auditing technical gaps and system readiness
Cogent2 connects your OroCommerce B2B with the John Lewis Marketplace, enhancing your ecommerce capabilities. Our consulting services, including system audits, are invaluable for identifying inefficiencies and integration gaps. By addressing these issues, our consultants work with your team to ensure your tech ecosystems operate smoothly and efficiently. This enables you to deliver an exceptional customer experience. With expertise in OroCommerce B2B and John Lewis Marketplace, we help optimise your ecommerce and marketplace operations, ensuring your business runs effectively and meets customer expectations.
Solution Design
Design for OroCommerce B2B and John Lewis Marketplace begins with the product catalogue. OroCommerce typically acts as the master for product data and stock, as it handles complex B2B attributes that the marketplace requires in a specific format. A core design decision involves the trade-off between high-frequency inventory updates and system stability. Frequent syncs reduce overselling risk but increase the load on API thresholds during peak periods. Orders typically flow from John Lewis back to OroCommerce for fulfilment, ensuring existing warehouse processes remain the priority. This design ensures finance can reconcile marketplace settlements against known orders, while operations maintain a single view of stock across B2B and marketplace channels.
Mapping data transfers and order injection logic
The integration establishes OroCommerce B2B as the master for product information, pushing enriched catalogue data to John Lewis Marketplace. To protect against overselling, inventory levels are synced on a defined schedule to meet marketplace performance standards. Orders from John Lewis are captured and injected back into OroCommerce for fulfilment. We prioritise data integrity by mapping specific B2B attributes to the marketplace taxonomy, ensuring SKU consistency across both platforms. Monitoring is built into the flow, catching mapping errors or failed order injections before they impact customer experience or lead to marketplace penalties.
Middleware orchestration and data security standards
Cogent2 leverages IPaaS to integrate OroCommerce B2B with John Lewis Marketplace, ensuring secure and efficient Ecommerce operations. IPaaS platforms facilitate seamless connections between Marketplaces, enhancing data flow and operational efficiency. With ISO 27001 and SOC 2 compliance as the minimum requirements, these platforms ensure robust security. By using IPaaS, businesses like OroCommerce B2B and John Lewis Marketplace can optimise their Ecommerce strategies, benefiting from streamlined processes and enhanced security measures.
Tracking sync health and operational data drift
Dashboards often fail to surface the silent errors that cause the most damage, such as a product appearing active in OroCommerce but failing to list on the marketplace due to a data mapping error. Our visibility layer monitors the health of the connection, alerting your team to inventory sync delays or calculation discrepancies. We track the movement of every order and stock update, ensuring that if a marketplace order fails to post to OroCommerce, it is flagged immediately for intervention. This proactive monitoring stops data drift from compounding, giving finance and operations a verified view of channel performance.
Operational handover for your internal teams
Handover ensures your ecommerce, ops and finance teams own the new operating model. Training focuses on daily and weekly management rather than technical theory. We define exactly where product data and orders live, how to read marketplace alerts and who owns specific exception types like mapping failures or inventory mismatches. Your team learns to monitor the flow between OroCommerce B2B and John Lewis Marketplace, identifying when a B2B attribute has failed to translate to the marketplace front-end. We provide operational documentation written for the people running the business, serving as a practical reference for resolving common data sync issues and maintaining catalogue integrity.
Ongoing technical governance and error resolution
Cogent2 offers robust support for your Ecommerce and Marketplaces operations, ensuring business continuity and peace of mind. With expertise in OroCommerce B2B and John Lewis Marketplace, they provide on-hand technical knowledge and support. Their services help maintain and optimise your Ecommerce platforms, including OroCommerce B2B, and ensure smooth operations on Marketplaces like John Lewis Marketplace, allowing you to focus on growth without technical disruptions.
Common failures
Inventory latency and overselling
Operational impact: Stock sold via B2B direct channels fails to update John Lewis quickly enough, leading to marketplace sales against zero inventory. This directly impacts seller performance metrics through cancellations and forces the customer service team to handle negative customer experiences. The fulfilment team's workflow is disrupted by exception handling for sales orders that cannot be shipped.
Prevention / Action: The integration must treat OroCommerce as the definitive source of truth for all stock levels. Inventory syncs should be event-driven, triggered by any change in stock quantity within OroCommerce, rather than relying solely on scheduled batch updates. A stock buffer, configured per SKU for the John Lewis channel, provides a safety net, and robust queue handling and retry logic are essential to manage temporary API disconnects without losing updates.
B2B product attributes on the marketplace
Operational impact: Wholesale-specific data such as case-pack SKUs, tiered pricing tables, or internal-only technical specifications are mistakenly synced from OroCommerce to the public John Lewis listing. This confuses customers, risks financial loss if B2B pricing is shown, and damages brand perception. It creates significant manual clean-up work for merchandising and data teams and can lead to account warnings from the marketplace.
Prevention / Action: Establish a dedicated 'channel view' or attribute set within OroCommerce for product data destined for John Lewis. This acts as a logical staging area before the sync. The integration's data-mapping must be configured to read only from this view, explicitly excluding any attributes not intended for public display. This ensures a clear separation between master B2B product records and the curated marketplace catalogue.
Failed dispatch notifications and carrier mismatches
Operational impact: An order is picked, packed, and shipped, but the dispatch confirmation message fails to update John Lewis. This occurs because the carrier name in the fulfilment system does not exactly match a value on the approved John Lewis carrier list. As a result, payments can be delayed, seller metrics are penalised for 'late shipment', and the CX team receives unnecessary 'where is my order?' enquiries.
Prevention / Action: The integration design must include a strict mapping table for carrier codes, translating the internal carrier names used in OroCommerce or the warehouse system into the specific string required by the John Lewis API. This is not a free-text field. The process should include an exception queue, holding back any dispatch confirmations with an un-mappable carrier and alerting an operator to resolve the data issue, preventing silent failures.
Mismatched order references and reconciliation gaps
Operational impact: The unique John Lewis 'Customer Order Number' is not successfully captured and stored on the corresponding Sales Order in OroCommerce. This makes tracing an order from one system to the other a manual, time-consuming process for operations and CX teams. Come month-end, the finance team cannot automatically reconcile payout journals from John Lewis against shipped orders, creating hours or days of investigative work.
Prevention / Action: The integration must, at the point of order creation, map the John Lewis order reference to a dedicated and indexed field within OroCommerce, like 'po_number' or a custom 'external_order_id' attribute. This ID must then be locked and used as the primary key for all subsequent updates, from fulfilment through to returns and financial reconciliation. Asserting this data point's integrity at the start prevents significant downstream operational cost.
Frequently asked questions
How does the integration maintain accurate stock levels between OroCommerce and John Lewis to prevent overselling?
The operating model treats OroCommerce as the single source for inventory, pushing stock levels to John Lewis Marketplace on a defined schedule. The integration logic is built to handle partial or delayed updates from the OroCommerce API, ensuring the stock count sent to John Lewis is always the true available-to-sell figure. This prevents overselling by making sure that a large B2B order in OroCommerce immediately makes that stock unavailable on the marketplace.
We sell in cases and pallets. How do you stop these B2B 'Product Units' from appearing incorrectly on John Lewis?
The integration maps OroCommerce's 'Product Units' to the single saleable SKU that John Lewis Marketplace expects, which is a critical step in the order-to-cash process. This prevents scenarios where B2B-specific units, like a pallet, are listed for the price of a single box. We ensure that only the correct consumer-facing SKU and unit quantity are synchronised from OroCommerce to the marketplace listing, protecting your inventory and pricing.
Our OroCommerce setup uses multiple price lists for different customer tiers. How can we sell on John Lewis without exposing B2B pricing?
The integration is configured to select one specific price list from OroCommerce as the source of truth for your John Lewis Marketplace listings. This ensures your tiered B2B pricing models are never exposed to the public, as only the designated consumer price is ever synced. This gives you central control over marketplace pricing directly within OroCommerce, without disrupting your existing B2B price structures.
When an order is placed on John Lewis, how does it appear in OroCommerce for our fulfilment team?
A new sale on John Lewis Marketplace automatically creates a corresponding Sales Order within OroCommerce, using it as the master system for order management. To ensure accurate tracking through the fulfilment process, the unique John Lewis order identifier is mapped to a custom field on the OroCommerce Sales Order. This centralises all B2B and marketplace orders into a single workflow, preventing any sales from being missed by the operations team.