Veeqo and John Lewis Marketplace
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Inventory latency and overselling
Operational impact: Delayed inventory updates from Veeqo to John Lewis Marketplace lead to overselling. This damages seller performance metrics and consumes customer service team resources managing cancelled Sales Orders. At scale, this fire-fighting erodes profitability and requires constant manual intervention from the operations team.
Prevention / Action: Design the process with Veeqo as the definitive source of truth for stock. Prioritise frequent, scheduled delta-syncs of inventory levels, supplemented by event-driven updates for stock adjustments if the architecture permits. The integration must have robust error logging to catch and alert on sync failures, preventing discrepancies from persisting.
Failed dispatch notifications
Operational impact: John Lewis has strict Service Level Agreements for dispatch confirmations. If Veeqo marks an order fulfilled but the update to the marketplace fails, customer notifications are delayed and, crucially, so is the payout. This directly impacts the finance team's cash flow reconciliation and can lead to account penalties for poor performance.
Prevention / Action: Maintain a strict mapping between carrier names used in Veeqo and the approved carrier codes specified by John Lewis. The integration logic must be designed to validate the presence of a valid tracking number and carrier before attempting to send a dispatch confirmation. Failed updates should be added to an exception queue for immediate operator review.
SKU data mismatch
Operational impact: If SKUs are not an exact character-for-character match between Veeqo and John Lewis, inventory and pricing updates fail silently. This leads to underselling available items or listing products at incorrect prices, directly affecting revenue. Merchandising and operations teams are then forced to spend significant time manually auditing SKU data to find and fix the source of the errors.
Prevention / Action: Define Veeqo as the master system for all product SKU data. Before activating the integration, conduct a full data audit to align all SKUs. The integration's monitoring should explicitly report on 'SKU not found' errors, creating a clear exception report for the e-commerce team to action rather than letting failures accumulate.
Order cancellation and return sync failures
Operational impact: Cancellations or returns initiated on John Lewis might not automatically update the order status in Veeqo. This can result in the fulfilment team picking, packing, and shipping an order that the customer has already cancelled, incurring wasted shipping costs and labour. It also delays the CX team processing the refund and prevents the stock from being returned to sellable inventory promptly.
Prevention / Action: The integration must poll for updates to existing orders, not just for new order creation. The logic should be designed to recognise a 'Cancelled' status on John Lewis and trigger a corresponding hold or cancellation in Veeqo, provided the Item Fulfilment process has not begun. Processes for returns must be clearly defined to ensure stock is correctly received back into Veeqo inventory.
Frequently asked questions
If we use Veeqo for fulfilment, can we trust it as the single source of truth for John Lewis Marketplace inventory?
Yes, the recommended operating model designates Veeqo as the master system for inventory levels. Veeqo continuously pushes stock updates to John Lewis Marketplace, ensuring the quantity shown on each listing is accurate. New Sales Orders from the marketplace are then sent back to Veeqo for your team to pick, pack, and dispatch.
What is the most common reason for overselling on John Lewis Marketplace when using Veeqo?
The most frequent cause is a failure in the stock sync process, often originating from a mismatched SKU between the two systems. If the SKU in Veeqo does not perfectly match the John Lewis listing, stock level updates for that item will fail. This discrepancy can easily lead to overselling, resulting in cancelled Sales Orders and potential damage to your seller rating.
How does the integration handle sending despatch information from Veeqo back to John Lewis?
To meet John Lewis's strict operational standards, every Item Fulfilment from Veeqo must include a valid tracking number and a carrier name from their approved list. If the carrier name used in Veeqo for a shipment does not exactly match an entry on the John Lewis list, the despatch confirmation will fail. This means the customer is not notified and your team must manually correct the fulfilment record to resolve the error.
What happens if a product is returned or an order is cancelled?
This depends on the operating model, but typically a return processed in Veeqo will trigger a stock adjustment to make the item available for sale again. It is crucial that the corresponding refund and return status is also correctly processed on John Lewis Marketplace to maintain accurate records. Failure to manage the returns handling process correctly across both systems can lead to inaccurate inventory and poor customer experience.