Try it now Login

EDI Trading Partner

Connect to Ocado EDI Instantly

Join thousands of customers that connect to Ocado with XEDI.

No credit card needed ✦ Free EDI mailbox included

See how XEDI connects suppliers to Ocado

Ocado suppliers use EDI to support accurate retail ordering, fulfilment and invoicing. XEDI helps automate Ocado document exchange and connect it with internal systems for better visibility and fewer manual steps.

Overview

Getting started with Ocado EDI

Purchase orders Order acknowledgements and responses Invoices Credit notes or adjustments where required Product, catalogue or stock data where required

Documents you can exchange

Purchase orders
Order acknowledgements and responses
Invoices
Credit notes or adjustments where required
Product, catalogue or stock data where required

Who it's for

Built for Ocado suppliers

Whether you send a handful of orders a week or thousands a day, XEDI keeps your Ocado trading accurate and hands-off.

Online grocery suppliers
Food and beverage suppliers
Consumer goods suppliers
Warehouse teams
Finance teams

In practice

Ocado EDI overview

Ocado EDI is the structured exchange of commercial documents between Ocado and businesses working in online grocery fulfilment and delivery operations. The agreed document set starts with orders and invoices, with the operational emphasis on keeping order, fulfilment and finance data aligned.

A practical Ocado integration should connect the agreed document set with the systems that process it. XEDI maps the agreed EANCOM or EDIFACT messages into ERP, warehouse, accounting or API workflows, while validation and alerts help teams deal with exceptions before they affect delivery or payment.

Every document validated before it moves

XEDI checks each Ocado order, despatch advice and invoice against the required format, so errors are caught before they reach your systems.

Onboarding

Ocado supplier onboarding process

For Ocado, onboarding starts with confirming the supplier relationship, document scope and connection route. XEDI then maps, tests and monitors the agreed workflow so teams can move from first order to stable live trading with clear ownership of exceptions.

01
Confirm the Ocado supplier account, buyer contacts, delivery locations, identifiers and current document requirements.
02
Agree the Ocado order, response and invoice scope for the trading relationship.
03
Map Ocado message data to the supplier's ERP, warehouse, order-management and accounting systems.
04
Configure EANCOM or EDIFACT validation, connection routing, exception alerts and user responsibilities in XEDI.
05
Complete the agreed Ocado test transactions, checking mandatory references, product data, delivery details and invoice matching.
06
Monitor initial live transactions and resolve rejected, delayed or mismatched documents with the operational and finance teams.

Ready to connect Ocado?

Talk through documents, standards, testing and system integration with XEDI.

Connect to Ocado Book a Demo

Detail

Everything about Ocado EDI

Ocado EDI message types

Ocado message requirements depend on the supplier account and fulfilment route. These are the common EANCOM or EDIFACT equivalents used to plan the order-to-invoice workflow; the shipping message is included when the agreed route requires it.

Message	Purpose	Direction
ORDERS	Purchase order with item, quantity, price, delivery location and requested delivery details.	Ocado to supplier
ORDRSP	Order acknowledgement or response used to confirm, reject or amend order lines before fulfilment.	Supplier to Ocado
INVOIC	Invoice linked to the order, delivery and supplier references agreed with Ocado.	Supplier to Ocado
APERAK	Application or functional acknowledgement used to confirm receipt or identify processing errors where supported.	Either direction

Ocado EDI requirements

Ocado requirements should be confirmed against the current agreement and test instructions. Planning should also account for the transport and validation controls used for online grocery fulfilment and delivery operations.

EANCOM or EDIFACT

Map the agreed Ocado order, response and invoice messages in the EANCOM or EDIFACT format used by the trading setup.

AS2 or managed connectivity

Use AS2, SFTP, a VAN or the connection method agreed with Ocado, with secure routing and delivery-status monitoring.

Product and location references

Validate agreed product identifiers, pack data, ship-to or depot locations and supplier references before a document is sent.

Testing and go-live

Test the agreed Ocado message set, resolve validation feedback and retain evidence that the connection is ready for live trading.

Common requirements & compliance

Common requirements

Ocado supplier account, trading partner and buyer identifiers
Product identifiers, SKUs, GTINs, pack sizes and agreed item descriptions
Delivery, depot, warehouse or ship-to references
Invoice, tax, payment and remittance references
Agreed EANCOM or EDIFACT message set and connection method
Test evidence for the agreed order and invoice flows

Compliance notes

Ocado document requirements can vary by category, region, delivery route and fulfilment model.
Supplier, product, location and invoice references must match the trading agreement and test data.
Use pre-send validation and exception monitoring to reduce rejected Ocado orders and invoices.

Ocado ERP integration

Ocado EDI integration connects supplier document flows with the systems teams use to process orders, allocate stock, ship goods and create invoices. XEDI can map the agreed Ocado data into ERP, accounting, warehouse, ecommerce and API workflows.

SAP

Map Ocado orders, shipment data and invoices into SAP workflows.

Oracle

Connect Ocado EDI with Oracle Fusion order, fulfilment and finance processes.

Sage

Automate Ocado order and invoice handling for Sage users.

Microsoft Dynamics

Route Ocado EDI messages into Microsoft Dynamics sales, stock and finance workflows.

NetSuite

Connect Ocado EDI with NetSuite order management, fulfilment and invoicing.

QuickBooks

Support Ocado invoice and accounting workflows for QuickBooks users.

Why suppliers choose XEDI for Ocado

Businesses choose XEDI for Ocado EDI when they need a managed connection focused on keeping order, fulfilment and finance data aligned, with the agreed documents, validation rules, integrations and exceptions visible in one workflow.

Ocado-specific onboarding for identifiers, document scope, testing and go-live planning.
Validation for Ocado orders and invoices before documents are exchanged.
EANCOM or EDIFACT mapping with ERP, accounting, warehouse, API, AS2 and VAN connectivity options.
Exception alerts and monitoring for failed, delayed or rejected documents.
A managed workflow that reduces manual re-keying while keeping procurement, operations and finance teams informed.

Supplier FAQ

Ocado EDI FAQs

What is Ocado EDI?

Ocado EDI is the structured exchange of documents between Ocado and its suppliers. It supports agreed workflows for orders, order responses, delivery information, invoices and related acknowledgements.

Can XEDI connect suppliers to Ocado EDI?

Yes. XEDI can connect Ocado EDI flows with supplier systems and automate the agreed EANCOM or EDIFACT messages, subject to the account's document scope and testing process.

Which documents does Ocado EDI support?

Every enriched XEDI partner page covers purchase orders and invoices. The wider Ocado workflow can include order responses, credit notes, product information and acknowledgements where agreed.

Which EDI standard is used for Ocado?

This Ocado page is planned around EANCOM or EDIFACT. The exact version, subsets and message rules should be confirmed from the current trading agreement and test pack.

Can Ocado EDI use AS2?

XEDI can support AS2 where it is the agreed Ocado connection route, including certificates, encryption, signatures and delivery-status monitoring.

Can Ocado EDI integrate with my ERP or accounting system?

Yes. XEDI can map Ocado documents into supported ERP, accounting, warehouse, ecommerce and API workflows, including SAP, Oracle, Sage, Microsoft Dynamics, NetSuite and QuickBooks.

What should a Ocado supplier prepare before onboarding?

Prepare supplier and product identifiers, delivery locations, tax and invoice details, the agreed message list, connection details and any testing instructions supplied for the account.

How long does Ocado EDI onboarding take?

Timing depends on the supplier systems, agreed message set, data quality, testing scope and Ocado onboarding process. Confirming scope early helps prevent avoidable delays.

Can XEDI help reduce Ocado order and invoice errors?

Yes. XEDI can validate mandatory fields, map references consistently and surface exceptions before documents are exchanged, reducing avoidable corrections in Ocado order and invoice workflows.

Do Ocado supplier requirements vary?

They can vary by category, region, fulfilment model and delivery route. The current Ocado agreement and test instructions should always take priority over a general integration plan.

Related partners