Adobe Commerce and John Lewis Marketplace
Integration Agency & Consultants
Operational risk between Adobe Commerce and John Lewis Marketplace peaks when marketplace orders outpace manual inventory updates. At scale, discrepancies between the Adobe Commerce catalogue and John Lewis stock levels often lead to overselling and cancelled orders. By establishing Adobe Commerce as the central source of truth for inventory and order flow, teams can maintain fulfillment accuracy across both channels without the manual overhead that creates operational drag.
Auditing your commerce and marketplace setup
We connect your Adobe Commerce and John Lewis Marketplace integration swiftly, supporting your ecommerce and marketplaces strategy. Our consulting services are invaluable, with our system audit services providing a thorough review of your Adobe Commerce and John Lewis Marketplace setup. This enables both our consultants and your team to take decisive action, ensuring your ecommerce and marketplaces technology ecosystems run efficiently. As a result, you can deliver a great experience to your customers and maintain a competitive edge in today’s demanding digital landscape.
Solution Design
For the Adobe Commerce and John Lewis Marketplace integration, we typically establish Adobe Commerce as the central source of truth for product data and inventory levels. A primary design decision involves the inventory sync frequency. We often recommend a regular push to John Lewis to protect against overselling, acknowledging the trade-off that constant synchronisation requires careful management of API limits. Orders are sequenced to flow into Adobe Commerce as the master for fulfilment, with status updates returning to the marketplace only once tracking is confirmed. This design ensures your finance team closes month-end based on verified Adobe Commerce records, while operations maintain channel-specific customer communications, ensuring a clean separation of concerns and data integrity across your retail stack.
Syncing inventory and order records securely
The integration establishes Adobe Commerce as the authoritative source for your product catalogue and inventory. Updates are typically pushed to John Lewis Marketplace on a defined schedule to prevent overselling, while orders placed on the marketplace are synchronised back into Adobe Commerce for fulfilment. We prioritise data integrity by ensuring marketplace mappings align with your Adobe Commerce item records. Monitoring is built into the flow, surfacing synchronisation issues or rejected marketplace orders before they impact your shipping performance. This structured movement of data ensures that your inventory levels remain accurate across both channels, shielding your reputation from the consequences of stock-outs.
Secure orchestration via enterprise grade IPaaS
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Adobe Commerce and John Lewis Marketplace, supporting Ecommerce and Marketplaces growth. IPaaS simplifies connecting Adobe Commerce to John Lewis Marketplace, reducing risk and complexity for Ecommerce businesses. The platform’s robust security, scalability, and centralised management ensure Marketplaces integrations are delivered with confidence, meeting the minimum requirements of ISO 27001 and SOC 2 and above.
Monitoring synchronisation gaps and validation errors
Standard dashboards often mask the quiet failures that degrade marketplace performance. True visibility requires surfacing hidden issues, such as product attributes that fail John Lewis validation or inventory updates that never reached the marketplace. Our approach goes beyond high-level status lights to identify specific synchronisation gaps and reconciliation discrepancies early. By monitoring the integration at the object level, we catch mismatched SKU data or stuck orders before they compound into customer cancellations and marketplace penalties. You gain a clear view of where truth resides and where the gaps are, allowing your team to act on exceptions rather than digging for data.
Hands-on handover for retail operations teams
Handover focuses on the teams running the daily operation: Ecommerce, Ops, and Finance. We provide documentation that explains the operating model in plain English, defining exactly where data objects like Sales Orders and SKUs originate. Your team learns what to check daily, such as pending marketplace shipments, and how to interpret alerts from the integration layer regarding synchronisation gaps. We clarify who owns specific exception types, ensuring customer service knows when to intervene on an order delay. This is operational documentation for people running a business, not a technical archive for IT. It ensures your team can confidently manage the John Lewis channel as part of your standard retail workflow.
Proactive maintenance and marketplace health monitoring
Support moves beyond reactive troubleshooting to proactive operational ownership. We monitor the integration for data drift, stuck orders, and field validation failures that could lead to marketplace penalties. When issues occur, our process ensures they are addressed based on their impact on your shipping performance and financial reporting. By providing ongoing monitoring and clear exception handling, we ensure that as your John Lewis Marketplace presence grows, your integration infrastructure remains a stable foundation rather than a source of operational drag.
Common failures
Inventory latency and overselling
Operational impact: Stock levels from Adobe Commerce fail to synchronise with John Lewis Marketplace in a timely manner. This leads to selling SKUs that are out of stock, forcing order cancellations which damage seller ratings and increase the workload for customer service teams. Fulfilment teams may also waste time attempting to pick and pack orders for unavailable items.
Prevention / Action: Establish Adobe Commerce as the single source of truth for inventory levels. The integration should use event-driven updates to push stock changes for specific SKUs to the marketplace immediately. For fallback batch processing, ensure the schedule is frequent enough to minimise risk during peak trading and includes robust queue handling to manage API rate limits or retry failed updates.
Failed dispatch notifications
Operational impact: When an order is dispatched from the warehouse and the shipment is created in Adobe Commerce, the confirmation message fails to update John Lewis. This typically occurs because the carrier name does not exactly match the approved John Lewis 'Carrier Code' list. This failure risks breaching marketplace service level agreements, delaying customer notifications, and can impact the timing of payouts.
Prevention / Action: The integration logic must include a mapping table that translates the carrier descriptions used in Adobe Commerce to the specific carrier codes required by the John Lewis API. This mapping should be actively maintained. The integration process must also include exception handling to flag any unmapped carriers for immediate review by the operations team, preventing dispatch updates from failing silently.
Inconsistent product data
Operational impact: Discrepancies between product attributes in Adobe Commerce and the offer data on John Lewis cause order synchronisation to fail. This is particularly common when SKUs do not have an exact one-to-one match or when complex product types like bundles or items with custom options are used. These failures prevent Sales Orders from being created in Adobe Commerce, requiring manual data correction and order processing by the ecommerce team.
Prevention / Action: Define Adobe Commerce as the master system for all core product catalogue data. The integration logic should be designed to filter or transform product types that are not directly supported by the marketplace API into a compatible format before attempting to synchronise. Implement a scheduled full catalogue audit to identify and correct data drift between the two platforms automatically.
Mismatched refund and credit data
Operational impact: Refunds or partial refunds processed via Credit Memos in Adobe Commerce do not automatically trigger the required return or refund status in John Lewis Marketplace. This creates significant reconciliation work for the finance team, who must manually align payout reports against refund journals. It can also lead to an inconsistent customer experience, where a refund is confirmed in one system but not the other.
Prevention / Action: The integration design must map the entire returns lifecycle, including the states for partial and full refunds. When a Credit Memo is issued in Adobe Commerce, the integration must trigger the precise API call required by John Lewis to process that refund. Implement monitoring and exception reports for any refund transaction that fails to synchronise, enabling a finance or CX team member to investigate and resolve issues quickly.
Frequently asked questions
How do we prevent overselling on John Lewis if our Adobe Commerce website is also taking orders?
Adobe Commerce is established as the central source of truth for inventory in this operating model. When a sales order is created in either Adobe Commerce or John Lewis Marketplace, the available stock level is updated in Adobe Commerce first. This new total is then synchronised with the John Lewis listing, preventing the same unit from being sold to two different customers.
Where should we create new products, and how do they get to John Lewis?
All new products should be created in Adobe Commerce, as it acts as the master item record. Once you build the new product in Adobe Commerce with its SKU, pricing, and imagery, the integration automatically pushes the data to create a corresponding product listing on John Lewis Marketplace. This ensures your catalogue is consistent and avoids manual data entry on the marketplace.
We use 'Custom Options' extensively in Adobe Commerce. Will these cause issues?
Yes, this is a common failure point if not handled correctly. Orders containing products with Adobe Commerce 'Custom Options' can fail to sync, because the data does not map to a standard field in John Lewis Marketplace. The integration must be configured to correctly interpret these options to ensure the sales order and its line items are created properly in the target system.
How precisely do SKUs need to match between Adobe Commerce and John Lewis?
The SKUs must match exactly for the stock sync to function correctly. A frequent error occurs if the SKU on the John Lewis item record contains spaces or special characters that are absent in the master Adobe Commerce SKU. This mismatch breaks the link between the two, causing the inventory level for that specific product to become desynchronised.
How are refunds handled if we process them inside Adobe Commerce?
This requires careful configuration, as a standard Adobe Commerce workflow might not complete the process in John Lewis. For example, creating a partial Credit Memo in Adobe Commerce does not automatically trigger the corresponding refund record and status update in John Lewis Marketplace. The integration must explicitly map these events to ensure the returns handling process is completed on both sides and avoids reconciliation problems.