Skip to main content

Amazon.com.au EDI: requirements and onboarding

Prepare an Amazon.com.au integration with explicit Australian store routing, program eligibility and fulfillment ownership. Connect the right order and financial workflow rather than cloning a North American or European setup.

Quick answers

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

  • Amazon identifies the Australian store as A39IBJ37TRP1C6 and assigns it to https://sellingpartnerapi-fe.amazon.com, the Far East SP-API endpoint. The name of that region is Amazon's technical grouping; it does not imply that an Australian account should use a Japanese store identifier.
  • Seller marketplace operations and Vendor supply arrangements have different business purposes. Amazon publishes separate Direct Fulfillment and Retail Procurement documentation for vendors. Availability still needs to be checked for the actual Australian account and operation.
  • The public Direct Fulfillment guide includes order acknowledgement, shipping and invoice stages, while the Retail Procurement Invoices reference is explicitly vendors-only. A public API family is not evidence that a particular vendor has been enabled for that program.
  • Sources were reviewed on November 9, 2026. No authenticated Australian vendor packet, trading agreement, EDI transport assignment or account approval was accessed. The recommendations below are planning exercises, not partner certification or proof of a SignalEDI 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.

  • Australian program definition: identify whether the integration supports marketplace selling, stock purchased by Amazon or another assigned vendor fulfillment arrangement. Capture the account, supplier identity, store, business contact and receiving operation as separate pieces of information.
  • Order and item data: obtain the account's authoritative message or API schema and clarify product identifiers, order-line references, pack quantities and permitted response states. Avoid substituting a familiar internal SKU where Amazon expects a different reference.
  • Inventory and dispatch information: determine the system of record for sellable stock, warehouse location, packaging, carrier references and shipment confirmation. Describe how local operational events become electronic messages without assuming that one warehouse timestamp represents all stages.
  • Invoice and adjustment instructions: obtain the permitted financial workflow, including currency representation, source tax data and correction references. Australian store routing does not determine GST treatment or resolve cross-border obligations; those decisions belong with the business and its qualified advisers.

Connectivity and testing requirements

Connectivity

Confirm whether the current Amazon.com.au 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.

  • Amazon identifies the Australian store as A39IBJ37TRP1C6 and assigns it to https://sellingpartnerapi-fe.amazon.com, the Far East SP-API endpoint. The name of that region is Amazon's technical grouping; it does not imply that an Australian account should use a Japanese store identifier.
  • Seller marketplace operations and Vendor supply arrangements have different business purposes. Amazon publishes separate Direct Fulfillment and Retail Procurement documentation for vendors. Availability still needs to be checked for the actual Australian account and operation.
  • The public Direct Fulfillment guide includes order acknowledgement, shipping and invoice stages, while the Retail Procurement Invoices reference is explicitly vendors-only. A public API family is not evidence that a particular vendor has been enabled for that program.
  • Sources were reviewed on November 9, 2026. No authenticated Australian vendor packet, trading agreement, EDI transport assignment or account approval was accessed. The recommendations below are planning exercises, not partner certification or proof of a SignalEDI production connection.

Questions to resolve from the current buyer packet

  • Confirm the Australian marketplace in the project record before reusing an existing Amazon adapter. Review every inherited account, region and environment default for an unintended North America or Europe assumption.
  • Map each requested capability to its actual program documentation and account permission. Keep features that are only possible in a different program outside the committed scope until eligibility is confirmed.
  • Record the Australian warehouse's operating time zone and the timestamps expected by the interface. If stock moves between states, preserve the source location and offset rather than applying a single national clock.
  • Prepare safe examples covering products, units, shortages and corrections. Record questions for the buyer or account owner whenever private requirements are needed; do not treat a plausible field mapping as an agreed rule.
  • Establish how the system identifies previously submitted business documents and checks uncertain results. A timeout should not cause an automatic second shipment confirmation, invoice or inventory adjustment.
  • Complete account-specific acceptance and operational readiness before production. State exactly which scenarios were tested, what remains unverified and who owns each exception, including any missing vendor documentation.

EDI requirements quick reference

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

Reject inherited regional defaults

Inspect a safe copy of the planned configuration and deliberately introduce a North America endpoint or non-Australian store reference. Trace what validates account, store and environment before a request can be queued. Do not use real credentials or issue a live transaction during this review.

What a useful result looks like

Conflicting configuration fails clearly before business data is sent. The account owner can see which environment and Australian scope each sample targets. A successful authentication check does not mask a wrong commercial destination or a workflow that the account is not entitled to use.

Preserve warehouse time-zone meaning

Prepare dispatch and inventory examples from two Australian warehouse locations with different local clock behavior. Include an event close to a date boundary and preserve its offset. Review the conversion into the interface's required format without changing the original business event or inventing a nationwide cutoff.

What a useful result looks like

Ordering and reconciliation remain consistent across warehouse locations. Operations can distinguish the local event date from processing time, and no order is silently moved into the wrong reporting period. Any account-specific cutoff remains a separately verified requirement rather than an assumption embedded in the mapper.

Handle an unavailable item honestly

Create a synthetic order whose requested quantity is no longer available. Consult the selected program's response and cancellation rules before deciding how to represent the shortage. Compare the ERP reservation, outgoing response and warehouse queue, and flag any behavior that the current private packet has not yet resolved.

What a useful result looks like

The sample does not promise inventory that cannot be supplied. Unsupported partial fulfillment or substitute-item behavior is not improvised. The evidence explains which state changed, which references were preserved and what confirmation is still needed before implementing the rule for an actual Australian account.

Separate invoice transmission from acceptance

Model an invoice request followed by a timeout and a second example followed by a known validation failure. Define how to discover the first outcome and how to correct the second. Follow the source order, shipment and invoice references into the accounting record using synthetic data only.

What a useful result looks like

An uncertain submission is investigated before resending, while a confirmed rejection has a traceable correction path. Financial reporting distinguishes queued, submitted and accepted documents. The exercise produces a useful readiness checklist without claiming that a sandbox result demonstrates a live Australian vendor connection.

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.

Amazon.com.au questions

Which regional endpoint applies to Amazon.com.au?
The official endpoint table places Australia in the Far East SP-API group. Configure the Australian store and authorized account independently from that regional selection. A connection that works against another Amazon host is not an Australian production test, and an EDI implementation still needs its own assigned connection details rather than this API address.
Can Amazon.com.au suppliers copy an overseas vendor mapping?
Treat it as a starting component, not an approved Australian specification. Check the business program, account permissions, item references, financial data and fulfillment rules against the current packet. Reuse is safest when the shared transformation is separated from account configuration and every difference is visible, rather than hidden inside country-specific assumptions.
What should an Amazon.com.au integration test beyond a successful request?
Test whether the intended business event is correctly represented and subsequently reconciled. Useful scenarios include wrong-store input, time-zone boundaries, stock changes and submissions with uncertain outcomes. Use the selected program's acceptance evidence to decide readiness. These exercises cannot establish Amazon approval, enable a vendor account or prove an existing SignalEDI service 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: Amazon.com.au EDI requirements · Amazon.com.au supplier EDI · Amazon.com.au EDI AU

© 2026 SignalEDI Inc. All rights reserved.