🔗 Amazon Vendor Central: Data Mapping & Synchronisation
This guide details exactly how data flows between your Amazon Vendor Central environment and Optiply. It outlines the required AWS regional endpoints, the two different synchronisation setups (Secondary vs. Full), and the specific mapping logic used to translate your e-commerce data.
🌍 1. AWS Regions & Connection Setup
Amazon Vendor Partner API endpoints are tightly associated with particular AWS Regions. The AWS Region is part of the credential scope required for calculating a secure signature when calling the API.
⚠️ Crucial Connection Rule:
Each connection can only link to one region. If you want to pull data from multiple global regions, you must establish multiple, separate integration links in Optiply.
Selling Region (Marketplaces) | Endpoint | AWS Region |
North America (Canada, US, Mexico, Brazil) |
|
|
Europe (Spain, UK, France, Belgium, Netherlands, Germany, Italy, Sweden, Poland, Saudi Arabia, Egypt, Turkey, UAE, India) |
|
|
Far East (Singapore, Australia, Japan) |
|
|
⏱️ 2. Synchronisation Overview
Depending on your specific workflow needs, Optiply supports two different integration setups (or "Flavours") for Amazon Vendor Central.
Setup 1:
SECONDARY (Sell Orders Only)
This setup is used when Optiply already pulls your products from a primary source (like WooCommerce or Shopify), and Amazon is strictly an additional sales channel.
Entity | Sync FROM -> TO | Frequency |
Sell Orders | Amazon > Optiply | Every 30 minutes |
Important Matching Rule: To match products from Amazon to your main integration, your primary system must have Products with EAN Codes to match with Amazon Vendor. While EAN is the main key in Amazon, some customers use our Optiply skuCode as the EAN on Amazon to bridge this gap.
Setup 2: FULL (Products + Sell Orders)
This setup is used when Amazon is treated as a primary data source for both your catalogue and your sales.
Entity | Sync FROM -> TO | Frequency |
Products | Amazon > Optiply | Every 30 minutes |
Sell Orders | Amazon > Optiply | Every 30 minutes |
🗺️ 3. Data Mapping Details
Products
(Endpoint: /catalog/2022-04-01/items - Searches for and returns a list of Amazon catalogue items and associated information).
Optiply Field | Amazon Field | Notes |
Name |
|
|
SKU Code |
|
|
EAN Code |
|
|
Price |
|
|
Unlimited Stock |
| Hardcoded |
Stock Level |
|
|
Remote ID |
|
|
Sell Orders
(Endpoint: /orders/v0/orders - These fields map the overarching data for the entire transaction).
Optiply Field | Amazon Field | Notes |
Total Value |
|
|
Placed Date |
|
|
Sell Order ID |
|
|
Note: The Orders.OrderStatus field contains the specific status of the order.
Sell Order Lines
(Endpoint: /orders/v0/orders/{orderId}/orderItems - These fields map the individual products within that specific transaction).
Optiply Field | Amazon Field | Notes |
Product ID |
|
|
Quantity |
|
|
Subtotal Value |
|
|
⚠️ Sell Order Limitation:
We do not sync subsequent Sell Order changes. Line changes, line deletions, or new lines added to existing Sell Orders in Amazon after the initial sync will not be updated in Optiply.
❓ 4. Frequently Asked Questions (FAQs)
Can I connect both my European and North American Amazon stores to the same integration?
No. Amazon requires separate API endpoints for different global regions. You will need to create one integration for your European marketplaces and a second, separate integration for your North American marketplaces.
If a customer changes their order on Amazon, will Optiply update it?
No. Optiply does not sync order changes. Once a Sell Order is pulled into Optiply, any subsequent line changes, deletions, or additions made in Amazon will not be reflected in our system.
I am using the "Secondary" setup. Why aren't my Amazon orders linking to my products?
When using Amazon as a secondary channel, Optiply relies on the EAN Code to match the Amazon order to the product data pulled from your primary webshop (like Shopify or WooCommerce). If your primary webshop products do not have matching EAN Codes (or SKUs acting as EANs), the orders cannot link properly.