SAP ECC and John Lewis Marketplace
Integration Agency & Consultants
The pressure on your SAP ECC integration usually peaks when a successful John Lewis pilot scales and manual order processing becomes impossible to maintain. At this volume, failing to map specific carrier codes or missing order cancellation windows in ECC leads to immediate service level penalties. Maintaining your partner status requires orders to flow from the marketplace to SAP and shipping updates to return without manual intervention. We focus on bridging the gap between the rigid material master requirements of SAP and the strict compliance standards of high-end UK retail.
Identifying constraints within your ECC environment
Cogent2 connects your SAP ECC with the John Lewis Marketplace, ensuring your ERP systems are efficient. Our consulting services, including system audits, are invaluable for identifying and addressing inefficiencies. These audits enable our consultants and your team to take decisive action, ensuring your tech ecosystems, including SAP ECC and John Lewis Marketplace, operate smoothly. This efficiency in ERP and marketplaces integration allows you to deliver an exceptional customer experience. Our expertise ensures your business runs effectively, supporting your growth and operational goals.
Solution Design
The design prioritises SAP ECC as the master for inventory and pricing, while the marketplace remains the source of truth for the initial customer order. A core design decision involves the trade-off of inventory sync frequency: pushing updates at a high frequency protects against overselling but increases the processing load on SAP material updates. We typically sequence order flow and stock sync first, deferring complex financial reconciliation until the core fulfilment path is stable. Finance closes monthly based on the ERP ledger, while operations works off shipping updates flowing back to the marketplace. This opinionated structure ensures that rigid heritage system structures map correctly to modern retail compliance requirements, preventing the failed product listings common in standard setups.
Mapping order data to SAP sales requirements
The integration maps marketplace order data directly into SAP ECC as Sales Orders, ensuring the John Lewis 'Consumer Order Number' is captured in the SAP Purchase Order (BSTNK) field for customer service visibility. SAP ECC remains the master for material data and stock balances, with updates managed to respect API limits while maintaining retail SLAs. Ship confirmations must provide the carrier service code exactly matching the JLP approved list to avoid rejection at the gateway. Monitoring tracks document statuses within ECC, detecting mapping errors or shipping rejections before they impact your supplier service levels. This ensures the rigid structure of your ERP aligns with the specific compliance requirements of the John Lewis marketplace.
Orchestrating logic via a secure iPaaS layer
Cogent2 leverages iPaaS to integrate SAP ECC with John Lewis Marketplace, ensuring secure, efficient connections. iPaaS benefits include centralised ERP integration, supporting SAP ECC and John Lewis Marketplace, while maintaining ISO 27001 and SOC 2 compliance and above. This approach enhances ERP and marketplace operations, providing robust security and streamlined data management.
Surfacing order exceptions and stock drift
Dashboards often hide individual order failures while showing overall sync success. We focus on granular visibility into the data flow, surfacing specific mapping errors where SAP ECC data does not align with John Lewis Marketplace requirements. Hidden issues, such as stock level drift or unacknowledged orders, can compound quickly during peak periods. Monitoring detects these exceptions early, alerting your operations team before a processing bottleneck results in a marketplace compliance breach. This proactive approach ensures you maintain visibility of the health of your retail partnership, rather than just monitoring bulk data movement.
Defining operational ownership across your teams
Finance, operations, and ecommerce teams must adopt a specific operating model to maintain John Lewis partnership standards. We hand over an operational guide that defines ownership boundaries, from SAP ECC material masters to marketplace shipping statuses. Training covers daily stock checks, reconciliation, and how to interpret alerts when a data transfer fails or a carrier code mismatch occurs. Your team learns to identify the root cause of stalled orders before they breach delivery SLAs. Documentation is provided as a practical reference for the people running the business, not a technical archive for IT. Your leads will understand exactly who owns each exception type, ensuring stock levels and fulfilment requirements are managed effectively across both systems.
Maintaining compliance through technical governance
Post-launch support focuses on maintaining the data flow between SAP ECC and John Lewis Marketplace. We provide ongoing monitoring to catch sync failures, mapping errors, or processing bottlenecks before they impact your warehouse or the customer experience. Our team handles troubleshooting for technical drift, ensuring that your internal teams can focus on fulfilment rather than diagnosing data errors. We oversee the health of the integration, providing a clear path for resolving exceptions and maintaining your standing as a John Lewis partner.
Common failures
Inventory latency and overselling
Operational impact: Delayed inventory updates from SAP ECC to John Lewis are a primary cause of overselling. Because SAP's Available-to-Promise (ATP) calculation may only run periodically, stock levels shown on the marketplace can be out of sync with the physical warehouse. This leads to cancelled Sales Orders, a poor customer experience, and direct breaches of John Lewis's strict supplier performance SLAs.
Prevention / Action: The integration's stock synchronisation cannot depend solely on batch-processed IDocs. A more frequent delta-based update process should be designed, triggered by stock movement events within SAP for specific SKUs. This ensures that SAP ECC remains the master source of truth for inventory, but communication with the marketplace is optimised for speed and accuracy, reducing the risk of selling stock that is not available.
Failed dispatch notifications and SLA breach
Operational impact: Although the fulfilment team dispatches an order on time, the dispatch confirmation fails to reach John Lewis because of a data mismatch. This commonly occurs when carrier information in the DESADV IDoc from SAP does not map exactly to a John Lewis approved carrier code. These failures count as a late shipment, directly impacting supplier performance metrics and potentially leading to financial penalties or suspension.
Prevention / Action: Design the integration to hold a specific mapping table for SAP's carrier codes against the approved John Lewis carrier list. The integration process should be triggered by the Post Goods Issue (PGI) event in SAP, immediately transforming the carrier data and sending the shipment notification. An exception queue must be configured to alert the operations team if an un-mapped carrier is used, allowing for immediate correction before an SLA is breached.
Incorrect product data and failed listings
Operational impact: John Lewis requires product data in a specific format, which often differs from how it is stored in SAP's Material Master. A frequent error is the SAP material number, often a padded 10-character field, not matching the John Lewis SKU, which prevents stock and price from syncing. This causes an operational burden on merchandising and ecommerce teams who must manually diagnose and correct these SKU-level discrepancies to ensure products are live and available for sale.
Prevention / Action: The integration must contain a transformation layer to cleanse and format data before it reaches the John Lewis API. This includes logic to trim leading zeros from SAP material numbers and map internal SAP values to the required John Lewis nomenclature. This process ensures that SAP remains the master for core product data while preventing its structural nuances from causing downstream listing or synchronisation failures on the marketplace.
Payout reconciliation discrepancies
Operational impact: John Lewis settlement reports and payouts are consolidated, covering many individual orders minus various fees. The finance team cannot easily match this single payment against the numerous corresponding Sales Orders and financial documents in SAP ECC. This forces a time-consuming manual effort to reconcile accounts, slows down the month-end close process, and obscures the true profitability of the channel.
Prevention / Action: The integration must be designed to systematically capture the John Lewis Order ID and store it in the purchase order field (`VBKD-BSTKD`) on the corresponding SAP Sales Order. When a payout file is received from John Lewis, the integration logic can then use this unique reference to match settlement lines to the correct financial documents in SAP. This automates the bulk of reconciliation, flagging only genuine exceptions for the finance team to investigate.
Frequently asked questions
Which system should be the source of truth for our stock and price?
SAP ECC must be the single source of truth for all inventory and pricing to maintain data integrity across your business. The integration's primary role is ensuring the Available-to-Promise (ATP) quantity from your SAP Material Master correctly updates the live stock on the John Lewis item record. Managing stock in both systems creates a high risk of overselling, which would breach John Lewis's strict supplier SLAs.
We're managing orders manually. At what point does that become a serious risk?
Manual processing becomes a critical risk once you cannot guarantee John Lewis's strict order-to-despatch SLAs, typically around 15-20 orders per day. Re-keying sales orders from the John Lewis portal into SAP ECC introduces data entry errors and processing delays. This bottleneck directly threatens your supplier performance rating and your ability to scale on the marketplace.
Why do our product listings fail to sync between SAP ECC and John Lewis?
A common failure occurs when SAP's Material Master stores a SKU with internal padding, like leading zeros ('000012345'), but John Lewis requires an exact match to the customer-facing SKU ('12345'). The integration must transform this number before sending it to the John Lewis catalogue, otherwise the item record will not be found. This leads to failed stock updates and inaccurate availability on the marketplace.
How do we handle shipping confirmations if one order is sent in multiple parcels?
This is a critical failure point, as John Lewis's platform typically expects a single, clear despatch confirmation for each order line. Sending multiple partial shipment updates from one SAP Sales Order, often via separate DESADV IDocs, frequently causes update failures. This means the customer does not receive complete tracking information, which directly impacts your supplier metrics and the customer experience.