O
Ocado Retail Tradacoms · EDIFACT DESADV · VAN
🇬🇧 UK

Ocado EDI,
done properly.

Supply Lens automates the complete Ocado EDI document cycle — purchase orders received, acknowledgements sent, despatch advice and invoices transmitted to spec. Standard Tradacoms via VAN, with Ocado's location GLN structure and fulfilment compliance requirements handled from day one.

5doc
Message types handled
VAN EDI
Standard Tradacoms via VAN
99.9%
Uptime SLA
Supply Lens — Ocado Live Flow Live
Ocado PO OC-2025-44821 received via VAN 48× 5060234811042 · 24× 5060234811059 · Hatfield CFC PO IN
EANs mapped · CFC GLN resolved Hatfield → GLN 5060100000021 · supplier OC-7731 matched PROCESSING
Sales order SO-13305 created ERP / IMS · 72 units · ref OC-2025-44821 CREATED
DESADV + INVOIC transmitted via VAN SSCC PAL-8812 generated · £1,188.00 · Ocado-compliant ASN + INV
Ocado-Specific Requirements

Ocado is a technology-led
retailer with standard EDI.

Despite Ocado's reputation as a technology business, its supplier EDI is standard Tradacoms via VAN — the same message types used by traditional grocery retailers. What makes Ocado distinct for suppliers is its Customer Fulfilment Centre model: all stock is received centrally, fulfilment timings are tightly managed, and compliance requirements around booking-in windows and delivery accuracy are enforced closely.

Standard Tradacoms via VAN

Ocado uses standard Tradacoms message types transmitted via a VAN. No proprietary API or additional technical layer is required. Supply Lens connects via the same VAN infrastructure used for other major UK grocery retailers. The integration pattern is well-established.

Location cross-reference

All Ocado CFC codes and GLNs are pre-loaded in Supply Lens. Location cross-referencing is triggered automatically during the order workflow. DESADV documents route to the correct Customer Fulfilment Centre without any setup from you.

Delivery slot compliance

Ocado manages inbound deliveries to its CFCs through a booking-in system. The DESADV must be transmitted before the delivery slot. Late ASNs cause goods-in delays and compliance flags. Supply Lens fires the DESADV on dispatch confirmation, within the required window.

Product cross-reference

Your products are imported into Supply Lens once. The workflow then resolves Ocado EANs to your internal item codes on every order. Multipacks, case/unit variants, and promotional configurations are all handled automatically.

Invoice accuracy requirements

Ocado validates invoices against cost prices and shipped quantities. Price and quantity discrepancies trigger a payment hold or deduction. Supply Lens validates invoice values against the originating PO before every INVOIC is transmitted, flagging issues before they reach Ocado's finance team.

Document Flow

Every document.
Every direction.
Automatically.

Supply Lens handles the full Ocado EDI message set via VAN — inbound and outbound — so no document is ever manually produced, re-keyed, or sent outside the compliance window.

  • ORDHDR — Ocado purchase orders received and validated (Tradacoms)
  • DESADV — ASN with SSCC pallet references transmitted on dispatch (EDIFACT)
  • INVOIC — Invoice submitted and validated against PO before transmission
  • No order response or control acknowledgement in this flow
  • All messages routed via VAN within Ocado's compliance windows
Ocado document cycle
Purchase Order ORDHDR
Ocado VAN
ASN / Despatch Advice DESADV
Ocado VAN
Invoice (pre-validated) INVOIC
Ocado VAN
Location & product cross-reference
Ocado reference Resolved automatically
CFC codes & GLNs
Pre-loaded · no setup needed
Product EANs
Resolved during order workflow
Multipack & case variants
Handled as separate line items
Standard EDI, not a custom API: Despite Ocado's technology profile, its supplier-facing EDI is standard Tradacoms via VAN — the same integration pattern used for traditional grocery retailers. No additional technical layers are required.
Configuration

Configured for
Ocado. Connected
to your system.

Supply Lens holds Ocado's CFC GLN structure and compliance rules so you don't have to. Your team provides credentials, product mappings, and confirms CFC routing — everything else is handled at the Supply Lens layer.

1

Ocado supplier onboarding

Your Ocado supplier number, GS1 GLN, and VAN credentials are captured and configured as the inbound/outbound channel.

2

Product import and cross-reference

Your products are imported into Supply Lens. The workflow handles Ocado EAN-to-item-code cross-referencing automatically — multipacks, promotional configurations, and case/unit variants included.

3

Location cross-reference

All Ocado CFC codes and GLNs are pre-loaded. The workflow resolves the correct fulfilment centre on every incoming order automatically — no CFC routing setup required from you.

4

ERP connection and go live

Your ERP or IMS is connected and invoice pre-validation enabled. Orders flow end-to-end — purchase order in, DESADV and INVOIC out — automatically and within Ocado's compliance windows.

EAN → item code cross-reference
Ocado EAN / GTIN Your item code
5060234811042 GRN-SMTH-250G
5060234811059 GRN-CRCH-250G
5060234811066 GRN-SMTH-500G
5060234811073 GRN-MP6-250G
ORDHDR ingest
Via VAN
ON
DESADV + SSCC
On dispatch
ON
INVOIC pre-check
Before transmission
ON
CFC routing
Per PO delivery loc.
CONFIG
Exception queue
Email + dashboard
CONFIG
Ocado Edge Cases

The situations that
catch suppliers out.

Ocado's CFC model means that inbound compliance — DESADV timing, SSCC accuracy, and delivery slot adherence — is tracked closely. Supply Lens handles the scenarios that typically generate compliance flags.

"We sent the DESADV after the delivery arrived at the Hatfield CFC — Ocado flagged it as a compliance failure."

Ocado's CFC goods-in process relies on the DESADV being received before the delivery. Supply Lens fires the DESADV as soon as dispatch is confirmed in your ERP — not when someone remembers to send it. The window is met automatically.

"The SSCC on our pallet label didn't match the DESADV — the CFC couldn't accept the delivery."

Ocado's automated goods-in systems match physical SSCC labels against the DESADV electronically. Supply Lens generates SSCC references as part of the DESADV and your label print run uses the same reference — they cannot diverge because they come from the same source.

"We assumed Ocado used a custom API because of how they talk about their technology platform."

Ocado's supplier-facing EDI is standard Tradacoms via VAN — the same integration pattern used for traditional grocery retailers. The technology Ocado is known for applies to its fulfilment operations, not its supplier trading documents. Supply Lens handles it as a standard EDI pairing.

"An Ocado PO came in with an EAN for a new seasonal product we hadn't mapped yet."

Unrecognised EANs go to an exception queue immediately — the PO is held, your team is notified with the full Tradacoms context, the mapping is added, and the order is re-triggered. No silent drop, The window is tracked from when the mapping is completed, not when the PO arrived.

Getting Set Up

What you need
to go live with Ocado.

Ocado onboarding involves their supplier trading team, VAN credentials, and your product and CFC routing data. Supply Lens manages the VAN connection and configuration — you provide the inputs.

  • Ocado supplier number and GS1 GLN
  • VAN credentials and trading partner identifiers
  • ERP or IMS credentials (Unleashed, CIN7, Enterpryze, or other)
  • Agreed cost price list for invoice validation
  • Sample Ocado POs (real examples where available)
Typical delivery timeline
1
Scope
Ocado supplier number, GLN, VAN credentials, and ERP credentials received.
2
Configure
Product import, EAN cross-reference, and location cross-reference verified in staging.
3
Test
Test PO processed via VAN — DESADV and INVOIC validated against Ocado spec and timing requirements.
Go live
Production VAN connection enabled — first live Ocado PO processed end-to-end.

EDI onboarding includes additional steps for VAN routing confirmation and live network testing before go-live.

ERP & IMS Connections

Connect Ocado to your back-office system.

Supply Lens routes Ocado POs directly into Unleashed, Enterpryze, or other connected ERPs — with the correct item codes, document series, and CFC GLN mapping for each.

Other retailers we support

View all 50+ retailers →

Ready to automate
your Ocado EDI?

VAN connection already in place. We handle the Ocado-specific setup — CFC GLN routing, SSCC configuration, DESADV timing compliance, and invoice pre-validation — from day one.