Skip to main content

Amazon.ca EDI requirements

Plan an Amazon.ca integration around the Canadian store and your actual Seller or Vendor program. Separate retail purchasing, Direct Fulfillment and marketplace selling before mapping orders, shipping information or invoices.

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.

  • Account and program record: identify the Canadian store, selling entity, supplier or seller identity, fulfillment arrangement and business owner. Keep those separate from application identifiers so a technical configuration change cannot quietly move transactions into a different commercial relationship.
  • Order and response contract: obtain the specification assigned to the account, including line references, acceptance or rejection behavior and permitted corrections. Do not map a marketplace customer order into a retail purchase-order response merely because both contain products and quantities.
  • Shipment and inventory scope: determine whether the project concerns inbound stock for Amazon, customer-direct fulfillment or another approved process. Record which system owns available inventory, package details, carrier selection and shipment completion, including the evidence required to reconcile exceptions.
  • Invoice and settlement scope: distinguish invoices you issue to Amazon as a vendor from marketplace settlement information. Confirm currency, tax fields, invoice identity and adjustment treatment using current account guidance; a Canadian store identifier does not specify tax treatment.

What the cited sources establish

  • Amazon's official store table identifies Canada as A2EUQ1WTGCTBG2. Its endpoint reference places Canada in the North America region at https://sellingpartnerapi-na.amazon.com. These are SP-API configuration facts, not Canadian EDI transport requirements.
  • Amazon distinguishes sellers, who sell their own goods through the marketplace, from vendors supplying Amazon. Vendor Retail Procurement and Vendor Direct Fulfillment have separate API documentation. A Canadian storefront does not erase those program boundaries or grant access to every vendor operation.
  • The Vendor Retail Procurement Invoices API is listed as vendors-only. Direct Fulfillment has its own order, shipping and payment workflow. Use those public references to identify the appropriate documentation family, then confirm the features enabled for your account.
  • Public documentation was reviewed on November 9, 2026. Authenticated Vendor Central instructions, supplier-specific EDI maps, commercial agreements and production permissions were not inspected. This guide does not establish a SignalEDI partnership, Amazon certification or a live Canadian connection.

Confirm in your current supplier packet

  • Start with one Canadian business scenario and write its direction of exchange: who places the order, who fulfills it, who receives the goods and who pays. Resolve that scenario before selecting an EDI message or API operation.
  • Keep marketplace identification explicit in configuration and logs. A shared North America endpoint is not enough to distinguish Canada from other stores, especially when the same application serves several accounts.
  • Request the current program packet through the account's authorized channel. Record revision, business scope and unanswered questions without copying credentials or personal customer information into a planning document.
  • Assign owners for SKU cross-references, quantities, pack sizes, addresses and monetary values. Confirm how the accounting and warehouse systems represent each field before translating it into an outbound document.
  • Plan exception handling for unavailable stock, rejected responses, duplicate requests and uncertain outcomes. Keep the original order and line references visible through each correction rather than replacing the history.
  • Approve production separately from sample mapping. Record the actual account, interface, tested scenarios, operational support path and unresolved limitations before any live order, shipment or financial document is transmitted.

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

Read the full partner planning guide and preparation exercises

© 2026 SignalEDI Inc. All rights reserved.