Retailer EDI requirements
Amazon.co.uk EDI requirements
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.
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.
- 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.
What the cited sources establish
- 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.
Confirm in your current supplier 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.
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 SP-API store identifiers (Amazon)
Supports: United Kingdom store identifier, checked November 9, 2026.
- Amazon SP-API endpoints (Amazon)
Supports: UK routing through the Europe SP-API endpoint; not a customs or EDI mandate.
- Amazon Seller and Vendor terminology (Amazon)
Supports: Different Seller and Vendor business models.
- Amazon Vendor Direct Fulfillment workflow (Amazon)
Supports: Program-specific order, label and shipment-confirmation sequence.
- Amazon Vendor Retail Procurement invoices (Amazon)
Supports: Separate vendor invoice API family and scope.