Supply Lens automates the John Lewis Partnership supplier document cycle. Purchase orders, sales reports and inventory reports in, invoices out, mapped to your ERP or IMS with the right branch codes, supplier IDs and John Lewis tolerance rules built in.
John Lewis's flow looks straightforward on paper. The work is in the supplier and branch codes, the tolerance rules on every invoice and landing the sales and inventory reports somewhere your team will actually use them. Get any of it wrong and you eat a deduction. Supply Lens is configured for those rules out of the box.
John Lewis receive supplier documents through a managed network rather than a point-to-point link. Supply Lens holds that network relationship, the routing and the partner profile on your behalf, so you need no account, subscription or gateway of your own.
John Lewis and Waitrose sit under the same Partnership infrastructure, sharing location structures, supplier codes and routing. If you already trade with one, you are most of the way to trading with the other, and Supply Lens carries the same configuration across both.
John Lewis identifies products by GS1 EAN and an internal product reference. Supply Lens maintains a cross-reference table mapping both to your own item codes, so the order lands correctly in your ERP regardless of which identifier John Lewis sends.
John Lewis applies strict invoice matching on price and quantity. Supply Lens validates the invoice against the originating purchase order and your agreed cost list before transmission, flagging any discrepancy for review rather than sending it and risking a deduction later.
Each John Lewis purchase order names a destination branch or depot by code. Supply Lens maps every active Partnership location to the correct routing in your warehouse system, so the order lands against the right destination in your ERP without manual intervention.
John Lewis send sales and inventory reports back over the same connection. Supply Lens lands them in your ERP against the right products and branches, so you can see what sold and what remains on shelf without anyone rekeying a spreadsheet or waiting for a monthly statement.
Supply Lens handles the full John Lewis document set inbound and outbound, so documents are produced and transmitted automatically, without manual rekeying.
Supply Lens holds John Lewis's rules and the connection itself so you don't have to. Your team provides credentials, product mappings and the agreed cost list. Everything else lives in the Supply Lens layer.
Your John Lewis supplier code, GLN and trading partner profile registered with John Lewis's gateway. Supply Lens manages the connection identifiers and certificates, so there is no setup needed your side.
John Lewis EANs and product references mapped to your item codes. Pack-size variants, promotional lines and multi-pack SKUs are handled automatically once their cross-reference is established.
Each John Lewis branch and depot code mapped to your correct warehouse, customer account or entity in your ERP, so orders route cleanly on receipt and reports land against the right location.
Your agreed John Lewis cost list registered for invoice validation. Tolerance rules applied per supplier agreement, so price discrepancies surface your side first.
Supply Lens handles the scenarios that typically cause invoice rejections, deductions or document mismatches in the John Lewis flow.
The format never reaches your system. Supply Lens turns John Lewis's purchase order into a clean payload your ERP already understands and renders every outbound document in the structure John Lewis requires on the way back out. Your team works in their normal interface, the format conversion happens in the Supply Lens layer.
Invoice values are validated against the originating purchase order and your agreed John Lewis cost list before submission. Discrepancies are flagged before the invoice is sent, giving your team a chance to correct or query rather than receive a John Lewis deduction weeks later.
Both reports are landed in your ERP against the products and branches they refer to, not left as a file to open. Sell-through and on-shelf position sit next to your own stock and order data, so replenishment decisions are made on what actually sold rather than on what was last ordered.
Unrecognised EANs go to an exception queue immediately. The order is held, your team is notified with the full John Lewis context, the mapping is added and the order is re-triggered. No silent drop, no late invoice, no missed delivery window.
John Lewis onboarding involves their supplier team, the connection setup and your internal product and pricing data. Supply Lens manages the configuration, the gateway and the format conversion. You provide the inputs.
John Lewis supplier code, GLNs, ERP credentials and cost list received
EAN cross-reference, depot routing and pricing configuration completed in staging
Test purchase order processed, reports ingested and invoice generated, validated against John Lewis's specification
Production enabled, first live John Lewis purchase order processed end-to-end
Supply Lens routes John Lewis purchase orders directly into Unleashed, Enterpryze or other connected ERPs with the right item codes, document series and depot routing.
Most suppliers are live within five days. No long contracts, nothing to set up on your side. We handle the John Lewis-specific configuration, you confirm the mappings.