Microsoft Dynamics 365 and John Lewis Marketplace
Integration Agency & Consultants
Financial reconciliation between John Lewis Marketplace and Dynamics 365 becomes a painful bottleneck when month-end reveals discrepancies between marketplace sales reports and your actual financial postings. At scale, the gap in sales data, marketplace fees, and tax treatments creates source-of-truth ambiguity that slows down your finance team. We synchronise sales, fees, and inventory data so your P&L accurately reflects John Lewis performance. This ensures Dynamics 365 remains the master record for your marketplace financials and fulfilment.
Consulting
We connect Microsoft Dynamics 365 with John Lewis Marketplace, supporting ERP and Marketplaces integration for efficient operations. Our consulting services are invaluable, offering a comprehensive system audit to uncover inefficiencies and integration gaps across Microsoft Dynamics 365, John Lewis Marketplace, ERP, and Marketplaces. This audit empowers both our consultants and your team to take decisive action, ensuring your technology ecosystem runs efficiently. As a result, you can deliver a consistently excellent experience to your customers.
Solution Design
The design for Microsoft Dynamics 365 and John Lewis Marketplace prioritises Dynamics 365 as the master for all product and financial data. We implement a specific sequencing where marketplace orders are injected as Sales Orders only after a SKU-match is verified against the ERP Item Master. While inventory pushes are typically batched to protect ERP performance, fulfilment updates are pushed to John Lewis on a short interval to satisfy marketplace requirements. A key trade-off involves the handling of settlement files. Batching these postings daily ensures easier month-end reconciliation against the general ledger but results in a slight lag in intra-day marketplace sales reporting. This design allows finance to close monthly from Dynamics 365 with high confidence, while the warehouse team works off a synchronised fulfilment queue.
Establishing automated order and fulfilment cycles
Dynamics 365 acts as the master for product, customer, and financial data, while John Lewis Marketplace feeds sales orders and fulfilment updates back into the ERP. We prioritise the accurate mapping of marketplace SKUs to Dynamics 365 item records to prevent stock sync failures. Orders are typically pulled on a defined schedule, triggering the creation of Sales Orders in Dynamics 365 for fulfilment. Once picked and packed, the integration pushes tracking numbers back to John Lewis to trigger customer notifications and marketplace payment cycles. Financial reconciliation is handled by importing settlement data into Dynamics 365 to clear outstanding marketplace invoices.
iPaaS
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations, Microsoft Dynamics 365 and John Lewis Marketplace integrations are delivered efficiently and securely. IPaaS connects ERP and Marketplaces, automating data between Microsoft Dynamics 365, John Lewis Marketplace, and other ERP or Marketplaces. This approach ensures robust data protection, reduces manual effort, and supports compliance, making integrations reliable and future-proof.
Surfacing financial deltas and sync exceptions
Standard dashboards often fail to catch the quiet errors that cause financial drift. Visibility requires monitoring the delta between marketplace sales and Dynamics 365 postings. We focus on surfacing specific exceptions, such as tax mismatches or orders that fail to inject due to SKU mapping errors. By detecting these gaps early, you avoid the compounding debt of hundreds of unreconciled transactions hitting the finance team at month-end. Operational intelligence means seeing exactly where an order is stuck in the pipeline before it impacts a customer or a financial report.
Operational handover for daily reconciliation rituals
Handover involves training your finance, operations, and ecommerce teams to own the new operating model. Finance learns to reconcile marketplace settlement reports directly against Dynamics 365 postings, while operations manages SKU mappings and warehouse code alignment. We provide clear guidance on reading integration alerts so teams can address exception types (such as rejected fulfilments or price mismatches) before they compound. Documentation is strictly operational, detailing daily checks and weekly reconciliation rituals rather than technical code references. This ensures your team runs the business with confidence, knowing exactly who owns each data object and exception.
Long term governance and error monitoring
Ongoing operational ownership prevents the reconciliation debt that often builds in marketplace channels. Our approach includes monitoring for sync failures, tax discrepancies, and inventory mismatches that could impact your standing with John Lewis. Escalation paths are structured so that technical issues are addressed before they disrupt warehouse flows or financial reporting in Dynamics 365. Manageing the integration layer ensures the connection remains stable as your order volume grows.
Common failures
Inventory latency and overselling
Operational impact: When inventory levels in Dynamics 365 are not synchronised to John Lewis in near real-time, overselling becomes inevitable. This creates a poor customer experience and forces the customer service team to process cancellations and refunds. For the fulfilment team, it generates Sales Orders for items that cannot be picked, creating exceptions that require manual resolution in the ERP.
Prevention / Action: The integration must treat Dynamics 365 as the single source of truth for stock levels. Design a process that pushes inventory changes from D365 to John Lewis on a frequent, scheduled basis, considering which D365 warehouse locations contribute to sellable stock. A commercially agreed stock buffer can also be built into the integration logic to provide a safety net against overselling during peak trading.
Payout and order record mismatch
Operational impact: John Lewis provides consolidated payouts covering multiple orders. If the individual Sales Orders in Dynamics 365 do not contain a reliable reference to the original marketplace transaction, the finance team cannot automatically reconcile payments. This results in weeks of manual spreadsheet work, delaying the month-end close and obscuring the profitability of the John Lewis channel.
Prevention / Action: Ensure the John Lewis 'Customer Order Number' is stored in a dedicated field (like 'External Document No.') on every D365 Sales Order created by the integration. The reconciliation process should then use this key to match items from the John Lewis payout report against the corresponding D365 invoices. This provides the foundation for an automated order-to-cash reconciliation.
Failed dispatch notifications
Operational impact: When an order is dispatched from the warehouse, Dynamics 365 is updated correctly but the confirmation is not passed to John Lewis. This failure means the customer is not notified and the marketplace's own service level agreements are breached, risking account penalties. The customer service team receives avoidable 'where is my order?' contacts, increasing operational overhead.
Prevention / Action: The integration must be designed to monitor for dispatch or shipment updates in D365 for any John Lewis order. Once a dispatch record with a tracking number is created, this should trigger an immediate notification to the John Lewis API, using the specific carrier codes they require. Implement robust monitoring and retry logic to ensure these critical updates are always processed successfully.
Incorrect product data publication
Operational impact: If updates to product master data in Dynamics 365 fail to synchronise, incorrect pricing, descriptions, or attributes can be displayed on the John Lewis marketplace. Selling at a wrong price creates immediate financial discrepancies for the finance team. Incorrect product details erode customer trust and can lead to higher return rates if the item received does not match the description.
Prevention / Action: Define Dynamics 365 as the master system for core product data like price and stock. The integration should be built to detect and publish changes from D365 item records to the corresponding John Lewis listings. This process requires strict validation and exception handling to prevent partial updates from corrupting an entire product record.
Frequently asked questions
How do we trace a John Lewis customer order back to our Dynamics 365 sales order?
To ensure full traceability, the integration maps the John Lewis 'Customer Order Number' to a specific field on the corresponding sales order in Microsoft Dynamics 365. Without this link, matching marketplace payout reports to D365 records becomes a manual task for the finance team. This also slows down customer service, who cannot easily find a John Lewis order in the ERP.
How does the integration ensure accurate financial reconciliation at month-end?
The integration helps prevent discrepancies between the John Lewis payout and the sales order values recorded in Microsoft Dynamics 365. It represents each marketplace payout as a corresponding journal entry in Dynamics 365, automatically accounting for sales, commissions, and refunds. This eliminates the need for manual reconciliation in spreadsheets, allowing the finance team to perform the month-end close faster and with greater confidence.
Which system acts as the master for inventory and price?
For this integration, Microsoft Dynamics 365 serves as the operational source of truth for product data, including price lists and inventory levels. The integration ensures that any price or stock update in Dynamics 365 is synchronised with the relevant listings on John Lewis Marketplace. This architecture is crucial for preventing overselling and ensuring price accuracy without manual updates.
What happens if our SKUs in Dynamics 365 don't match the John Lewis listings?
An exact match between the SKU in Microsoft Dynamics 365 and the corresponding product on John Lewis Marketplace is critical for order processing. If they do not match, a sales order will fail to be created in Dynamics 365 after a customer makes a purchase, which halts the entire order-to-cash process. This failure requires manual data correction and creates a risk of not fulfilling an order on time.
Can we use our existing couriers or are there specific fulfilment rules?
The integration must map your carriers to the specific 'Carrier Code' approved by John Lewis Marketplace. When an order is fulfilled in Dynamics 365, the integration must send the correct code to trigger the 'Dispatch Confirmation' on the marketplace. If this mapping fails, the customer will not receive their tracking information and your payment from John Lewis could be delayed.