Skip to main content

Metcash EDI: requirements and onboarding

Distinguish Metcash's Food and Liquor supplier relationships, Sorted delivery workflows and ChargeThrough invoice route before treating every independent-retail order as one EDI program.

Quick answers

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

  • Metcash's official contact page directs prospective Food and Liquor suppliers to separate MetConnect entry points. It separately routes retailer trading-account applications. A supplier selling into the network and an independent retailer buying from it are different account roles.
  • Metcash's Sorted FAQ distinguishes Metconnect relationship management from Sorted order and invoice management for direct-to-store or cross-dock deliveries. It also says expansion to other states or Cross Dock terms requires the trading-terms process. Shared access does not establish identical commercial scope.
  • The current Sorted Easy Invoicing page describes digitizing system-generated PDF invoices. It identifies this as the required route for new ChargeThrough suppliers unless they have an EDI connection, while describing it as an option for existing suppliers. This is not a universal mandate for every Metcash business.
  • Sources were reviewed November 9, 2026. MetConnect pages returned rendering errors, so gated technical packets were not inspected. This guide does not apply historical Express Receiving thresholds as current requirements or claim SignalEDI certification.

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.

  • Trading terms and account scope: identify Food or Liquor, supplier versus retailer role, permitted states and delivery arrangement. Confirm whether warehouse supply, direct-to-store, cross-dock or ChargeThrough is the actual commercial relationship.
  • Order records: establish the approved source of orders, product identifiers, retailer destinations and supplier references. Ask how supplier-initiated orders differ from portal-originated orders before assigning one common matching strategy.
  • Invoices and credits: choose the route authorized for the account, such as the applicable EDI connection or Easy Invoicing workflow. Obtain the current format, product-data and correction instructions rather than submitting through two channels.
  • Physical delivery and reconciliation evidence: record the receiving destination, delivery reference, quantities and any cross-dock handoff. Keep the final retailer, intermediate facility and financial counterparty distinct where the agreement assigns different roles.

Connectivity and testing requirements

Connectivity

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

  • Metcash's official contact page directs prospective Food and Liquor suppliers to separate MetConnect entry points. It separately routes retailer trading-account applications. A supplier selling into the network and an independent retailer buying from it are different account roles.
  • Metcash's Sorted FAQ distinguishes Metconnect relationship management from Sorted order and invoice management for direct-to-store or cross-dock deliveries. It also says expansion to other states or Cross Dock terms requires the trading-terms process. Shared access does not establish identical commercial scope.
  • The current Sorted Easy Invoicing page describes digitizing system-generated PDF invoices. It identifies this as the required route for new ChargeThrough suppliers unless they have an EDI connection, while describing it as an option for existing suppliers. This is not a universal mandate for every Metcash business.
  • Sources were reviewed November 9, 2026. MetConnect pages returned rendering errors, so gated technical packets were not inspected. This guide does not apply historical Express Receiving thresholds as current requirements or claim SignalEDI certification.

Questions to resolve from the current buyer packet

  • Start from the business and trading terms rather than the Metcash name alone. Document the states and delivery modes already approved, then list proposed extensions separately so technical access cannot be mistaken for commercial authorization.
  • Map Metconnect, product management, Sorted and the assigned EDI route to their actual responsibilities. Decide where supplier identity, product data, orders and invoices are maintained and which team owns a correction in each system.
  • For an Easy Invoicing account, compare the system-generated PDF with the approved product data and sample requirements. Keep a reproducible original and a clear error-handling owner rather than assuming that emailing a document completes acceptance.
  • Prevent duplicate billing when an account changes methods. Identify the final invoice handled by the previous route, the first handled by the next and how delayed orders or corrections will be reconciled.
  • Obtain current warehouse or cross-dock technical and delivery instructions for the exact scope. Record any inaccessible guide as an open item; old public implementation thresholds and another division's packet are not substitutes.

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.

Separate supplier and retailer identities

Create an internal example with a manufacturer supplying the network and an independent retailer purchasing goods. Assign their commercial roles, order references and payment relationships before choosing portal records. Include a direct-to-store delivery where the physical receiver and financial counterparty must be checked against the actual agreement.

What a useful result looks like

The account model does not confuse the seller with the buyer or assume that the delivery address identifies the payer. Each reference has a documented owner and purpose. The resulting questions are specific enough to resolve with the assigned account materials.

Validate the chosen invoice route

For a hypothetical approved Easy Invoicing account, prepare a sample PDF from the source accounting system and compare its items, quantities and prices with the product records. For an EDI account, identify the separately assigned technical guide instead. Describe the validation evidence required for each without sending either sample externally.

What a useful result looks like

The workflow follows the confirmed account route and does not treat two available methods as permission to bill twice. Product mismatches are identified before submission. A PDF generated successfully or a file parsed locally is not reported as Metcash acceptance.

Extend state and delivery scope

Model a supplier currently approved for one state and direct-to-store delivery that proposes a second state and a cross-dock arrangement. List the commercial, item-data, destination and delivery questions for the extension. Ask the owner to mark which terms and operational instructions are already confirmed and which remain pending.

What a useful result looks like

The plan distinguishes current trading scope from future capability. Existing login access cannot activate the new lane by itself. Each additional destination has an accountable approval and configuration step rather than inheriting assumptions from the original route.

Reconcile a method change and late correction

Plan a safe cutover between two authorized invoice methods using a synthetic document register. Add an old order that arrives late and a correction relating to an invoice created before the switch. Decide which process owns each record and how operators check status before resubmitting anything.

What a useful result looks like

Every invoice and correction has one owner, a preserved original reference and an explainable route. The cutover cannot silently abandon old exceptions or create a duplicate through the new method. Completion evidence remains tied to the particular account and workflow tested.

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.

Metcash questions

Are Metcash Metconnect and Sorted the same workflow?
They serve related but distinct purposes in the official supplier guidance. Plan where relationship records, product data, orders and invoices belong, and confirm the scope assigned to your account. Access through related systems should not lead to duplicate entry or the assumption that every delivery program has the same technical requirements.
Must every Metcash supplier submit Easy Invoicing PDFs?
No universal requirement is supported. The published rule is specifically framed around new ChargeThrough suppliers and includes an EDI exception; existing suppliers are described separately. Confirm your account's approved route and current requirements before changing a submission method or assuming a PDF process replaces an existing EDI connection.
Can a Metcash supplier expand to another state without revisiting setup?
Do not assume that technical access grants that scope. Confirm trading terms, destinations, item availability and delivery arrangements for the new state. Then compare the document and reconciliation requirements. Keep the proposed expansion out of production until both the commercial and technical owners have confirmed what changes.

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: Metcash EDI requirements · Metcash supplier EDI · Metcash EDI AU

© 2026 SignalEDI Inc. All rights reserved.