EDI requirements for Loblaw suppliers running Odoo

What Loblaw publishes about supplier EDI

Loblaw's public supplier information is spread across its main supplier page, the small supplier page and the portal support page. None of them mentions EDI, X12, transaction sets or GS1. They describe the Loblaw Supplier Portal and the roles around it.

Access sits with a role Loblaw names the Portal Administrator, the person at your company who acts as primary contact for the portal and who "is able to manage access for users in their organization to specific applications required through the Loblaw Supplier Portal". An organization can hold up to three. The same page carries separate control-brand NDAs for LCL, SDM, Joe Fresh and T&T, so confirm which banner your listing sits under.

Start with two messages. Find who holds Portal Administrator at your company, then write to vendorcomm@loblaw.ca with supplier questions or vendorportaladmin@loblaw.ca for portal access. Ask for two named things: the Supplier onboarding checklist, and the document set your category is being onboarded to. Get the guideline in writing before anybody scopes a build against it, and the free Requirement Check will read it with you.

The documents behind a grocery mandate

A large Canadian grocery programme runs four documents in a loop, and grocery adds a fifth. The retailer sends an 850 purchase order. You return an 855 acknowledgment inside their window. You send an 856 advance ship notice before the truck reaches the dock. You bill with an 810 invoice. Many grocery programmes use the 875 grocery purchase order, the same job written in the grocery subset of X12 and weighted toward cases, pallets and delivery windows. The 997 functional acknowledgment is required by some programmes and absent from others, so check yours.

You can read the Canadian versions today. GS1 Canada's Canadian EDI Guidelines file the guides by sector, and the one you want is Grocery. The index carries 850, 855, 856, 810, 820, 852 and 997 guides in version series from 4010 through 8010, and each opens with no login. Open the version your retailer runs; their guideline names it. Deductions arrive on the 820 remittance advice, and our X12 transaction codes in Odoo page lists the rest.

Which route your files travel

Your letter or your portal names the route, and the choice is usually made for you. A platform sits between you and the retailer, translates, and bills per document. If your letter names SPS Commerce, the Odoo side of an SPS Commerce connection is covered separately. A direct AS2 or SFTP link removes the middle and moves the mapping work to you. A web portal has you keying documents by hand, which works at low volume and stops working as you grow.

Platform vendors list large retailers in their public network directories. A listing means that platform can reach that retailer. It settles nothing about which route you have been told to use, so read the line in your own letter and treat that as the answer.

What changes inside your Odoo

There is no X12 in Odoo. Odoo 19.0 does carry a feature called EDI: the Purchase app exports a purchase order as a UBL XML file, and another Odoo database imports it as a sales order. The documentation describes that as an exchange "directly between their Odoo databases". Your Loblaw guideline will be X12, and X12 appears nowhere in the Odoo 19.0 documentation. So a retail programme is a connector sitting on top of Odoo, and four things on the Odoo side decide whether it holds.

Casepack. Odoo 19.0 calls this Packagings, enabled under Inventory, Configuration, Settings, Products, Units of Measure and Packagings. Packagings are configured on the individual product form, so every item you ship needs its own case and pallet definition, each carrying a Unit Name, a Quantity and a Reference Unit. All three are required. A casepack that disagrees with theirs produces a shortage on a load your warehouse picked correctly.

Identifiers. Odoo 19.0's GS1 barcode nomenclature maps the 14-digit GTIN, application identifier 01, to the Barcode field on the product form, and the 18-digit Serial Shipping Container Code, application identifier 00, to the Package name. Your 856 and your pallet labels are built out of those two fields.

Their order number. The retailer's PO belongs in Customer Reference on the sales order, the field Odoo exposes as client_order_ref. Everything they send back quotes that number, a deduction included.

The window. Odoo 19.0 puts a Delivery Date on the order with an Expected date beside it. Grocery delivers into a window, so settle which of those two your warehouse is promising against before the first live order lands.

The testing phase

Grocery programmes generally run testing in three stages. Connectivity comes first, proving your files reach them and theirs reach you. Each document is then validated against their guideline one at a time, in the order the business runs them. A production window follows, with live orders flowing while somebody watches every one.

The item master is what overruns. Every item needs its GTIN, its casepack, its price and their item number agreeing across your Odoo, their system and anything in between. A short, clean product master tests quickly. A long one with three spreadsheets behind it is where the weeks go, and that part you can fix before the letter arrives.

Where the deductions bite

A deduction is your customer paying you less than your invoice and telling you why in a code. It reaches you on the remittance advice, which is why one event carries two names in the same conversation: they call it a chargeback and your statement calls it a deduction. How chargebacks land in Odoo covers the reconciliation side.

Across grocery programmes generally, three mechanical causes account for the document-driven ones. A document arrives outside its window. A document disagrees with the documents around it, most often an 856 that fails to match the 850 or the trailer. A label carries the wrong identifier or sits in the wrong place on the carton.

The schedule that applies to you travels with your guideline and the amounts differ by programme, so ask for it in writing before you agree to a go-live date. Loblaw's small supplier page states payment terms of 7 days for suppliers in that programme, with smallsupplier@loblaw.ca as the contact on it. On terms that short, an invoice that fails validation is a visible hole in the week it was due.

EDI in Canada covers how Canadian and cross-border programmes differ, and suppliers holding the same letter from a US grocer want Kroger EDI requirements. For the general-merchandise side of a Canadian book, see Walmart EDI requirements.