Skip to main content

Coles EDI: requirements and onboarding

Separate Coles merchandise, non-resale purchasing, random-weight invoicing and delivery standards so the chosen electronic workflow matches both the commercial account and the goods actually supplied.

Quick answers

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

  • Coles Group's supplier page separates goods for resale from goods not for resale and directs both to Supplier Central. The distinction matters before mapping: retail merchandise and services used to operate stores are not automatically the same order-to-cash program.
  • Supplier Central's indexed EIDC Random Weight article describes an electronic process for receiving orders and submitting invoices for distribution centres, including an INVOIC reference. Direct access returned a rendering error during the November 9, 2026 review, so detailed attached guides and account-specific rules were not verified.
  • The official Supplier Central updates index records a July 30, 2026 Coles Liquor delivery-policy update clarifying paperwork for B2B versus non-B2B suppliers. That dated listing is evidence to obtain the current liquor policy, not permission to apply liquor rules to every Coles supply route.
  • Coles Collect publishes a resources entry point for supply standards, transport and handling guidance. These operational materials are separate from message acceptance. No source reviewed establishes a SignalEDI certification or one universal Coles document matrix.

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.

  • Supply agreement and program classification: establish GFR or GNFR, grocery or liquor where relevant, delivery destination and legal customer. Ask whether the assigned process is integrated B2B, EIDC Random Weight or another explicitly approved arrangement.
  • Order and invoice guides: obtain current field definitions, product references, units, tax handling and correction semantics. For weight-based products, distinguish an ordered estimate from actual measured quantity and the basis used to calculate the invoice.
  • Shipment and receiving documentation: confirm the notice, docket, label and appointment requirements for the actual lane. Do not assume that electronic transmission eliminates paperwork or that one category's delivery checklist applies to another.
  • Product and packaging records: identify the authoritative item hierarchy and handling information. Ask which changes require a master-data update and how the effective date is coordinated with future orders and already packed stock.

Connectivity and testing requirements

Connectivity

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

  • Coles Group's supplier page separates goods for resale from goods not for resale and directs both to Supplier Central. The distinction matters before mapping: retail merchandise and services used to operate stores are not automatically the same order-to-cash program.
  • Supplier Central's indexed EIDC Random Weight article describes an electronic process for receiving orders and submitting invoices for distribution centres, including an INVOIC reference. Direct access returned a rendering error during the November 9, 2026 review, so detailed attached guides and account-specific rules were not verified.
  • The official Supplier Central updates index records a July 30, 2026 Coles Liquor delivery-policy update clarifying paperwork for B2B versus non-B2B suppliers. That dated listing is evidence to obtain the current liquor policy, not permission to apply liquor rules to every Coles supply route.
  • Coles Collect publishes a resources entry point for supply standards, transport and handling guidance. These operational materials are separate from message acceptance. No source reviewed establishes a SignalEDI certification or one universal Coles document matrix.

Questions to resolve from the current buyer packet

  • Name the specific Coles supplier program and responsible account owner before choosing a map. Keep the corporate supplier entry point as navigation, not as proof that all business units accept identical messages.
  • For random-weight scope, agree where measured weight is captured, which unit is transmitted and how price extensions and rounding are calculated. Confirm the actual guide instead of converting cases to kilograms using a fixed guess.
  • Review the current Supplier Central change log with logistics and finance. Record the particular documents relevant to your category, and obtain the revised policy itself before changing a production control.
  • Compare physical delivery evidence with the electronic record, including shortages, damaged goods and rejected stock. Give exceptions a shared reference so warehouse and receivables teams do not resolve the same event differently.
  • Prepare separate technical, operational and commercial readiness evidence. Keep required account approval and unresolved source access issues explicit; successful internal parsing cannot substitute for Coles acceptance or physical supply compliance.

EDI requirements quick reference

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

Classify merchandise and indirect purchasing

Compare two synthetic orders: retail goods intended for resale and a service used to operate a distribution centre. Identify the contracting entity, supplier account, relevant portal instructions and billing owner for each. Ask the implementation team which documents are confirmed and which require separate procurement guidance.

What a useful result looks like

The service invoice does not inherit merchandise shipment requirements by default. Each workflow is scoped from its actual account instructions. Shared customer branding cannot conceal a different approval process, receiving model or financial reference.

Calculate a random-weight invoice

Create a safe example with an estimated order weight, a different measured shipment weight and a price expressed per agreed unit. Have warehouse staff identify the measurement source and finance calculate the extended amount and tax. Introduce a unit mismatch and a rounding difference without inventing any Coles tolerance.

What a useful result looks like

The proposed mapping preserves the agreed basis of calculation and exposes mismatches before submission. Reviewers can reproduce the total from the recorded quantity and price. Any partner-specific tolerance or correction rule remains a question until the assigned guide confirms it.

Check the paperwork branch

For an actual in-scope category, prepare a delivery checklist and mark the supplier's approved electronic trading mode. Compare the current delivery policy with the draft docket and shipment evidence. If liquor is in scope, verify the revised B2B or non-B2B instructions rather than relying on a pre-update checklist.

What a useful result looks like

The operator has a category-specific document list with a source revision and owner. Electronic submission and physical paperwork are checked independently. An outdated checklist or another business unit's document cannot be treated as sufficient receiving preparation.

Reconcile a rejected portion of delivery

Model a shipment where only part of the goods are accepted. Keep the original order, actual dispatch, receiving evidence and proposed invoice side by side. Ask the team to identify whether the applicable process calls for revised billing, a credit or another agreed action, and preserve the original business references.

What a useful result looks like

The final explanation distinguishes ordered, shipped, received and billed quantities. A financial correction is supported by evidence and account instructions rather than an automatic overwrite. The exercise does not imply that a test was submitted to or approved by Coles.

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.

Coles questions

Can Coles random-weight invoices use a fixed case conversion?
Do not assume so. Establish the approved ordering, measurement and billing units from the assigned guide, then capture the actual quantity at the correct operational step. Test price extensions and rounding with finance. A fixed case estimate can be useful for planning but should not silently replace the measured basis required by the account.
Does Coles electronic trading remove delivery paperwork?
That depends on the program and current delivery policy. The official change index specifically flags a liquor distinction between B2B and non-B2B paperwork. Obtain the policy for your lane and check it with warehouse staff; a message receipt does not prove the driver has the necessary receiving documents.
What should a new Coles integration confirm before testing?
Confirm the legal customer, GFR or GNFR scope, product category, delivery route, approved trading process and current technical packet. Then test the actual identifiers and units your systems will use. Keep any inaccessible attachment or unresolved requirement in the readiness record rather than filling it with another retailer's assumptions.

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

© 2026 SignalEDI Inc. All rights reserved.