Retailer EDI requirements
Amazon.com.au EDI requirements
Source-qualified document scope
Public sources reviewed 2026-11-09. These notes preserve the scope and access limits of the cited material; your current assigned packet controls implementation.
- 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.
What the cited sources establish
- 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.
Confirm in your current supplier 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.
This is a preparation checklist, not an additional mandate, certified mapping or production approval. Confirm transport, document versions, deductions and timing for your program.
Sources and their limits
- Amazon store identifier reference (Amazon)
Supports: Australian store identifier; reviewed November 9, 2026.
- Amazon SP-API endpoint reference (Amazon)
Supports: Australia belongs to the Far East API endpoint group.
- Amazon business terminology (Amazon)
Supports: Seller and Vendor distinction; not account-specific Australian eligibility.
- Vendor Direct Fulfillment workflow guide (Amazon)
Supports: Separate vendor fulfillment process and API documentation family.
- Vendor Retail Procurement Invoices API (Amazon)
Supports: Vendor invoice interface scope, distinct from a general marketplace accounting feed.