Skip to main content

ASDA EDI: requirements and onboarding

Separate ASDA resale, non-resale and George supplier entry paths, then confirm the assigned current EDI account instead of inheriting Walmart-era identifiers or treating product discovery as technical approval.

Quick answers

Can SignalEDI help me connect to ASDA?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your ASDA 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 ASDA 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 ASDA?
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

  • ASDA's official Becoming a Supplier page distinguishes goods for resale, goods not for resale and George Clothing. Resale product submissions use RangeMe, GNFR enquiries use a separate procurement form and George has its own supplier enquiry route. These are distinct commercial entry paths.
  • ASDA's public OneTime portal states that it is for suppliers issued credentials for the ASDA platform. The accessible login page does not disclose a current technical implementation packet or prove that a particular supplier, provider or account has completed onboarding.
  • ASDA's current supplier-relations page describes its Supplier Charter introduced in 2025 and separates local supplier development from global sourcing through IPL. Commercial or sourcing participation should not be confused with a common EDI document scope.
  • The public sources reviewed on November 9, 2026 do not establish one current ASDA transaction/version matrix. Do not reuse Walmart identifiers, US X12 mandates or historical migration instructions without current account evidence. This page is preparation guidance, not SignalEDI certification or approval.

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.

  • Commercial onboarding record: identify GFR, GNFR or George, the contracting entity, category and assigned supplier account. Keep a RangeMe proposal or enquiry separate from an approved listing, purchasing relationship and active technical account.
  • Assigned EDI packet: obtain current message types, syntax, versions, transport and test expectations from the account's authorized route. Confirm which order, shipment, invoice and correction messages are required for the actual delivery program.
  • Product, location and supplier identifiers: build a current cross-reference using approved ASDA records. If historical identifiers exist, retain an explicit migration mapping with effective dates instead of using the old code as an unexplained default.
  • Invoice and operational exception evidence: establish the links among order, dispatch, receipt, invoice and any adjustment. Keep finance queries, portal visibility and technical acceptance separate so a missing status does not become duplicate billing.

Connectivity and testing requirements

Connectivity

Confirm whether the current ASDA 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.

  • ASDA's official Becoming a Supplier page distinguishes goods for resale, goods not for resale and George Clothing. Resale product submissions use RangeMe, GNFR enquiries use a separate procurement form and George has its own supplier enquiry route. These are distinct commercial entry paths.
  • ASDA's public OneTime portal states that it is for suppliers issued credentials for the ASDA platform. The accessible login page does not disclose a current technical implementation packet or prove that a particular supplier, provider or account has completed onboarding.
  • ASDA's current supplier-relations page describes its Supplier Charter introduced in 2025 and separates local supplier development from global sourcing through IPL. Commercial or sourcing participation should not be confused with a common EDI document scope.
  • The public sources reviewed on November 9, 2026 do not establish one current ASDA transaction/version matrix. Do not reuse Walmart identifiers, US X12 mandates or historical migration instructions without current account evidence. This page is preparation guidance, not SignalEDI certification or approval.

Questions to resolve from the current buyer packet

  • Confirm the supplier entry path before gathering technical requirements. A service provider supplying logistics or software should not automatically inherit a resale merchandise mapping, and a George enquiry does not establish grocery account scope.
  • Obtain the current assigned onboarding instructions rather than treating the public portal notice as a project schedule. Record what has actually been issued and approved for your account, including the responsible commercial and technical owners.
  • Inventory legacy references carefully. Compare customer numbers, location IDs, item identifiers and message envelopes with the current packet; do not assume a field remains valid because it appears in an old Walmart-era export.
  • Give product discovery, listing approval, operational readiness and electronic testing separate milestones. Track missing specifications as unresolved questions and use safe synthetic data until the correct scope and environment are confirmed.
  • Design a changeover reconciliation plan if replacing a previous connection. Identify ownership of outstanding orders, delayed acknowledgements and invoice corrections, then verify the first production scope through the required account acceptance process.

EDI requirements quick reference

Document codes and the planning checklist for this partner also live on the ASDA 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.

Choose the correct supplier entry path

Prepare three synthetic proposals: grocery merchandise, an indirect service and a clothing range. Map each to the commercial route described on ASDA's official supplier page, then list the additional information needed before technical design. Include an attractive product submission that has not received listing approval.

What a useful result looks like

The plan does not confuse an enquiry with an active account or apply grocery shipment assumptions to every supplier. Each proposal has a clearly identified next evidence requirement. The draft listing remains outside production order and invoice processing until the relationship is confirmed.

Audit legacy identifier assumptions

Take a harmless sample of an older customer configuration and compare every external reference with the current assigned ASDA packet. Mark the source and effective date for supplier, location, product and envelope identifiers. Include one old value that happens to resemble a current one to test whether superficial similarity bypasses review.

What a useful result looks like

Every production reference is supported by current account evidence. Old values remain available for historical reconciliation but do not automatically route new documents. Unconfirmed mappings are held for clarification rather than silently translated to guessed identifiers.

Preserve open documents during provider change

Create a synthetic cutover register containing an outstanding order, a dispatched shipment, an invoice awaiting business acceptance and a later correction. Assign an owner and route for each before and after the switch. Simulate a delayed response arriving through the previous provider and describe how it is matched.

What a useful result looks like

The transition retains one coherent business history even when transport systems change. Documents are not resent merely because the new platform cannot yet see them. The operator can explain which connection owns each next action and what evidence is needed to resolve uncertainty.

Separate technical and commercial readiness

Build an example readiness record where product approval is complete but a required message guide is missing, then another where a sample parses correctly but receiving arrangements are unresolved. Ask the implementation and operations owners to identify the exact remaining work without collapsing both cases into a single success flag.

What a useful result looks like

The readiness statement names the verified account, documents and scenarios, and keeps blockers visible. A login, local parser result or commercial listing cannot stand in for ASDA production acceptance. No unsupported deadline, certification or live-connection claim is attached to the exercise.

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.

ASDA questions

Does submitting products to ASDA through RangeMe complete EDI onboarding?
No. It is a commercial discovery route. Keep buyer review, approved item setup, supplier account activation, logistics preparation and electronic acceptance separate. A reviewed product profile should not trigger production documents or be treated as evidence that a particular provider or technical map is approved.
Can an ASDA supplier retain a Walmart-era EDI setup?
Only where current ASDA instructions explicitly confirm the relevant identifiers and behavior. Compare the active packet with the old configuration rather than relying on historical ownership or a familiar document code. Preserve old transaction history, but require evidence before using legacy references for new orders or invoices.
What should ASDA suppliers verify when changing EDI providers?
Confirm the account, current message scope, approved connection route and who owns open documents during the transition. Test delayed orders, uncertain receipts and corrections related to old invoices. The change should preserve business identity and reconciliation history rather than treating the new technical connection as a fresh commercial account.

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: ASDA EDI requirements · ASDA supplier EDI · ASDA EDI UK

© 2026 SignalEDI Inc. All rights reserved.