Canadian Tire buys centrally for a dealer network of independently operated stores, and its EDI program reflects that structure everywhere: orders explode to individual stores, assortments vary by location, and sell-through data flows back keyed to Canadian Tire's own product numbers. The good news for US suppliers expanding north — it's X12, following familiar conventions, with item data synchronized through GS1 Canada. A Canadian Tire build runs 2–3 days, sequenced like this.
Scope the agreement before the maps
Two scoping questions save rework later. First, banners: Mark's and SportChek belong to Canadian Tire Corporation, but trading programs are scoped per banner agreement, so confirm exactly which banners your setup covers. Second, identifiers: documents carry CTC product numbers alongside GTINs, which means your GS1 Canada synchronization and your internal item data both feed the same cross-reference. Get the agreement scope and the identifier plan settled, then build.
Build the three tables the program runs on
The item table maps CTC product numbers and GTINs to your SKUs — and because the dealer network's assortments vary by store, expect the ordered-item mix to differ across locations rather than assuming one national assortment. The location table covers stores and DCs. The reference table is the subtle one: vendor and agreement numbers arrive in REF segments on the 850 and must round-trip onto every downstream document, so configure the maps to inherit them structurally instead of trusting each document build to remember.
Handle the SDQ explosion
Store-distribution orders pack quantities for many individual Canadian Tire stores into SDQ segments on single lines. Your ERP — NetSuite, Dynamics 365 Business Central, or another of the 30+ supported systems — must unpack them into store-level allocations before anything is picked. Test this with a genuinely wide order during setup; an SDQ that fans out across the dealer network is a different beast from a three-store sample.
Make the ASN mirror the pallets
Canadian Tire receiving expects the 856 to describe freight as physically built: pallet → carton hierarchy, SSCC-18 labels on every shipping unit matching the MAN serials in the document, and the ASN posted before freight reaches the distribution centre. The reliable construction is the one that works everywhere scan-based receiving exists — a single pack-out record feeding labels and ASN, generation triggered by ship-confirm — but the pallet-level completeness deserves explicit testing here, since every shipping unit needs its serial.
Put the 852 to work
Canadian Tire sends store-level sell-through keyed by CTC product number in the 852. Two setup notes: the activity data reflects the corporate banner you trade under (confirm scope in your agreement), and the feed is only valuable if it lands somewhere — wire it into replenishment forecasting rather than an unread folder. Suppliers who plan from store-level POS data spot regional demand shifts across the dealer network cycles earlier than those waiting on POs alone.
Go live and watch the round trips
At switch-on, monitor 997 acknowledgments, ASN timing against DC arrival, and — specific to this partner — a periodic audit that vendor and agreement numbers are still echoing on every outbound document. Reference round-tripping fails silently after map changes, and silent failures surface as matching problems weeks later.
One planning note for US suppliers
If this is your first Canadian trading partner, sequence the GS1 Canada work ahead of everything else — identifier synchronization has external dependencies your project plan doesn't control, while the mapping and testing are fully in your hands. Everything else about the build will feel familiar to a team that has stood up US big-box retailers.
The cost side
Canadian Tire documents ride the standard EDISQ meter: first 25 per month free, then from $0.50 per document declining to $0.10 at the deepest volume tier, billed marginally. Cross-border trading adds no premium — connectivity, certified maps, and the sandbox are in the rate, there are no mapping or setup fees, and the Production plan's $100/month minimum applies in full to usage. Full tiers at pricing.
FAQ
Does Canadian Tire trade X12 or EDIFACT?
X12 — Canadian retail largely follows US X12 conventions, with item data synchronized through GS1 Canada.
What must round-trip on Canadian Tire documents?
Vendor and agreement numbers from the REF segments of the 850 must appear on every downstream document. Configure maps to inherit them automatically.
Do Mark's and SportChek ride the same setup?
They are Canadian Tire Corporation banners, but trading programs are scoped per banner agreement — confirm which banners your setup covers before testing.
How long does Canadian Tire EDI setup take?
About 2–3 days of technical work: cross-references, SDQ handling, ASN hierarchy, and the 852 feed into replenishment.