Microsoft Dynamics Business Central and John Lewis Marketplace
Integration Agency & Consultants
At low volume, teams can hide the gaps between Business Central and John Lewis Marketplace. At scale, inventory latency begins to lag behind real sales, causing overselling and customer dissatisfaction. This integration connects John Lewis directly to your ERP, ensuring Sales Orders post correctly and inventory levels remain synchronised. By establishing an authoritative source of truth, you prevent reconciliation debt in your finance reporting and protect your seller metrics on the marketplace. This transition usually becomes urgent when the warehouse can no longer rely on the stock numbers shown in Business Central.
Auditing system gaps and integration requirements
Connect Microsoft Dynamics Business Central with John Lewis Marketplace quickly and reliably. Our consulting services are invaluable for businesses integrating ERP systems like Microsoft Dynamics Business Central with Marketplaces such as John Lewis Marketplace. Our system audit services uncover inefficiencies and integration gaps, empowering both our consultants and your team to take decisive action. This ensures your ERP and Marketplaces work together efficiently, supporting a smooth-running tech ecosystem and helping you deliver an excellent customer experience.
Solution Design
Design decisions for this pair focus on maintaining Business Central as the system of record for inventory while John Lewis owns the initial customer transaction. We typically push inventory updates on a defined schedule rather than in real-time. This trade-off protects ERP performance during high-volume events, as continuous real-time lookups can create operational latency for warehouse teams. We sequence Sales Order imports to move immediately, while financial settlements are batched to match John Lewis's remittance cycle. This design creates a clear ownership boundary where operations work from ERP stock levels and finance relies on automated settlement mapping to resolve the payout relationship. This ensures stable performance during peak trading.
Syncing marketplace orders with warehouse workflows
The integration between John Lewis Marketplace and Business Central ensures marketplace orders follow your ERP fulfilment logic. Orders sync into Business Central as Sales Orders, allowing warehouse teams to pick and pack within a single system of record. To prevent overselling, Business Central acts as the inventory master, pushing available-to-sell levels to John Lewis at defined intervals. When a Warehouse Shipment is posted, the tracking ID and carrier code flow back to the marketplace. This ensures the marketplace stays in step with the warehouse. For finance, mapping marketplace fees directly to the general ledger reduces the effort required to reconcile settlement payouts.
Orchestrating secure flows on compliant middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Microsoft Dynamics Business Central and John Lewis Marketplace, connecting ERP and Marketplaces with ease. IPaaS platforms simplify complex ERP and Marketplaces data flows, ensuring Microsoft Dynamics Business Central and John Lewis Marketplace integrations are robust, scalable, and compliant. This approach reduces risk, supports business growth, and guarantees data protection as a minimum requirement.
Monitoring SKU mapping and delivery exceptions
Standard dashboards often signal that a connection is active while missing the underlying data gaps that disrupt operations. Data issues occur when a Sales Order appears to have synced, but a SKU mismatch or invalid carrier code prevents it from being processed by the marketplace. We focus on surfacing these specific exceptions early. This involves monitoring for inventory sync failures that lead to overselling and ensuring that marketplace tracking updates are confirmed by the sync logic. By identifying these issues at the point of failure, teams can resolve mapping errors before they result in customer delivery delays.
Operational handover for finance and logistics
Handover ensures finance, operations, and ecommerce teams own the logic of the Business Central and John Lewis connection. Ecommerce teams manage marketplace availability while warehouse operations own the fulfilment loop. Finance typically performs reconciliation of settlement files against Business Central Sales Invoices. We provide documented operating models that define where each data object lives and how to respond to specific alerts, such as SKU mapping errors or failed tracking exports. This documentation is written as a practical reference for the people running the business. Training is anchored in the specific design decisions made for your workflow.
Maintaining data integrity and tracking syncs
Support focuses on maintaining data integrity between Business Central and John Lewis. We prioritise exceptions that impact your marketplace standing, such as order import failures or tracking sync errors. By monitoring for data issues, we identify mapping gaps before they lead to manual work for your team. Our model ensures that while we handle the technical recovery of failed syncs, your operations team maintains visibility through clear alerts. This allows them to focus on fulfilment while we preserve the data flow and protect the accuracy of your financial records.
Common failures
Inventory latency and overselling
Operational impact: Stock levels in Business Central become disconnected from available-to-sell quantities on John Lewis. This leads to overselling and cancelled orders. During peak, this lag creates a situation where the integration appears active but stock is already depleted.
Prevention: Establish Business Central as the authoritative source for stock. Implement a safety buffer in the integration logic to protect the marketplace and ensure stock pushes are regularly triggered.
Carrier mapping failures
Operational impact: John Lewis requires specific carrier codes for dispatch confirmation. If Business Central carrier descriptions are not mapped correctly, fulfilment updates fail. This creates a gap where the customer receives no notification and the marketplace flags the account for late shipping.
Prevention: Maintain a mapping table that translates Business Central carrier methods to the approved John Lewis codes. Any record that fails the mapping must be flagged for review.
Settlement reconciliation
Operational impact: John Lewis payouts consolidate multiple orders and fees into a single remittance. Finance teams often face manual work at month-end unpicking these discrepancies between marketplace reports and the ERP records.
Prevention: The integration should assist in pulling settlement data to automate the creation of journals in Business Central. This helps break out sales and fees, matching the payout against specific orders.
Frequently asked questions
How does the integration prevent overselling on the John Lewis Marketplace?
Stock level drops in Business Central below a defined safety buffer can be configured to trigger an immediate inventory sync to the John Lewis Marketplace. By using Business Central as the master record, the integration pushes available stock levels to prevent overselling. High volume spikes are typically managed via a queue to protect against sync delays during peak trading.
How are shipment updates managed to avoid marketplace penalties?
Accuracy is critical because tracking numbers must usually be pushed to John Lewis before the order status is finalized in the ERP. Failing to sync tracking correctly can trigger automated refund processes within the marketplace. In many implementations, the workflow prioritises shipping all order lines together to ensure the marketplace status remains in step with Business Central.
What happens if product data is incorrectly mapped?
Mismatches between Business Central and the John Lewis catalogue can lead to list failures or incorrect pricing. The integration typically uses the Business Central SKU as the primary identifier. To avoid duplicate record errors, the system must also correctly handle the marketplace order ID within the Business Central external document fields during the invoicing process.
How does the integration handle financial reconciliation?
The integration is designed to align with the John Lewis settlement report, which often acts as the definitive source for tax liability. By automating the mapping of settlement files to Sales Invoices in Business Central, finance teams can reduce the manual work required to reconcile payouts. Transactions are typically grouped under a designated marketplace account to keep the ledger clean.