What is EDI and why do Canadian retailers require it?

EDI, Electronic Data Interchange, is the machine-to-machine exchange of business documents between trading partners in a structured format. Above a certain volume, large Canadian retailers like Loblaws, Sobeys, Metro, Walmart Canada, and Costco make it mandatory: purchase orders, ship notices, and invoices flow directly between ERPs with no rekeying.

Which X12 documents do I need to support?

The baseline set across the major Canadian retailers is: 850 (purchase order, inbound), 855 (PO acknowledgement, outbound), 856 (advance ship notice with SSCC, outbound), 810 (invoice, outbound), 820 (payment remittance, inbound), and 997 (functional acknowledgement, both directions). Costco adds the 832 (Item Master catalogue).

How much does it cost to connect Odoo to a retailer?

The one-time implementation cost to connect a new retailer to Odoo is typically $5,000 to $15,000 per retailer, at a $175/hr rate, including mapping, testing, and retailer certification. The translator subscription is on top of that, $300 to $1,500 per retailer per month.

Can direct AS2 eliminate the translator subscription?

Yes, partly. Walmart Canada and Home Depot Canada both support a direct AS2 connection with no VAN, which removes the per-retailer subscription fee. In exchange, you take on certificate management and uptime. The estimator zeroes the recurring line when you pick direct AS2, which mostly pays off above roughly 10,000 documents per month.

How long does EDI setup take?

A first connection typically takes 6 to 10 weeks: translator onboarding and Odoo bridge configuration, document mapping, retailer certification, then a parallel-run period. Subsequent retailers using the same translator are faster, typically 3 to 5 weeks each, because the Odoo side is already wired.

Free tool · Updated June 20, 2026

Are you ready for EDI with Canadian retailers?

Pick Loblaws, Sobeys, Metro, Walmart Canada, Costco, and the rest, and get the required X12 documents, a readiness checklist, the one-time cost to connect Odoo, and the monthly translator subscription. Built by Octura's senior Odoo architects. No email required.

Nine major Canadian retailersLoblaws, Sobeys, Metro, Walmart Canada, Costco, and the rest, each with its own X12 requirements.
A per-retailer readiness checklistThe union of required X12 documents, plus SSCC labelling and the 832 catalogue when they apply.
One-time cost and subscription, split apartThe one-time Odoo wiring and the monthly translator subscription on two separate lines.

Book a Scoping Call See retailer requirements

Retailers to connect Select every Canadian retailer you need to supply

Monthly document volume Total EDI messages per month across all retailers

Current system Odoo already live shortens the ERP-side wiring

EDI translator The middleware that handles X12 parsing and transport

Catalogue interchange (832) Required by Costco, and some assortment-heavy retailers

SSCC / GS1-128 labelling Pallet labels printed from Odoo, driven by the 856

One-Time Low$9,400Clean mapping, first-pass certification

Most Likely One-Time Cost$11,700Implementation, mapping, testing, certification

One-Time High$15,200Per-retailer quirks, certification re-runs

Retailers connected1

Required X12 documents6

Translator subscription (per month)$300 to $1,500

Setup timeline6 to 10 weeks

Required X12 Documents

850Purchase OrderInbound
855PO AcknowledgementOutbound
856Advance Ship Notice (with SSCC)Outbound
810InvoiceOutbound
820Payment RemittanceInbound
997Functional AcknowledgementBoth

Readiness Checklist

Odoo is live and serves as the system of record
Choose an EDI translator: SPS Commerce, TrueCommerce, or OpenText
Configure SSCC / GS1-128 printing in Odoo, driven by the 856
832 catalogue interchange not required for this selection
Map the inbound 850 to an Odoo sales order, with 855 and 810 outbound
No strict-timing retailers in this selection

Indicative USD range at a $175/hr rate. Per-retailer implementation typically lands between $5,000 and $15,000, and the translator subscription between $300 and $1,500 per retailer per month. For an exact figure, request a scoping call.

Book an EDI Scoping Call →

How This Estimator Works

Selling into a large Canadian retailer above a certain volume makes EDI mandatory. This estimator starts from your retailer list and derives the real work: it takes the union of the X12 documents each one requires, sizes the Odoo connection build, adds SSCC labelling and the 832 catalogue export when they apply, and charges a separate line for the monthly translator subscription.

The first retailer carries the bulk of the effort, the Odoo-side wiring. Each additional retailer costs far less because the ERP is already connected to the translator. The one-time cost tracks the source EDI article: roughly $5,000 to $15,000 per retailer, at a $175/hr rate. The single-retailer floor is $5,000.

Every per-retailer requirement comes from our guide, Odoo EDI Integration for Canadian B2B.

What Each Retailer Requires

The big Canadian retailers almost all run ANSI X12, most often the 5010 release, with a small set of mandatory documents: 850, 855, 856 with SSCC, 810, 820, and 997. The differences are in the specific segments, the timing windows, and the labelling rules.

Loblaws. X12 5010, full document suite, GS1 SSCC labels on all DC shipments.
Sobeys. X12 4010 common, some divisions on 5010. ANSI 856 with item-level detail required.
Metro. X12 4010/5010 mix. Strict on ANSI 856 timing, 2 hours before delivery minimum.
Walmart Canada. X12 5010, the most demanding guide. Direct AS2 supported. ASN compliance penalties for variance.
Costco Canada. X12 5010, custom subset. Item Master catalogue interchange (832) plus the standard documents, strict timing windows.
Canadian Tire. X12 5010, GS1-128 labelling, direct EDI gateway above a SKU threshold.
Couche-Tard. X12 5010 across the convenience banner, direct-distribution model to stores.
Home Depot Canada. X12 5010, DOTCOM portal for forecasting, direct AS2 supported. Strict on 856 timing and SSCC labels.

The X12 Document Flow in Odoo

A typical EDI cycle chains inbound and outbound messages. The inbound 850 (purchase order) from the retailer becomes an Odoo sales order. The outbound 855 acknowledges it. At shipment, the outbound 856 (advance ship notice) carries the pallet hierarchy, SSCC numbers, and lot/serial detail. The outbound 810 (invoice) is generated on shipment confirmation. The inbound 820 settles invoices, and the 997 acknowledges every message in both directions.

GS1-128 and SSCC labels print from Odoo's report engine at pack time, fed by the same data as the outbound 856. Costco adds the 832 (Item Master catalogue). A missing 997 is the canary for a transport failure: Odoo should alert if a sent document has not received its 997 within the retailer's window.

Choosing an EDI Translator

Odoo does not parse X12 natively. Every working Odoo + EDI deployment leans on an external translator that handles parsing, mapping, and AS2/VAN transport, then bridges to Odoo as JSON via the REST API or an SFTP file drop. The big three in Canada are SPS Commerce, TrueCommerce, and OpenText. Smaller specialists like 1 EDI Source and EDI2XML serve the mid-market and regional chains.

The translator subscription runs $300 to $1,500 per retailer per month depending on volume. Walmart Canada and Home Depot Canada both support a direct AS2 connection with no VAN: the saving can be significant at scale, but you take on certificate management and uptime. The estimator zeroes the subscription line when you pick direct AS2.

What This Estimator Does Not Cover

The estimator is built for Canadian retailers on ANSI X12. It does not cover EDIFACT, the international syntax dominant in Europe and Asia, nor US retailers and their own implementation guides. If you export to European subsidiaries (for example Metro AG's German operation), you will need separate EDIFACT support, which is out of scope here.

It also does not deep-model the underlying Odoo implementation build, nor data migration from another ERP. Treat the mid figure as a planning number, not a quote.

Next Steps After Your Estimate

The next step is a 30-minute scoping call. Octura has wired Odoo to Loblaws, Sobeys, Walmart Canada, Costco Canada, and Home Depot Canada for B2B suppliers across Canada. As an official Odoo partner in Canada, we review your retailer list, your ERP state, and the right translator, then send a fixed-price quote.

Book an EDI Scoping Call →

Backed by real migrations

Numbers like yours, validated on real migrations

Three engagements where the projection turned into operational reality on Odoo. Read the full case studies on the migration service page.

ManufacturingV12 → V17
Industrial Manufacturer, Texas
12custom modules ported, zero data lost
DistributionV14 → V18
Wholesale Distributor, Quebec
30%faster page loads after the upgrade
Professional ServicesCE → Enterprise
Consulting Firm, Brussels
0hproduction downtime during cutover

Frequently Asked Questions

01What is EDI and why do Canadian retailers require it?
EDI, Electronic Data Interchange, is the machine-to-machine exchange of business documents between trading partners in a structured format. Above a certain volume, large Canadian retailers like Loblaws, Sobeys, Metro, Walmart Canada, and Costco make it mandatory: purchase orders, ship notices, and invoices flow directly between ERPs with no rekeying.
02Which X12 documents do I need to support?
The baseline set across the major Canadian retailers is: 850 (purchase order, inbound), 855 (PO acknowledgement, outbound), 856 (advance ship notice with SSCC, outbound), 810 (invoice, outbound), 820 (payment remittance, inbound), and 997 (functional acknowledgement, both directions). Costco adds the 832 (Item Master catalogue).
03How much does it cost to connect Odoo to a retailer?
The one-time implementation cost to connect a new retailer to Odoo is typically $5,000 to $15,000 per retailer, at a $175/hr rate, including mapping, testing, and retailer certification. The translator subscription is on top of that, $300 to $1,500 per retailer per month.
04Why do I need an EDI translator with Odoo?
Odoo does not parse X12 natively. An external translator like SPS Commerce, TrueCommerce, or OpenText handles parsing, mapping, and AS2/VAN transport, then bridges to Odoo as JSON via the REST API or an SFTP file drop. Building X12 parsing in-house is 3 to 6 months of engineering for a result that is not differentiated.
05Can direct AS2 eliminate the translator subscription?
Yes, partly. Walmart Canada and Home Depot Canada both support a direct AS2 connection with no VAN, which removes the per-retailer subscription fee. In exchange, you take on certificate management and uptime. The estimator zeroes the recurring line when you pick direct AS2, which mostly pays off above roughly 10,000 documents per month.
06How long does EDI setup take?
A first connection typically takes 6 to 10 weeks: translator onboarding and Odoo bridge configuration, document mapping, retailer certification, then a parallel-run period. Subsequent retailers using the same translator are faster, typically 3 to 5 weeks each, because the Odoo side is already wired.
07Does this estimator cover EDIFACT and US retailers?
No. It is built for Canadian retailers on ANSI X12. It does not cover EDIFACT, the international syntax used in Europe and Asia, nor US retailers and their own implementation guides. For exports to European subsidiaries, separate EDIFACT support is required, which is out of scope here.