What a The Edge by John Lewis integration gives you.
The Edge orders land in your commerce platform and ERP with full line-item detail and correct fulfillment instructions. Duplicate detection and order acknowledgement confirmation give you confidence that nothing is lost between channel and warehouse.
Channel-specific stock buffers and allocation rules prevent oversell across The Edge and your own direct storefronts. Real-time inventory updates keep The Edge listings honest and reduce customer cancellations due to out-of-stock surprises.
Tracking numbers and dispatch confirmations synchronise back to The Edge within minutes of fulfillment, improving customer satisfaction and reducing support inquiries from John Lewis Partnership buyers.
Product lists, descriptions, images and pricing update on The Edge as you publish changes in your core system. Transformation rules ensure John Lewis Partnership formatting requirements are met without manual override.
Orders sync to your ERP with The Edge attribution and commission codes, enabling straightforward channel revenue reporting and settlement accounting with John Lewis Partnership.
Where a The Edge by John Lewis integration earns its place.
If two or more of these are true, the integration usually pays for itself quickly.
Where off-the-shelf connectors fall short.
Vendor connectors are fine for simple cases. Here's where the real ones need more.
The Edge does not automatically reserve inventory across your other sales channels. You must define and maintain stock buffers, channel allocation rules and override thresholds in your integration layer to prevent simultaneous oversell across The Edge and direct channels.
The Edge enforces John Lewis Partnership formatting rules for product names, descriptions, images and attributes that may differ from your primary commerce platform. You must maintain a transformation layer that maps your canonical product data to The Edge's required schema.
Order ingestion does not include automatic retry, idempotency or exception queue management. Failed or duplicate orders can slip through without detection unless you build explicit monitoring and manual intervention protocols.
The Edge pricing is typically managed via periodic batch uploads rather than live negotiation. Dynamic or customer-specific pricing adjustments require manual intervention or custom integration logic outside The Edge's native capabilities.
The Edge marketplace provides basic return requests, but chargeback disputes, merchant performance ratings and account-level credits may not flow automatically to your ERP, creating reconciliation gaps at month-end.
Stock buffers and channel allocation rules live outside the marketplace platform itself, creating governance complexity that manual spreadsheets cannot sustain at scale.
Where this integration sits in your estate.
The Edge by John Lewis holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.
Commerce platform agnostic. Connect The Edge by John Lewis across your entire technology stack.
- Marketplace order ingestion and order acknowledgement
- Channel-specific buyer profiles and purchase history
- Returns and refund requests from The Edge buyers
- Merchant performance ratings and account standing
- Dispatch confirmation and tracking data publishing back to buyers
- Canonical product data, descriptions and images
- Base inventory levels before channel allocation
- Pricing strategies and promotion calendars
- Order fulfillment instructions and warehouse operations
- Refund processing and credit memo generation
- Channel attribution and revenue reporting
Systems this integration usually sits next to.
Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.
- Adobe Commerce
- Magento Open Source
- Shopify Plus
- BigCommerce
- Other storefronts
- ERP (Sage, Infor, SAP)
- PIM or product content management
- Order management system
- Fulfillment or WMS
- Carrier integration (DPD, DHL, Royal Mail)
- Accounting / finance ledger
Not sure if this works with your stack?
Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.
The data flows we wire.
Each flow has a direction and an owner. We agree both before a line of code is written.
How iWeb configures the integration around your business.
Same method on every integration. The decisions come before the code.
- 01Design stock allocation rules
We define channel-specific stock buffers, allocation percentages and override thresholds that prevent oversell across The Edge and other channels while maximizing throughput on each channel.
- 02Build order ingestion and deduplication
We implement order landing logic that captures The Edge order metadata, detects duplicate submissions and routes orders into your commerce platform and ERP with full traceability and reconciliation fields.
- 03Transform and publish product data
We create mappings between your canonical product attributes and The Edge schema, automating channel-specific naming, description, image and pricing transformations on each publish cycle.
- 04Monitor and alert on failures
We instrument the integration with alerting for stuck orders, stale inventory syncs, failed dispatch confirmations and pricing mismatches. Exception queues surface issues before they escalate to customer complaints.
- 05Support returns and refund workflows
We connect return requests from The Edge to your fulfillment and ERP systems, tracking refund status and ensuring credits are reflected on customer accounts and John Lewis Partnership settlement invoices.
Who owns what.
The single most important table in any integration. One system owns each field; everything else reads it.
Built this before
iWeb has implemented multi-channel marketplace integrations across B2B and B2C estates where stock allocation, order ingestion and dispatch synchronisation are critical to uptime and customer trust. We understand how The Edge sits alongside your ERP, fulfillment and direct commerce channels.
What we test before launch.
Every one of these is rehearsed before a customer ever sees the integration.
Common risks and where they bite.
We name these on day one. A risk written down is a risk you can plan around.
If inventory levels are not buffered and allocated per channel, The Edge and your direct storefront can sell the same stock units simultaneously, leading to backorders, cancellations and customer complaints.
Failed order submissions or missing order acknowledgement logic can leave orders stranded in The Edge without fulfillment instruction reaching your warehouse, causing late dispatch and customer escalations to John Lewis Partnership.
If inventory syncs are infrequent or product transformations break, The Edge listings become out of date or incorrectly formatted, leading to customer confusion, returns and merchant performance penalties.
If dispatch confirmations fail to flow back to The Edge, buyers remain unaware of shipment status. This creates support burden and damages your reputation as a merchant on the John Lewis Partnership platform.
If orders are not tagged with The Edge attribution or commission codes reach your ERP incorrectly, month-end settlement reconciliation with John Lewis Partnership becomes manual, error-prone and time-consuming.
If return requests from The Edge do not sync to your fulfillment and accounting systems, refunds may be processed outside ERP controls, creating liability gaps and unreconciled credits on customer accounts.
Relevant services and sectors.
Common questions about The Edge by John Lewis integrations.
How do we prevent overselling the same stock on The Edge and our direct storefronts?
We define channel-specific stock buffers and allocation rules in the integration. Raw inventory from your ERP is reduced by a reserved percentage for each channel before publishing to The Edge. Real-time stock syncs ensure The Edge reflects only available quantity after other channel allocations.
Can we use different prices on The Edge than on our direct channels?
Yes. We maintain separate pricing rules per channel in the integration layer. The Edge pricing is applied during product publication, allowing you to set competitive or margin-optimized prices per channel without modifying your core pricing engine.
How do orders from The Edge reach our fulfillment warehouse?
Orders flow from The Edge into your commerce platform, then to your order management system and ERP. We ensure each order includes The Edge order reference, customer shipping address and any special fulfillment instructions, so your warehouse can pick and ship without ambiguity.
What happens if an order fails to ingest from The Edge?
We implement exception queues and alerting that surface failed orders within minutes of submission. A manual review process allows operators to retry or escalate the order. Every ingested order is logged with its The Edge order ID, so reconciliation is possible.
How quickly do tracking numbers reach The Edge customers?
Once your fulfillment system generates a tracking number, we sync it back to The Edge typically within 5-15 minutes, depending on your fulfillment system's API and refresh frequency. Customers see shipment status on The Edge within the same window.
How are returns and refunds handled between our ERP and The Edge?
Return requests from The Edge flow into your order management system. Once processed and approved in your ERP, the refund status and reason code sync back to The Edge. This ensures customers see return status and your accounts record the credit correctly.
Who owns the product descriptions and images on The Edge?
Your product and merchandising team maintains canonical descriptions and images in your PIM or commerce platform. The integration automatically transforms and publishes them to The Edge per John Lewis Partnership requirements. Manual overrides can be applied if needed.
How do we reconcile The Edge orders for commission settlement with John Lewis Partnership?
Each order ingested from The Edge carries a The Edge order reference and is tagged with the channel code in your ERP. Month-end settlement queries filter by channel to calculate total sales, commissions and chargebacks due, simplifying reconciliation.
Can we halt The Edge order flow if our ERP goes down?
Yes. We implement circuit-breaker logic that pauses order ingestion if your ERP is unreachable, preventing orphaned orders. Once connectivity is restored, orders are re-attempted in sequence. You can also manually trigger a hold via monitoring dashboards.
How often do product and inventory updates publish to The Edge?
We typically sync product and inventory on a scheduled cycle (e.g., every 15-30 minutes) or event-driven (e.g., when stock falls below threshold). Frequency is configurable based on your business needs and The Edge's API rate limits.
What data does The Edge require for each product listing?
The Edge requires SKU, title, description, images, price, inventory quantity and category. Additional attributes (brand, size, colour, etc.) depend on product category. We maintain a mapping schema that transforms your canonical data to match The Edge requirements.
How do we monitor the health of The Edge integration?
We implement dashboards showing order ingestion rate, inventory sync latency, dispatch confirmation lag and error counts. Alerts fire if order processing stalls, inventory publishes fail or tracking data does not return to The Edge on time.
Can we run a pilot with a subset of inventory on The Edge?
Yes. We can filter products by category, brand or SKU range during the pilot, publishing only a subset to The Edge while the integration runs in shadow mode for others. Once confident, you can expand to full catalogue.
Projects with a similar shape.
A foodservice platform rebuilt around product data, account ordering and operational control.
Foodservice ordering supported by cleaner product data, account workflows and connected operations.
A builders' merchant PWA built around branch stock, trade accounts and customer ordering.
Merchant trading supported by branch stock visibility, trade accounts and mobile-first ordering.
A multi-merchant PWA built around branch stock, trade accounts and product data.
Timber and merchant trading supported by branch stock visibility and account-led ordering.