Quick answers
- Can SignalEDI help me connect to Amazon.ca?
- SignalEDI helps prepare mappings, sample validation, and the workflow required for your Amazon.ca 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.ca 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.ca?
- 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.
Plan the integration workflow
SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.
1. Your business system
Identify the source records, system edition, data owner, and allowed access.
2. SignalEDI preparation
Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.
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 checklistPublic sources reviewed 2026-11-09
What the public record confirms
- 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.
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.
- 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.
Connectivity and testing requirements
Connectivity
Confirm whether the current Amazon.ca 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'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.
Questions to resolve from the current buyer 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.
EDI requirements quick reference
Document codes and the planning checklist for this partner also live on the Amazon.ca 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 plansPractice 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.
Prevent cross-store processing
Use synthetic Canadian and United States records with deliberately similar order and SKU references. Run them through the proposed routing rules without sending production traffic. Include a record with no store context and another whose account and marketplace disagree.
What a useful result looks like
Canadian records remain associated with the intended account and store. Missing or conflicting scope stops processing with an actionable explanation. A North America host name alone never selects the business destination, and unrelated orders do not enter the Canadian accounting or warehouse queue.
Trace Canadian order economics
Create a multi-line example with differing pack sizes, a discount and a proposed adjustment. Ask the finance and fulfillment owners to trace quantities and monetary values through the planned mapping. Treat the tax representation as an unresolved configuration item until current account instructions settle it.
What a useful result looks like
The sample preserves item identity, units, currency and reconciliation references. Calculated totals can be explained from source values. No exchange-rate assumption, tax default or rounding change is silently introduced because an existing US integration happened to use it.
Keep fulfillment programs separate
Describe one shipment replenishing Amazon stock and another going directly to a customer. Select the intended program for each before choosing message fields. Include an intentionally mismatched sample to exercise the rule preventing a warehouse replenishment record from entering a customer-direct workflow.
What a useful result looks like
Each sample uses its assigned contract and state transitions. Unsupported scenarios are held for clarification rather than forced into whichever mapper exists. The evidence states the limitations of the exercise and does not imply that every program is enabled for the account.
Reconcile an uncertain submission
Model a timeout after an outbound response or invoice has been sent. Specify where the integration checks the business result and which identifiers it retains. Add an acknowledged rejection that needs correction, keeping it distinct from a request whose outcome remains unknown.
What a useful result looks like
The operator can distinguish accepted, rejected and unconfirmed work. Retrying does not duplicate the business document. Production readiness requires a documented recovery path and real program evidence beyond this local scenario, with customer data and access material kept out of public examples.
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 SP-API store identifiers — Amazon
Supports: Canadian store identifier; public documentation reviewed November 9, 2026.
- Amazon SP-API regional endpoints — Amazon
Supports: Canada uses the North America endpoint; this is an API reference, not an EDI connection packet.
- Amazon SP-API terminology — Amazon
Supports: Distinction between Seller and Vendor business relationships.
- Vendor Retail Procurement Invoices API — Amazon
Supports: Vendors-only invoice API and its documented program scope.
- Vendor Direct Fulfillment workflow — Amazon
Supports: Separate Direct Fulfillment workflow; not confirmation of account eligibility.
Amazon.ca questions
- Does an Amazon.ca Seller account use the same integration as a Vendor account?
- Do not assume that it does. Establish whether you sell through the marketplace or supply Amazon, then identify the fulfillment program. The useful starting artifact is a short account-and-workflow record, not a universal transaction list. Confirm which documentation and operations your Canadian account is actually authorized to use before implementing or requesting access.
- Can an Amazon.ca integration reuse a United States configuration?
- Some technical components may be reusable, but Canadian store selection, account authorization and commercial data need independent checks. Make store identity an explicit input rather than inheriting it from a US default. Review currency, addresses, products and accounting treatment against the Canadian workflow, and test negative cases where an order belongs to the wrong store.
- What proves that an Amazon.ca connection is ready for production?
- Evidence should cover the specific account and program, not only a successful API call or valid EDI envelope. Retain representative mapping results, confirmed business outcomes, exception handling and the applicable production approval. The advisory exercises below help organize that evidence; they are not Amazon's official certification script or proof that SignalEDI has a deployed connection.
Related EDI resources
- Customer requires EDI guide turns the buyer packet into a scoped implementation checklist.
- QuickBooks EDI integration explains supported accounting workflows. Confirm system edition and document scope; it does not establish a connector for this program.
- Managed EDI onboarding is an optional paid path when your team wants help coordinating the scoped partner workflow.
- Walmart EDI requirements covers publicly documented supplier interfaces and buyer-packet boundaries for Walmart programs.
- EDI requirements checker drafts a local readiness checklist without saving buyer data.
Prepare your side for partner testing
SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.
Connect nowTopics: Amazon.ca EDI requirements · Amazon.ca supplier EDI · Amazon.ca EDI CA