Stokly ERP and John Lewis Marketplace
Integration Agency & Consultants
Operational drag begins the moment John Lewis Marketplace sales volume outpaces your team's ability to manually update Stokly ERP. When inventory levels drift and stockout risks increase, the manual reconciliation of marketplace orders becomes a commercial risk rather than just a task. We connect Stokly ERP to John Lewis to automate inventory synchronisation and order fulfilment, ensuring your source of truth for stock remains accurate across every channel. This protects your delivery promises and prevents the penalties associated with overselling on the John Lewis platform.
Auditing your Stokly data architecture
We connect your Stokly ERP with John Lewis Marketplace quickly, ensuring your ERP and Marketplaces work together efficiently. Our consulting services are valuable because our system audit identifies integration gaps and inefficiencies, enabling both our consultants and your team to take decisive action. This helps your Stokly ERP and John Lewis Marketplace integrations run smoothly, supporting your wider ERP and Marketplaces ecosystem. As a result, you can deliver a reliable, high-quality experience to your customers and keep your technology running at its best.
Solution Design
Designing the Stokly ERP and John Lewis Marketplace integration requires clear ownership of the order to cash cycle. We establish Stokly as the master for product and inventory data, pushing availability to John Lewis on a defined schedule. A central design trade-off involves inventory sync frequency. While rapid updates reduce overselling risk, they can increase system load during peak periods. In most setups, we implement protective stock buffers and throttled updates to balance accuracy with stability. Orders flow into Stokly for fulfilment and financial booking, ensuring the ERP remains the source of truth for your accounts. We sequence inventory and order flows first to stabilise the core operation before automating secondary processes. This design ensures finance closes the month using Stokly reports while warehouse operations work from consolidated data, preventing manual reconciliation across marketplace portals.
Syncing stock levels and order records
The integration transforms John Lewis Marketplace data into Stokly-compatible records. Stokly ERP serves as the authority for SKUs and available stock, pushing updates to the marketplace on a defined schedule to prevent overselling. Orders flow from John Lewis into Stokly, where they are managed for fulfilment. Once dispatched, the tracking details and fulfilment status flow back to the marketplace to trigger notifications. The process includes a validation step where order values are checked against the ERP's requirements before the record is finalised. This helps prevent errors and ensures that marketplace sales are accurately reflected in your financial reporting within Stokly.
Secure orchestration on accredited platforms
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient delivery of Stokly ERP and John Lewis Marketplace integrations. IPaaS simplifies connecting Stokly ERP with Marketplaces like John Lewis Marketplace, ensuring ERP data flows securely. Benefits include centralised management, robust compliance, and reduced risk, making Marketplaces integration straightforward and secure while meeting the minimum requirements of ISO 27001 and SOC 2 and above.
Surfacing operational exceptions and data gaps
Dashboards often only show that a sync attempted to run, rather than confirming data accuracy. We focus on surfacing operational exceptions, such as when a John Lewis order fails to map to a Stokly SKU or when inventory levels diverge between systems. We aim to detect failed transformations before they create reconciliation gaps in your ERP. This visibility allows your team to identify specific errors, such as missing data or VAT mismatches, without digging through complex logs. Identifying these issues early prevents small sync failures from compounding into major stockouts or financial discrepancies that would otherwise only be discovered during month-end close.
Handovers for finance and operations teams
Post-launch, ownership of the Stokly ERP and John Lewis Marketplace integration typically transfers to your finance, ops, and ecommerce teams. We provide an operational playbook that defines where data lives, how to monitor order flows, and who owns specific exception types. Your team learns what to check on a defined schedule to ensure John Lewis orders have successfully synchronised into Stokly for fulfilment and how to handle routine reconciliation tasks. This documentation is written for the people running the business rather than a technical archive. Training is anchored in your design decisions, ensuring your team can manage the operating model for routine monitoring or alert response.
Managing post-launch stability and governance
Post-launch, we provide operational oversight to manage integration health between Stokly and John Lewis. We monitor for sync failures and data discrepancies, specifically tracking inventory updates and fulfilment status to prevent marketplace penalties. Our support model categorises exceptions by their operational impact, ensuring critical stockout risks or fulfilment delays are prioritised for resolution. We act as an extension of your operations team, adjusting logic as volumes increase to prevent reconciliation debt from accumulating as you scale.
Common failures
Inventory latency and overselling
Operational impact: Stokly ERP's stock level for a SKU becomes higher than the actual available inventory, often due to timing lags in accounting for sales from other channels. John Lewis Marketplace accepts orders against this phantom stock, leading to overselling. This forces the customer service team to cancel sales orders, directly impacting customer satisfaction and your marketplace performance rating.
Prevention / Action: Stokly ERP must be the single source of truth for inventory. The integration should push frequent, delta-only stock updates to John Lewis. A modest, sellable stock buffer should be configured in Stokly, not the integration layer, providing a safety net against race conditions for fast-moving SKUs. Failed updates must trigger an immediate alert for the operations team.
Dispatch confirmation failures
Operational impact: An Item Fulfilment is created in Stokly ERP, but the corresponding dispatch confirmation and tracking number fails to update the John Lewis Marketplace order. This breaches marketplace SLAs for dispatch communications and can delay the release of payment. The customer service and operations teams are left to manually update John Lewis, creating unnecessary administrative work.
Prevention / Action: The integration must maintain a strict mapping of carrier service names between Stokly and the approved John Lewis carrier list. The process must be sequenced: the dispatch confirmation to John Lewis should only be triggered after the Item Fulfilment is successfully created in Stokly. Monitor API responses from John Lewis and create an exception queue for any rejected confirmations.
Order reference and reconciliation gaps
Operational impact: The John Lewis 'Customer Order Number' is not correctly captured on the corresponding Sales Order in Stokly ERP. When the finance team receives the payout statement from John Lewis, there is no shared reference to automate matching. This forces a laborious, manual reconciliation of payout data against potentially thousands of sales orders, delaying month-end financial closing.
Prevention / Action: The integration must be designed to durably store the John Lewis customer order number in a dedicated 'External Reference' field on the Stokly Sales Order at the time of creation. This provides a persistent key for all downstream processes. This ensures the finance team can reliably link payout transactions to the original sale and associated journal entries.
SKU data mismatch
Operational impact: A SKU in Stokly does not exactly match the listing on John Lewis Marketplace, often due to a manual change on one system. This breaks the link for that product. Inventory updates from Stokly fail to apply, and sales orders from John Lewis fail to create, resulting in missed sales and apparent stockouts which require manual detection by merchandising or ops teams.
Prevention / Action: Establish Stokly ERP as the catalogue master. Any changes to SKUs or critical product identifiers must be made in Stokly and propagated to John Lewis via the integration. The integration should treat SKU as the immutable join key; if an order arrives for a SKU not found in Stokly, it must be flagged as an exception rather than being ignored or partially processed.
Frequently asked questions
Which system should be the master source of truth for inventory levels?
Stokly ERP must act as the definitive master for all inventory data. The integration then pushes available stock quantities from Stokly ERP to John Lewis Marketplace on a frequent, scheduled basis. This ensures your John Lewis listings accurately reflect warehouse stock, preventing overselling and protecting your seller rating.
We manage John Lewis orders manually in Stokly ERP now. When does this typically become a problem?
This operating model becomes unsustainable as John Lewis Marketplace sales volume grows. Teams find that manual sales order creation in Stokly ERP leads to fulfilment delays and errors in stock reconciliation. This directly risks poor seller performance metrics on the marketplace and creates unnecessary operational overhead.
What happens if a SKU in Stokly ERP doesn't perfectly match the John Lewis Marketplace listing?
Even minor mismatches between the Stokly ERP item record SKU and the corresponding John Lewis Marketplace SKU will break the stock synchronisation for that product. This can lead to that item showing as out of stock on the marketplace when you have plenty, or worse, overselling an item you do not have. This is a common failure point that requires careful initial data mapping and ongoing governance.
Why would shipment confirmations from Stokly ERP fail to update John Lewis Marketplace?
This failure commonly occurs when the carrier or shipping service recorded in Stokly ERP does not exactly match a name on the approved John Lewis 'Carrier List'. The integration must map these values precisely for an Item Fulfilment to successfully trigger the dispatch confirmation. If it fails, the customer is not notified of shipment and your account metrics can be negatively affected.
How does the integration handle customer returns and refunds?
A robust integration ensures a return initiated on John Lewis Marketplace creates the corresponding return authorisation in Stokly ERP, instructing your warehouse on the incoming item. Once the item is received, Stokly ERP can update its inventory count, making the SKU available for resale. This prevents returned stock from getting lost and ensures financials are updated correctly for the refund.