Skip to main content

Tesco EDI: requirements and onboarding

Prepare Tesco UK trading by connecting approved product and case data to the assigned commercial account, while keeping product induction, compliance access and EDI production approval separate.

Quick answers

Can SignalEDI help me connect to Tesco?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your Tesco program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
What determines the Tesco onboarding timeline?
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
Which ERP systems can I use for Tesco?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Review integration scope

Plan the integration workflow

SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.

  1. 1. Your business system

    Identify the source records, system edition, data owner, and allowed access.

  2. 2. SignalEDI preparation

    Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.

  3. 3. Partner testing and approval

    Complete the partner-controlled tests and retain permission before enabling live exchange.

Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.

Build your onboarding checklist

Download the onboarding worksheet (text)

Public sources reviewed 2026-11-09

What the public record confirms

  • Tesco publishes product-data training for myProduct: Induct that distinguishes consumer product identifiers from outer-case identifiers, fixed and variable ordering, and country-specific product setup. The public guide includes multi-market examples and Central Europe support references; it is not a UK EDI implementation packet.
  • Tesco's publicly hosted UK and Republic of Ireland Inspectorio Compliance training describes Toolkit as an access point for direct supplier partners and separates supplier organizations from factory sites. Its historical rollout details are not used here as current access promises or mandatory onboarding timelines.
  • These primary materials establish useful distinctions between product data, supplier identity and compliance work. They do not establish the current UK order, ASN, invoice, acknowledgement or transport matrix. Obtain the current packet for your category and account before selecting syntax or message versions.
  • Sources were reviewed November 9, 2026. Publication and market scope matter: a public training example cannot establish current UK field requirements, and neither Toolkit access nor a completed product record proves SignalEDI certification or an approved production connection.

Document and workflow scope

Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.

  • Account and market scope: identify the actual Tesco buying entity, UK program, supplier account and approved destinations. Separate direct merchandise supply from a marketplace, indirect procurement or another country's arrangement before choosing technical materials.
  • Product and case master data: collect the approved item relationships, ordering units, pack quantity and cost basis. Ask which internal and external identifiers are authoritative for the account and how a case change becomes effective.
  • Orders, shipments and invoices: obtain current UK message guides and representative examples for the agreed delivery flow. Confirm how changes, partial fulfillment, quantity differences and credits are handled instead of copying a generic UK retail document list.
  • Compliance and operational records: identify any applicable site approval, product specification, artwork and receiving requirements separately from EDI testing. Retain the owner and status of each prerequisite so technical success does not conceal an unfinished product or supply-chain step.

Connectivity and testing requirements

Connectivity

Confirm whether the current Tesco program uses AS2, SFTP, VAN, or another named transport.

Onboarding window

Not verified on this page.

Certification focus

The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.

  • Tesco publishes product-data training for myProduct: Induct that distinguishes consumer product identifiers from outer-case identifiers, fixed and variable ordering, and country-specific product setup. The public guide includes multi-market examples and Central Europe support references; it is not a UK EDI implementation packet.
  • Tesco's publicly hosted UK and Republic of Ireland Inspectorio Compliance training describes Toolkit as an access point for direct supplier partners and separates supplier organizations from factory sites. Its historical rollout details are not used here as current access promises or mandatory onboarding timelines.
  • These primary materials establish useful distinctions between product data, supplier identity and compliance work. They do not establish the current UK order, ASN, invoice, acknowledgement or transport matrix. Obtain the current packet for your category and account before selecting syntax or message versions.
  • Sources were reviewed November 9, 2026. Publication and market scope matter: a public training example cannot establish current UK field requirements, and neither Toolkit access nor a completed product record proves SignalEDI certification or an approved production connection.

Questions to resolve from the current buyer packet

  • Create a UK-specific scope record and label every source by market, program and revision. Use the public training to formulate questions, then resolve actual field rules against materials assigned to your account.
  • Trace an approved consumer product through its case configuration and order unit. Verify that ERP, warehouse, artwork and finance records describe the same physical item rather than relying on a shared description or similar-looking barcode.
  • For weight-based products, distinguish planning estimates, actual measured quantities and the unit used for pricing. Ask which data is required at ordering, dispatch and billing, and where each value originates.
  • Treat an expansion into another market or a new case size as a controlled data change. Review external identifiers, descriptions, taxes and effective dates before reusing a UK mapping or sending new stock against old item data.
  • Retain separate readiness evidence for commercial listing, product information, physical delivery and electronic exchange. Confirm the account's actual approval process without promising a fixed date or treating a training screenshot as a completed test.

EDI requirements quick reference

Document codes and the planning checklist for this partner also live on the Tesco EDI requirements page. That page stays separate from this onboarding profile.

How SignalEDI handles it

  • Prepare a versioned mapping and testing checklist from the requirements you provide.
  • Validate synthetic or scrubbed samples before partner testing.
  • Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.

Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart

Pricing

SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Compare current plans

Practice the workflow before partner testing

These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.

Trace one product through two case configurations

Create an internal example of one consumer product with two proposed case packs. Identify the ordering and billing units and mark only the commercially approved case as active. Trace both through the proposed ERP and warehouse cross-reference, checking that a product-level match alone cannot choose the wrong pack.

What a useful result looks like

The example preserves the distinction between physical item and trade configuration. An unapproved case cannot become orderable because it shares a consumer product description. Reviewers can reproduce each quantity conversion and identify the account-specific evidence needed before implementation.

Keep variable-weight data explainable

Prepare a hypothetical weight-based item with an order estimate, measured dispatch quantity and an agreed price basis. Ask warehouse and finance owners to calculate the invoice from the recorded facts. Introduce a case-versus-kilogram mismatch and specify how the internal validation should detect it before a partner-facing sample is generated.

What a useful result looks like

The calculation is reproducible and unit conversions are explicit. Estimates do not silently replace actual quantities where the assigned process requires measurement. Any rounding, tolerance or correction rule not confirmed by the UK packet remains an open question rather than a guessed default.

Review a market or case-data change

Model a UK item that is proposed for another market or a changed outer pack. List which attributes could change, which records remain historical and which approvals must be reconfirmed. Use the public training only as a question guide, then require the relevant market owner to validate the actual process.

What a useful result looks like

The plan avoids applying a multi-market example as an automatic UK rule or vice versa. Existing orders retain the data version under which they were placed. New identifiers and effective dates are controlled rather than introduced by an unreviewed master-data overwrite.

Separate onboarding evidence

Create a readiness worksheet with successful product setup, an unfinished operational requirement and no confirmed EDI production acceptance. Ask a reviewer to explain the remaining work without using one overall green status. Add a safe technical sample and record exactly what it proves and what it does not.

What a useful result looks like

The final readiness statement names the UK account and tested scenarios while keeping unfinished prerequisites visible. Product, compliance and electronic-exchange evidence cannot substitute for one another. No local test or public guide is described as Tesco certification or permission to send live data.

Common integration questions

Can I keep my existing ERP or accounting system?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Does validation mean my partner has approved production?
No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
Where can I see SignalEDI pricing?
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Authoritative sources

Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.

Tesco questions

Does a Tesco product-induction guide define the UK EDI map?
No. It explains product-data concepts, while your account's technical guide defines the documents and fields exchanged. Use the training to identify possible mismatches, then confirm the applicable UK requirements. Market-specific examples or support contacts should not be silently generalized into a universal Tesco mandate.
Why should Tesco suppliers separate product and case identifiers?
They can represent different levels of the physical product hierarchy. In preparation, trace the consumer item, ordered pack and billed quantity separately, then reconcile them against approved account data. This prevents a correct-looking barcode from hiding an incorrect case conversion or a price applied to the wrong unit.
What counts as Tesco integration readiness?
Evidence for the specific UK account: approved scope, current item data, complete operational prerequisites, tested business cases and the required production acceptance. Keep those milestones distinct. Access to Toolkit, an approved factory or a product record can be useful evidence for one part of onboarding without proving every other part is complete.

Related EDI resources

Prepare your side for partner testing

SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.

Connect now

Topics: Tesco EDI requirements · Tesco supplier EDI · Tesco EDI UK

© 2026 SignalEDI Inc. All rights reserved.