Retailer EDI requirements
Sobeys EDI requirements
Scope Sobeys integration around the local or broader supply agreement, banner, region and delivery model before turning a Canadian product listing into an automated order-to-invoice process.
Source-qualified document scope
Public sources reviewed 2026-11-09. These notes preserve the scope and access limits of the cited material; your current assigned packet controls implementation.
- Commercial and item setup: collect the approved banner, geographic scope, supplier account, products, case configurations and launch locations. Keep proposed listings separate from approved items so a draft product cannot accidentally become orderable.
- Orders and changes: request the current message guide and a representative sample for your own lane. Ask how store and DC destinations are identified, how changes supersede an order, and whether the supplier must acknowledge commercial acceptance.
- Delivery and receiving evidence: establish whether the assigned flow uses an electronic shipment notice, a store delivery record, a signed receipt or another mechanism. Confirm how shortages, substitutions and rejected goods are documented.
- Invoices and credits: obtain the relevant Canadian billing instructions, tax treatment and reference rules. Ask which delivery evidence supports payment queries and how a credit is linked to the original invoice without creating duplicate billing.
What the cited sources establish
- Sobeys' public Local Supplier Engagement page describes a Local Program that can begin in fewer than five stores and grow with its team. It identifies Canadian-made, regionally relevant, packaged products ready for sale as program criteria. That is a commercial listing path, not an EDI accreditation statement.
- The official supplier-partnership material describes supplier relationships and sourcing expectations, but the public material reviewed does not establish a current universal EDI message matrix for every Sobeys banner, region and delivery model. No authenticated supplier packet was accessed for this review.
- The practical distinction is scope: acceptance of a local product does not tell an implementation team whether replenishment, store delivery, invoicing and credits use the same process as a national distribution-centre agreement. Those questions belong in the assigned onboarding packet.
- Use this page to prepare precise questions and safe examples. It does not claim that SignalEDI has been approved by Sobeys, that every supplier uses one protocol, or that a US retail transaction list can be adopted unchanged in Canada.
Confirm in your current supplier packet
- Write a one-page supply-scope record covering banner, province, supplier legal entity, delivery model and billing account. For a local pilot, list the actual authorized stores instead of describing the account as nationally enabled.
- Build an item cross-reference from approved product data. Include consumer identifier, case identifier where applicable, pack size, ordering unit and billing unit. Assign an owner for packaging changes before testing automated quantity conversions.
- Compare a local delivery example with the intended expansion scenario. Identify which additional stores, depots, purchase-order formats or tax jurisdictions would trigger a fresh review rather than automatically inheriting the pilot configuration.
- Agree how operational exceptions reach finance: a short delivery, damaged item or disputed price should carry a traceable reference and evidence. Avoid correcting the invoice by changing the historical order or erasing the original receipt.
- Use the current partner materials supplied to your account to resolve message versions, connectivity, testing and approval. Track each unanswered question with an owner and source date; public listing guidance cannot fill a missing technical requirement.
This is a preparation checklist, not an additional mandate, certified mapping or production approval. Confirm transport, document versions, deductions and timing for your program.
Sources and their limits
- Sobeys Local Supplier Engagement (Sobeys)
Supports: Public page reviewed November 9, 2026; Local Program entry and growth model, Canadian-made and regional product criteria. Not an EDI specification.
- Sobeys supplier partnerships (Sobeys)
Supports: Official supplier relationship and sourcing context; reviewed November 9, 2026. Does not establish message codes or account-specific implementation requirements.