Supply Lens automates the Boots supplier document cycle. Purchase orders in, invoices out, all transmitted over the VAN that Boots uses and mapped to your ERP or IMS with the right depot codes, supplier IDs and Boots tolerance rules built in.
Boots's supplier integration is intentionally simple: orders in, invoices out, transmitted as Tradacoms over a Value Added Network. There is no separate acknowledgement message, no advance ship notice, no functional ACK. Where the complexity sits is in the supplier and location codes, the tolerance rules and the multiple business units fed from a single supply chain.
Boots receives EDI through a Value Added Network rather than a direct point-to-point AS2 link. Supply Lens connects to that VAN once, on your behalf, so you don't need a VAN account, a B2B gateway or your own AS2 certificates.
Boots uses Tradacoms, the legacy UK retail format still standard across most established UK retailers. Supply Lens generates and parses Tradacoms structures correctly so the format is invisible from your ERP's point of view, the order just arrives.
Boots stores, Boots Opticians, boots.com fulfilment and Boots Pharmaceuticals supply chain all draw from the same supplier setup but with different routing and document expectations. Supply Lens carries the right configuration per order so each business unit lands clean.
Boots identifies products by GS1 EAN and a Boots internal article number. Supply Lens maintains a cross-reference table mapping both to your own item codes, so the PO lands correctly in your ERP regardless of which identifier Boots sends.
Boots applies strict invoice matching on price and quantity. Supply Lens validates the invoice against the originating PO and your agreed cost list before transmission, flagging any discrepancy for review rather than sending it and risking a deduction later.
Boots fulfils through its central Nottingham campus and a network of regional DCs serving stores and online. The correct destination is set by location code on the PO. Supply Lens maps every active Boots location to the right routing in your warehouse system.
Boots's EDI flow is intentionally minimal: a purchase order in, an invoice out, both transmitted over the VAN that Boots uses. Supply Lens handles the format, the routing and the validation so neither side ends up rekeying anything.
Supply Lens holds Boots's rules and the VAN connection so you don't have to. Your team provides credentials, product mappings and confirms which Boots business units you supply. Everything else lives in the Supply Lens layer.
Your Boots supplier code, GLN and trading partner profile registered with the VAN that Boots uses. Configured as the inbound and outbound channel without any setup on your side.
Boots EANs and internal article numbers mapped to your item codes. Pack-size variants, promotional lines and multi-pack SKUs handled cleanly without manual maintenance.
Each Boots DC and business unit code mapped to your correct warehouse, customer account or entity. Boots stores, Opticians and online fulfilment kept distinct in your ERP.
Your agreed Boots cost list registered for invoice validation. Tolerance rules applied per supplier agreement, so price discrepancies surface your side first.
Boots's flow is short but unforgiving. Supply Lens handles the scenarios that typically cause invoice rejections, deductions or document mismatches.
Format never reaches your system. Supply Lens parses Boots's Tradacoms ORDHDR into a clean order payload your ERP already understands and renders your outbound invoice as INVFIL 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 PO and your agreed Boots cost list before submission. Discrepancies are flagged before the INVFIL is sent, giving your team a chance to correct or query rather than receive a Boots deduction weeks later.
Each Boots business unit (stores, Opticians, boots.com fulfilment, pharmaceuticals supply chain) is configured as a distinct routing path in Supply Lens. POs land against the right customer record in your ERP automatically, with the right pricing and the right document series applied.
Unrecognised EANs go to an exception queue immediately. The PO is held, your team is notified with the full Boots context, the mapping is added and the order is re-triggered. No silent drop, no late invoice, no missed delivery window.
Boots EDI onboarding involves their supplier team, the VAN registration and your internal product and pricing data. Supply Lens manages the configuration, the VAN trading partner setup and the format conversion. You provide the inputs.
Boots supplier code, GLNs, business unit list, ERP credentials and cost list received
EAN cross-reference, location routing and business-unit configuration completed in staging
Test ORDHDR processed, INVFIL generated and validated against Boots's Tradacoms specification
Production enabled, first live Boots PO processed end-to-end through the VAN
Supply Lens routes Boots POs directly into Unleashed, Enterpryze or other connected ERPs with the right item codes, document series and business-unit routing for each.
Most suppliers are live within five days. No long contracts, no VAN account on your side. We handle the Boots-specific setup, you confirm the mappings.