Retailer EDI requirements
Sainsbury's EDI requirements
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.
- Supplier relationship and access record: establish the approved company, supplier account, category and any authorized representative. Record which staff maintain the relationship and who can retrieve current technical and operational documents.
- Current Supplier Handbook and assigned technical packet: obtain the relevant version and identify its scope before mapping. Confirm order, shipment, invoice and adjustment requirements directly instead of relying on an old third-party message checklist.
- Item and receiving data: reconcile product identifiers, case packs, ordering units, depot or other destination references and delivery evidence. Ask whether every receiving location in scope follows the same workflow.
- Invoice and query evidence: establish the linkage between order, dispatch, receipt and billed amount. Capture the required references for a price or quantity dispute, and keep the commercial query separate from the transport status of the invoice file.
What the cited sources establish
- Sainsbury's current corporate contact page directs existing goods-for-resale Grocery and Fresh partners to Together With for day-to-day supplier activity. It separately routes prospective Sainsbury's and Argos suppliers through an introduction form; an introduction is not an active trading account.
- The official Together With landing page's indexed content identifies the Supplier Handbook, trading terms and Supplier Support app as resources. Direct retrieval required JavaScript during the November 9, 2026 review, and authenticated handbook contents were not accessed.
- The public registration guide distinguishes supplier and agent roles and asks suppliers for their company details and supplier code. Registration identity is useful for document access but is not itself an interchange identifier, a technical message version or proof of production acceptance.
- No current universal Sainsbury's transaction matrix was established from these sources. Confirm the actual UK account, category and receiving program rather than importing another retailer's syntax, acknowledgement times or ASN rules. This guide makes no SignalEDI certification claim.
Confirm in your current supplier packet
- Confirm whether the project is for Sainsbury's Grocery or Fresh, another merchandise program, or an Argos relationship. Shared corporate contact routes do not establish shared technical specifications or account approvals.
- Build an access and responsibility list using named roles rather than shared assumptions. A supplier administrator, third-party agent, warehouse operator and finance owner may need different information and authority.
- Obtain the current handbook and technical documents through the account's approved access route. Record inaccessible items as open questions, including message versions, transport, receipt semantics and the allowed method for corrections.
- Trace an actual in-scope destination and approved item through a safe order-to-invoice example. Verify units and references at every stage, then add a short delivery so the exception process is reviewed before live volume arrives.
- Agree what evidence closes an issue. A portal login, support case, transport acknowledgement, goods receipt and paid invoice are different events; the operational record should say which one is known and which remains unresolved.
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
- Sainsbury's official supplier contact routes (J Sainsbury plc)
Supports: Existing GFR Grocery/Fresh suppliers are directed to Together With; prospective supplier route is separate. Reviewed November 9, 2026.
- Together With supplier resources (Sainsbury's)
Supports: Official indexed landing content identifies Supplier Handbook, trading terms and Supplier Support. Direct rendering required JavaScript; authenticated contents not reviewed.
- Together With registration guide (Sainsbury's)
Supports: Publicly indexed official registration guidance distinguishes supplier/agent roles and supplier-code setup. No reliable internal revision date established; confirm current access instructions.