SAP B1 and John Lewis Marketplace
Integration Agency & Consultants
The delay between high-volume John Lewis Marketplace orders and your SAP B1 system creates serious operational risks. Our integrations are built with AI-powered delivery, guided by experienced operators who understand these platforms. This ensures inventory remains accurate and that fulfilment teams can consistently meet demanding dispatch windows without manual intervention.
Identifying operational gaps and integration risks
Cogent connects your SAP B1 with John Lewis Marketplace, ensuring efficient ERP and marketplace integration. Our consulting services, including system audits, are invaluable for identifying inefficiencies and integration gaps. By addressing these issues, our consultants and your team can ensure your tech ecosystems operate smoothly, allowing you to deliver an exceptional customer experience. With expertise in SAP B1 and John Lewis Marketplace, we help optimise your ERP and marketplace operations, ensuring your business runs efficiently and effectively.
Solution Design
Our design for SAP B1 and John Lewis Marketplace prioritises SAP B1 as the authoritative source for inventory and financial recording. Orders flow into the ERP on a defined cadence, ensuring fulfilment teams work from a single queue. A primary decision involves inventory synchronisation: we prioritises high-frequency stock updates from SAP B1 to John Lewis to prevent overselling on a high-volume marketplace. Conversely, we typically batch financial postings. This is a deliberate trade-off. While real-time financial syncing offers immediate visibility, batching can simplify reconciliation and reduce system load. This approach ensures the finance team closes books using stable ERP data while the warehouse operates from accurate pick lists. The result is an operating model that protects marketplace performance metrics without compromising ERP performance or data integrity.
Mapping bi-directional order and stock flows
The integration establishes a bi-directional flow between John Lewis Marketplace and SAP B1. Orders are pulled from the marketplace and injected into SAP B1 as Sales Orders, using defined mapping rules for tax and customer data. SAP B1 remains the source of truth for all inventory. Stock levels are pushed to John Lewis on a regular cadence to ensure the marketplace reflects actual warehouse availability. Once an order is marked as despatched in SAP B1, the integration pushes the tracking information back to John Lewis to complete the fulfilment cycle. We monitor these flows to detect data errors or SKU mismatches before they impact fulfilment.
iPaaS
The integration establishes a bi-directional flow between John Lewis Marketplace and SAP B1. Orders are pulled from the marketplace and injected into SAP B1 as Sales Orders, using defined mapping rules for tax and customer data. SAP B1 remains the source of truth for all inventory. Stock levels are pushed to John Lewis on a regular cadence to ensure the marketplace reflects actual warehouse availability. Once an order is marked as despatched in SAP B1, the integration pushes the tracking information back to John Lewis to complete the fulfilment cycle. We monitor these flows to detect data errors or SKU mismatches before they impact fulfilment.
Tracking data exceptions and sync health
Standard dashboards often hide the details that cause the most operational friction. We focus on surfacing exceptions: orders that failed to post to SAP B1 due to data discrepancies, or inventory updates rejected by the marketplace because of SKU errors. Our approach monitors the health of the connection, detecting when the sync cadence drifts or when system responses lag. Instead of checking if the integration is running, your team sees exactly which transactions require manual intervention. This visibility prevents small data mismatches from compounding into month-end reconciliation gaps or missed marketplace SLAs.
Transferring workflow ownership to internal teams
Handover focuses on how your finance and operations teams run the business using the integrated SAP B1 and John Lewis Marketplace environment. We provide operational documentation that explains where data originates, what to check regularly in SAP B1 to catch order sync errors, and how to verify marketplace payouts. Operations teams learn to manage inventory alerts, while finance takes ownership of settlement reconciliation. This documentation is written for the people managing the marketplace rather than for IT, serving as a practical guide for daily processes. Training is anchored in the design decisions made for your business, ensuring the team knows exactly how to respond to sync alerts or inventory exceptions.
Maintaining connection stability and data integrity
Once the integration is live, we provide ongoing monitoring to ensure your SAP B1 and John Lewis sync remains stable. We check for system changes, connection timeouts and data exceptions that could disrupt your fulfilment flow. If an order fails or inventory drifts, we identify the root cause—whether it is a configuration error in SAP B1 or a mapping issue—and work to resolve it. This support model means your team can focus on picking and packing orders, while we ensure the technical connection between your ERP and John Lewis Marketplace is maintained.
Common failures
Inventory latency and overselling
Operational impact: High-frequency requests from the marketplace to update stock can cause 'record locking' errors in SAP B1, especially with older integration methods. These failed updates mean the inventory level on John Lewis becomes inaccurate, leading to overselling. This forces the customer experience team to cancel Sales Orders and manage negative feedback, while the operations team investigates stock discrepancies.
Prevention / Action: Avoid using the SAP B1 DI API for high-volume, real-time inventory updates. Instead, use the Service Layer or a queuing mechanism that aggregates updates into controlled batches. This approach respects SAP B1's processing model, reduces locking errors, and provides a more reliable inventory figure to the marketplace, based on a defined schedule rather than failed real-time attempts.
Lost customer order reference
Operational impact: If the John Lewis 'Customer Order Number' is not mapped to a searchable field in the SAP B1 Sales Order, the operational link is broken. The customer service team cannot find marketplace orders in SAP B1 using the customer's reference, delaying query resolution. Finance then struggles to reconcile John Lewis payout reports against SAP B1 invoices, making month-end processes difficult.
Prevention / Action: The integration's mapping logic must place the John Lewis Order ID into a standard, indexed field on the SAP B1 Sales Order, such as 'NumAtCard'. This ensures the number is consistently available for lookups by all teams. This data pathway should be a critical test case during the project, covering both order creation and the returns process.
Dispatch notification and carrier mapping failure
Operational impact: John Lewis requires merchants to use specific carrier codes when confirming dispatch. If the carrier name recorded in SAP B1 or an external warehouse system does not exactly match an approved John Lewis value, the dispatch confirmation API call will fail. This directly impacts seller performance metrics, delays customer notifications, and can hold up the release of funds for that Sales Order.
Prevention / Action: The integration layer must contain a mapping table to translate internal carrier descriptions to the exact string values required by the John Lewis API. This table should be the source of truth for carrier data. The integration should also feature exception handling to flag any un-mappable carriers to the operations team for manual correction and review.
Inaccurate stock from multiple warehouses
Operational impact: When SKUs are held in multiple SAP B1 warehouses (OWHS records), incorrectly aggregating this data for the marketplace feed is a common issue. If the logic fails to sum all locations, or one warehouse sync process fails, the stock level sent to John Lewis is wrong. This results in either significant lost sales through underselling or reputational damage from overselling and cancelling orders.
Prevention / Action: Design the integration to query all relevant SAP B1 warehouses for a specific SKU and sum their 'Available' quantities before pushing a single update. This logic must be atomic, meaning it should only send an update after confirming a successful response from all intended sources. A monitoring process should alert the operations team if any single warehouse location fails to respond.
Frequently asked questions
How can we trust our SAP B1 inventory will stay accurate when selling on a high-volume channel like John Lewis?
The integration establishes SAP B1 as the single source of truth for all inventory, ensuring John Lewis Marketplace only reflects stock you can actually fulfil. As John Lewis sales orders are created in SAP B1, they allocate stock against the item record. The updated available-to-sell quantity is then synchronised back to the marketplace, preventing overselling and protecting your seller rating.
We use multiple warehouses in SAP Business One. How does this affect inventory sync with John Lewis Marketplace?
Mapping multiple SAP B1 warehouses (OWHS) to a single stock feed for John Lewis requires specific logic to prevent inaccuracies. If not aggregated correctly, you risk overselling or showing items as out of stock when they are available in another location. A robust integration sums the inventory from specified warehouses into a single available quantity before updating the stock level on John Lewis.
How do you prevent the integration from slowing down SAP B1 during high-volume stock updates?
This is a common operational risk, as high-frequency inventory updates can cause record-locking on the SAP B1 Item Master Data, interrupting other users. Instead of using direct, real-time updates via the DI API for every change, a more resilient approach queues stock adjustments. This ensures inventory is synced reliably without locking the SAP B1 database during busy periods.
How do we trace an order from John Lewis Marketplace through to our SAP B1 system?
To maintain a clear audit trail, the John Lewis 'Consumer Order Number' must be mapped to a dedicated reference field in SAP B1, typically the 'Customer PO Number' (NumAtCard) on the Sales Order. This ensures that when a customer enquires about their John Lewis order, your team can find it instantly in SAP B1 using the number provided. Without this, matching orders between systems becomes a slow, manual process.
We sell products that need batch tracking in SAP B1. Can the integration handle this?
Yes, but it requires precise configuration at the item level to avoid fulfilment errors. A common failure occurs if a John Lewis order contains an item that requires tracking, but the corresponding 'Item Master' record in SAP B1 is not configured for 'Batch/Serial' management. The integration must create the Sales Order in a way that enforces batch number assignment during the fulfilment process.