Skip to main content

Amazon.co.uk EDI: requirements and onboarding

Scope an Amazon.co.uk connection by UK store, business relationship and fulfillment program. Build reliable order, shipment and invoice controls without importing another country's or another Amazon program's assumptions.

Quick answers

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

  • The official SP-API store table lists the United Kingdom as A1F83G8C2ARO7P. Amazon places the UK on https://sellingpartnerapi-eu.amazon.com, its Europe endpoint. The API region is a technical routing designation, not a statement that every European commercial or tax rule applies to UK transactions.
  • Amazon's Seller and Vendor relationships are distinct. Public documentation also separates Vendor Retail Procurement from Vendor Direct Fulfillment. Identify the account and program before deciding which order, shipment, inventory or invoice interface belongs in the project.
  • Amazon's Direct Fulfillment documentation describes acknowledgement before label creation and a separate shipment-confirmation step. This is a program-specific sequence, not a universal rule for every Amazon.co.uk seller or every form of vendor supply.
  • This review covers public sources available on November 9, 2026. It does not verify private UK vendor agreements, current account-specific EDI specifications, enabled API roles or approval to exchange live data. No SignalEDI certification or commercial relationship is implied.

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.

  • UK account scope: record the legal supplier or seller, marketplace, fulfillment program and business contact. If the business also trades in continental Europe, maintain a separate scope record for each relationship rather than assuming the regional API host makes them interchangeable.
  • Purchasing and response messages: obtain the applicable guide for order receipt, changes and acceptance. Establish how buyer references, line identifiers and delivery destinations survive translation into the ERP, including cases where a familiar SKU appears more than once.
  • Fulfillment evidence: agree which record represents packed goods, issued labels, physical dispatch and accepted shipment confirmation. These events can occur at different times. Define the operational owner and correction process for a package that changes after the first label is generated.
  • Financial documents: confirm whether you are implementing vendor invoices, credit notes or a marketplace accounting feed. Keep currency, tax data and cross-border information attached to their source documents, and obtain specialist guidance for legal or tax decisions rather than inferring them from API geography.

Connectivity and testing requirements

Connectivity

Confirm whether the current Amazon.co.uk 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.

  • The official SP-API store table lists the United Kingdom as A1F83G8C2ARO7P. Amazon places the UK on https://sellingpartnerapi-eu.amazon.com, its Europe endpoint. The API region is a technical routing designation, not a statement that every European commercial or tax rule applies to UK transactions.
  • Amazon's Seller and Vendor relationships are distinct. Public documentation also separates Vendor Retail Procurement from Vendor Direct Fulfillment. Identify the account and program before deciding which order, shipment, inventory or invoice interface belongs in the project.
  • Amazon's Direct Fulfillment documentation describes acknowledgement before label creation and a separate shipment-confirmation step. This is a program-specific sequence, not a universal rule for every Amazon.co.uk seller or every form of vendor supply.
  • This review covers public sources available on November 9, 2026. It does not verify private UK vendor agreements, current account-specific EDI specifications, enabled API roles or approval to exchange live data. No SignalEDI certification or commercial relationship is implied.

Questions to resolve from the current buyer packet

  • Write the UK business scenario in plain language before mapping fields. Identify who buys the product and who ships it, and separate stock delivered to Amazon from orders fulfilled directly to an end customer.
  • Confirm the correct store context even when an application already uses the Europe endpoint. Review how the ERP distinguishes UK activity from orders, inventory and financial postings for other markets.
  • Obtain the latest account-specific instructions and name the document owner. Where access is gated, record the missing map or approval as an open dependency rather than filling gaps with another vendor's implementation.
  • Review UK warehouse cutoffs and event timestamps using the agreed business clock. Preserve the original timestamp and offset so changes between GMT and British Summer Time do not create ambiguous shipment histories.
  • Agree how cancellations, shortages, corrected quantities and invoice adjustments are represented for the selected program. Do not add partial fulfillment behavior merely because it is supported elsewhere in the business.
  • Keep approved program behavior, local test results and Amazon production evidence separate. Recheck account readiness and unresolved errors before cutover; a working transport connection cannot settle a rejected business document.

EDI requirements quick reference

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

Keep UK and EU account contexts distinct

Prepare two synthetic orders for the same product, one assigned to the UK relationship and one to a different European store. Exercise routing, inventory reservation and financial posting with explicit account context. Include an ambiguous order to check that the integration does not guess from a shared endpoint.

What a useful result looks like

Each record stays with its intended commercial relationship and destination. Ambiguous records enter an exception queue with enough information to resolve them. A reused API client cannot silently merge UK and continental activity or imply authorization for an account outside the approved scope.

Exercise a seasonal clock change

Create synthetic warehouse events around a UK daylight-saving transition, including a timestamp that would be ambiguous without an offset. Trace order receipt, packing, dispatch and transmission as separate events. Ask the operations owner to identify which business cutoff applies to the sample.

What a useful result looks like

The event sequence is understandable and preserves the original offsets. Cutoff evaluation uses the agreed business context rather than a server's accidental default. This is an operational recommendation, not a newly asserted Amazon timing mandate or a substitute for current account instructions.

Recover a changed package

Model a packed order whose contents or packaging must change before handover. Determine whether the assigned workflow permits a replacement label, cancellation or another correction. Trace the old and new references in a safe local sample and show how obsolete labels are kept out of the dispatch queue.

What a useful result looks like

Only the intended package is eligible to ship, with a clear audit trail connecting its business references. The integration does not report dispatch merely because a label exists. Unsupported correction behavior remains a documented dependency rather than being invented to make the sample pass.

Reconcile invoice and shipment outcomes

Use a synthetic vendor scenario with a shipment event, an invoice submission and a later rejection or adjustment. Check how the accounting owner discovers the mismatch and how the warehouse record remains available. Keep any API response, business acceptance and financial posting as separate pieces of evidence.

What a useful result looks like

Finance can explain what was shipped, what was submitted and what was accepted. Corrections retain the original identifiers and do not create duplicate receivables. A local demonstration remains advisory until the specific account workflow and production permissions are independently confirmed.

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.co.uk questions

Does Amazon.co.uk use the same API region as other European stores?
Amazon lists the UK under its Europe SP-API endpoint. That shared host does not select the correct store, establish account access or make commercial requirements identical across countries. Keep the UK marketplace and business relationship explicit in the configuration, and review other countries as separate operating scopes when the application supports them.
Does Amazon.co.uk require the same EDI documents from every supplier?
This public review does not establish a universal UK transaction matrix. Requirements depend on the assigned account and fulfillment program, and some implementation materials are available only through authorized supplier channels. Obtain that packet before committing to document codes, transport, versions or timing. An API example is useful context but does not replace an EDI agreement.
How should an Amazon.co.uk team plan for shipment changes?
First separate a generated label from physical dispatch and from Amazon's recorded business outcome. Then use the correction or cancellation behavior permitted by your program. The recommended exercises below explore those boundaries without prescribing an unverified UK rule. Retain the original business references so warehouse staff and finance can reconcile the final result.

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.co.uk EDI requirements · Amazon.co.uk supplier EDI · Amazon.co.uk EDI UK

© 2026 SignalEDI Inc. All rights reserved.