Skip to main content

Australia Post EDI: requirements and onboarding

Plan Australia Post shipping integration around the eligible contract account and the Shipping and Tracking API workflow. Separate label generation, order lodgement, physical handover and tracking instead of presenting a generic retail EDI document matrix.

Quick answers

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

  • Australia Post's official integration page says its Shipping and Tracking APIs require an Australia Post eParcel or StarTrack contract. It describes shipment management, labels, order summaries and tracking, with Australia Post and StarTrack services available through the integration subject to account scope.
  • The Developer Centre separates Shipping and Tracking from the Postage Assessment Calculator and Delivery Choices. It directs contract-rate calculations to Shipping and Tracking rather than the general postage calculator, and provides separate testbed and production-registration paths.
  • The public Developer Centre FAQ states that certification is not required for Shipping and Tracking API use, while registration and eligibility still apply. Do not turn that statement into a claim that every account is automatically enabled or that a particular provider is officially certified.
  • Sources were reviewed on November 9, 2026. Some developer-reference pages exposed search-index text but no readable page body, and authenticated account entitlements were not checked. No universal X12/EDIFACT packet, SignalEDI partnership or live Australia Post connection is established by this review.

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.

  • Contract and account scope: identify the eParcel or StarTrack relationship, charge account, shipping locations and authorized products. Distinguish the business's chosen contracting route from a general consumer or small-business shipping login before planning direct API access.
  • Shipment and item specification: obtain the current schema for the selected service and record item identifiers, sender references, addresses, dimensions, weight and product choices. Confirm which values come from the order system and which are determined during packing.
  • Labels and lodgement record: define how shipment creation, label retrieval, order summary or lodgement and physical dispatch relate in the warehouse. Keep those stages distinct so an electronic label cannot accidentally trigger a customer message claiming the parcel has already been handed over.
  • Tracking and reconciliation scope: retain the identifiers needed to connect carrier events with customer orders and operational exceptions. If invoice data or an older file-based service is also needed, obtain its separate account instructions rather than deriving billing EDI requirements from the shipping API.

Connectivity and testing requirements

Connectivity

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

  • Australia Post's official integration page says its Shipping and Tracking APIs require an Australia Post eParcel or StarTrack contract. It describes shipment management, labels, order summaries and tracking, with Australia Post and StarTrack services available through the integration subject to account scope.
  • The Developer Centre separates Shipping and Tracking from the Postage Assessment Calculator and Delivery Choices. It directs contract-rate calculations to Shipping and Tracking rather than the general postage calculator, and provides separate testbed and production-registration paths.
  • The public Developer Centre FAQ states that certification is not required for Shipping and Tracking API use, while registration and eligibility still apply. Do not turn that statement into a claim that every account is automatically enabled or that a particular provider is officially certified.
  • Sources were reviewed on November 9, 2026. Some developer-reference pages exposed search-index text but no readable page body, and authenticated account entitlements were not checked. No universal X12/EDIFACT packet, SignalEDI partnership or live Australia Post connection is established by this review.

Questions to resolve from the current buyer packet

  • Confirm the eligible contract and authorized products first. An existing online shipping account or a familiar Australia Post logo in another platform does not establish the direct interface or entitlement required for this project.
  • Choose the correct API family for the business outcome. Separate general postage estimates, contract shipping, delivery choices and tracking requirements so an available calculator is not used as proof of contract pricing.
  • Obtain the current technical reference and account onboarding guidance through the authorized channel. Record unresolved access or documentation questions and confirm the test environment before issuing any request that could create a real shipment.
  • Review package data after packing, not only at checkout. Agree who owns final dimensions, weight, address corrections and product selection, and how those values remain linked to the source customer order.
  • Define the warehouse handover event and the customer-facing status that follows it. Plan retries, repeated tracking input and interrupted lodgement without assuming that every successful request represents physical movement.
  • Complete the actual production-access process and operational checks before live use. State which account, products and scenarios were exercised; advisory samples and testbed responses do not establish a production connection.

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.

Match the contract to the selected interface

Prepare a synthetic project record with its intended charge account, contract type and shipping products. Compare it with the selected API documentation and environment. Include a request for a product that has not been confirmed for the account, without making any live call.

What a useful result looks like

The implementation cannot infer entitlement from a generic login or an available catalog entry. Unconfirmed products and access requirements remain explicit dependencies. The readiness statement names the precise contract scope and distinguishes test access from production approval.

Validate final packed-item data

Create a customer order whose estimated parcel measurements change after packing. Trace final weight, dimensions, address and service selection into the proposed shipment request. Include a missing measurement and a unit mismatch to reveal whether the system guesses or asks for correction.

What a useful result looks like

The warehouse owns a clearly defined final record, and incompatible or missing data is visible before lodgement. Source values and conversions remain explainable. The integration does not silently use an estimate as measured truth or switch to another product to conceal an invalid shipment.

Separate labels from physical handover

Model a shipment with a generated label that is not yet handed over, then a properly lodged and dispatched shipment. Review the order-management and customer-notification states for both. Add an interrupted lodgement attempt whose result must be checked before repeating it.

What a useful result looks like

Customers are not told that goods have moved solely because a label exists. The warehouse can distinguish prepared, lodged and physically dispatched work according to its agreed process. Recovery investigates uncertain outcomes and avoids duplicate shipment creation or misleading status updates.

Reconcile delayed and repeated tracking events

Use synthetic events arriving late or more than once for a multi-item customer order. Preserve carrier timestamps and item references, then review the rule for presenting the order's overall status. Include an unknown item identifier that requires investigation rather than a guessed match.

What a useful result looks like

Repeated events do not create duplicate notifications, and one delivered item does not silently complete every item on the order. Unknown references remain actionable. The test records local reconciliation behavior while leaving real service access, current limits and production performance to account-specific verification.

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.

Australia Post questions

Does Australia Post require a universal EDI transaction set for shipping?
This review does not establish one. The public sources describe named shipping APIs and account eligibility rather than a universal retail purchase-order, ASN and invoice matrix. If your contract assigns a file-based or EDI service, obtain that specific packet. Do not label an API integration as X12 or EDIFACT merely because the page uses EDI in its address.
Can any Australia Post online account use Shipping and Tracking APIs?
Confirm the eligible contract and production-access process rather than assuming that an online login is enough. The official integration guidance identifies eParcel or StarTrack contracts for this API route. Other shipping products can have different arrangements, so check the intended account and service before choosing documentation or promising implementation scope.
Does Australia Post testbed success mean parcels can be shipped live?
No. Keep local mapping, testbed behavior, production access and physical warehouse readiness separate. Verify the actual account and product entitlements, then confirm how labels, lodgement and handover work in the chosen process. The exercises below are advisory and cannot prove an active SignalEDI connection or an official provider relationship.

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

© 2026 SignalEDI Inc. All rights reserved.