Supply Lens automates the complete Waitrose EDI document cycle for John Lewis Partnership suppliers — purchase orders received via Opentext VAN, EDIFACT DESADV ASNs transmitted on dispatch, invoices formatted to JLP's compliance requirements.
Waitrose EDI runs through the John Lewis Partnership's central trading infrastructure. EDI messages are exchanged via the Opentext VAN — the same network used by JLP's wider supplier base. Supply Lens is connected to the Opentext VAN and handles all Waitrose-specific document requirements, supplier codes, and location GLN mapping.
Waitrose EDI is transmitted via the John Lewis Partnership's Opentext VAN. Supply Lens is already connected to the Opentext network, so you do not need to set up a separate VAN account. Messages route through the JLP EDI infrastructure from day one.
All JLP distribution centre codes and GLNs are pre-loaded in Supply Lens. Location cross-referencing is triggered automatically during the order workflow with no depot routing setup required from you.
Waitrose assigns each supplier a JLP-specific vendor code used to identify your business across all Tradacoms messages. Supply Lens configures your JLP vendor code at the integration level so it is always applied accurately.
Your products are imported into Supply Lens once. The workflow then resolves Waitrose EANs and article numbers to your internal item codes on every order. Core range, seasonal lines, and exclusive products are all handled automatically.
Waitrose invoice matching is based on agreed cost prices and confirmed quantities. Discrepancies between the INVOIC and the originating ORDHDR are flagged before submission. Supply Lens validates price and quantity against the PO before every INVOIC is transmitted via the Opentext VAN.
Supply Lens handles the full Waitrose EDI message set via the Opentext VAN — inbound and outbound — so no document is ever manually produced, re-keyed, or sent late.
Waitrose holds its suppliers to the same quality standards it applies to its products. EDI compliance is taken seriously — routing errors, late ASNs, and invoice discrepancies are followed up promptly.
Supply Lens is already connected to the Opentext VAN used by the John Lewis Partnership. New suppliers do not need to establish a separate VAN account. Your Waitrose EDI is live through the Supply Lens connection from day one of onboarding.
JLP depot GLNs are held in Supply Lens and resolved automatically from the PO delivery location. Once the depot-to-GLN mapping is configured, the wrong GLN appearing in a DESADV is not possible — the mapping is applied at the integration layer, not by your team manually.
Waitrose and John Lewis trade under the same JLP EDI infrastructure via the same Opentext VAN. Supply Lens handles both as a single VAN relationship, with separate supplier codes and routing rules for each trading name. One connection, correctly separated at the document level.
Waitrose article number and EAN mismatches are resolved through the Supply Lens cross-reference table — which maps the Waitrose product reference to your internal item code. When Waitrose updates their product file, the mapping is updated in Supply Lens without touching your ERP.
Waitrose onboarding involves their JLP supplier trading team, your VAN routing details, and your product and depot data. Supply Lens manages the Opentext VAN connection and configuration — you provide the inputs.
EDI onboarding includes additional steps for VAN routing confirmation and live network testing before go-live.
Supply Lens routes Waitrose POs directly into Unleashed, Enterpryze, or other connected ERPs — with the correct item codes, document series, and JLP depot mapping for each.
Opentext VAN connection already in place. We handle the Waitrose-specific setup — JLP supplier codes, DC GLN routing, SSCC configuration, and invoice validation — from day one.