Setup guides · October 20, 2026

How to Set Up EDI with Loblaw (Step by Step)

Loblaw EDI setup for suppliers: ECCnet GTIN synchronization, banner-aware order handling, pallet-case ASN structure, testing, and go-live.

Two registrations stand between you and your first Loblaw purchase order, and only one of them is EDI. Canada's largest grocer synchronizes product data through GS1 Canada's ECCnet registry, and its EDI documents then reference those synchronized GTINs — so a Loblaw onboarding is really a data project and a connectivity project running in parallel. Handled that way, the EDI side takes 2–3 days. Here's the sequence.

Track one: synchronize the product data

Start ECCnet early because it gates everything. GTINs for your items get registered and synchronized through GS1 Canada before the first order can reference them cleanly; the EDI documents will lean on those identifiers from day one. This track runs on GS1 Canada's timelines, not yours — which is exactly why it starts first, while the technical build proceeds alongside it.

Track two: know your banners

Loblaw orders are cut per division and banner — Loblaws, No Frills, and Real Canadian Superstore share the network, with banner-level context carried on the documents. Your agreement defines which banners are in scope, and the setup should encode that: order intake aware of the division and banner each 850 belongs to, and cross-reference tables that resolve ship-tos across the regional DC structure. Confirm scope with your buyer before testing rather than discovering an unexpected banner in production.

Connect the ERP and load the tables

Attach your business system — NetSuite, Sage Intacct, or whichever of the 30+ supported platforms runs your operation — so orders arrive as ready-to-work sales orders. The item table keys on the ECCnet-synchronized GTINs; the location table carries the regional DCs; and both feed the outbound documents that close the loop, through to the 810 invoice reconciling against order and receipt.

Build the ASN the DC plans around

Loblaw's receiving standard is a pallet → case hierarchy into the regional DC, with the 856 landing before the delivery appointment. The construction rules are the dependable ones: capture the load as built — pallets and the cases on them — in one shipment record at ship-confirm, generate the ASN from that record, and let the confirm event trigger transmission so appointment timing is met structurally. Grocery freight adds a practical wrinkle worth testing: mixed pallets, where the hierarchy has to describe which cases sit on which pallet accurately.

Test both tracks together, then switch on

The sandbox pass that matters runs an ECCnet-registered item through the full cycle: order in, allocation, pallet-case ASN out, invoice matched. Add a scenario for an item whose GTIN is not yet synchronized — the correct behavior is a flagged exception, not a silently transmitted document that bounces on Loblaw's side. At go-live, monitor 997 acknowledgments and ASN-versus-appointment timing, and keep the item exception queue visible; in a registry-driven program, most order problems are really data-synchronization problems wearing an EDI costume.

Sequencing the two tracks

A workable calendar: kick off ECCnet registration in week zero; run the ERP connection, cross-references, and map configuration while the registry work proceeds; and schedule the joint sandbox pass for whenever the first items complete synchronization. The failure pattern to avoid is serializing — finishing the EDI build, then starting the data work, then discovering the combined test at the end. Registry-driven programs reward parallelism and punish queues, and the supplier who runs both tracks at once is trading weeks against days.

What the meter reads

Loblaw volume prices identically to every EDISQ partner: 25 documents each month free, then from $0.50 per document easing to $0.10 at the highest tier, marginal-tier billed. There is no surcharge for Canadian trading and no mapping or setup charges — connectivity and certified maps are part of the rate, with live trading on the Production plan's $100/month usage-credit minimum. The complete price list is at pricing, and adjacent Canadian expansion targets live in the partner directory.

FAQ

Do I need ECCnet before trading EDI with Loblaw?

Product data for Canadian grocery majors is synchronized through GS1 Canada's ECCnet registry, and the EDI documents reference those GTINs — so plan the data sync alongside the EDI build.

Which banners does a Loblaw EDI setup cover?

Loblaws, No Frills, and Real Canadian Superstore share the network, with orders cut per division and banner. Your agreement defines the exact scope.

What ASN structure does Loblaw expect?

Pallet-to-case hierarchy into the regional DC, with the ASN landing before the delivery appointment.

How many days is the Loblaw technical setup?

Around 2–3 days with certified maps, run in parallel with the ECCnet data synchronization.