EDI requirements for Canadian Tire suppliers running Odoo

What Canadian Tire publishes, and where the EDI detail lives

Canadian Tire's supplier pages lay out a four-step path to becoming a product supplier: register in the Canadian Tire Vendor Gateway, participate in a sourcing review, negotiate the contract, and onboard. The Vendor Gateway handles sourcing activity such as requests for quote and contractual information, and new vendors also receive access to the Data Vault. Every supplier and their subcontractors are held to the Supplier Code of Business Conduct, which carries audit-backed standards and named zero-tolerance categories.

The public pages carry no EDI specification and no transaction-set list. Integration specifics arrive during onboarding, scoped to your category and banner, so the useful questions go to your sourcing contact once step one is done: which documents your listing trades, and where the integration guideline lives. The free Requirement Check reads whatever onboarding hands you and turns it into an Odoo-side scope.

The documents behind a general-merchandise mandate

A Canadian general-merchandise programme generally runs the standard loop. The order arrives as an 850 purchase order, an 855 acknowledgment answers it, the 856 advance ship notice precedes the truck, and the 810 invoice has to match the order. The 997 functional acknowledgment confirms each envelope landed. Programmes add change orders, inventory feeds and sales reporting where a category trades them; the X12 catalog covers every number in plain language.

Which sets your listing actually mandates is an onboarding fact. Collect it in writing, with the guideline, before anybody scopes a build against it.

Which route your files travel

Canadian suppliers reach their retailers over the same three broad routes as everywhere else: a platform that translates and bills per document, a direct connection where the programme allows one, or keying at low volume. If your onboarding names a platform such as TrueCommerce, the Odoo side of a TrueCommerce connection is covered separately. The route decision usually arrives with your onboarding material, so treat the line in your own paperwork as the answer, and remember the route only moves files. The mapping into your Odoo is the same work on every route.

What changes inside your Odoo

There is no X12 in Odoo, so a Canadian Tire programme is a connector sitting on top of it. The four Odoo-side mechanisms are the constant across this page family. Packagings carry the casepack, configured per product with a Unit Name, Quantity and Reference Unit. The GS1 nomenclature maps the GTIN to the product Barcode field and the SSCC to the Package name, the two fields your 856 and carton labels are built from. The retailer's PO number belongs in Customer Reference, the field Odoo exposes as client_order_ref. And the Delivery Date against Expected date decides what your warehouse promises into a delivery window.

Hardlines and seasonal assortments put the pressure on the item master: item numbers, identifiers and casepacks changing by programme year, all of which must agree across your Odoo, their item file and your labels before the first order flows.

Testing and enforcement, in general form

Programmes generally test in stages: connectivity, then each document validated against the guideline, then a watched production window. Enforcement runs on compliance scorecards and deductions, and a deduction reaches you as a coded line on the remittance advice. How chargebacks land in Odoo covers the counting and the reconciliation. The windows and rates that apply to you are guideline facts; get them in writing before agreeing a go-live date.

The wider Canadian picture is on EDI in Canada. The grocery side of a Canadian book runs through Loblaw EDI requirements, and the cross-border mass-merchant mirror is Walmart EDI requirements.