Elbuz pulls the listings of your Amazon seller account through the official SP-API and brings them into the base catalog, where prices and stock are managed together with your other channels.
When you need this:
- Large assortment, several channels: prices come from markup rules, stock from supplier price lists.
- You sell in several Amazon countries: one template per marketplace, one shared catalog.
- You need Amazon orders in Elbuz: each arrives as a “Customer order” document.
- Prices and stock on Amazon should come from Elbuz: an export template sends them by seller SKU.
Where to start: enter the Marketplace ID and link the app with a code.
What the Amazon connection can do
- Connects without passwords: you link the app with a code, and the Seller is filled in automatically.
- Turns listings into product cards: name, description, price, quantity, active status, brand, category, photos and variant family.
- Imports orders as “Customer order” documents.
- Combines several marketplaces: each country has its own template, all feeding one catalog.
- Sends price and stock back and publishes new products.
- Updates by itself: orders every 5 minutes, the catalog on a schedule.
What you need from Amazon: app linking and Marketplace ID
Linking the app with a code
Amazon grants access only through an app, so the main way to connect is linking with a code: click “Connect”, sign in on Amazon and approve access, then enter the code you're shown into the “Link code” field and click “Link store”. Once linked, the Seller ID is filled in automatically.
The token field in the form is only needed for the test environment (sandbox) or unusual cases. With a normal connection, the token is issued and renewed automatically.
Marketplace ID is required
Each Amazon country is a separate marketplace with its own Marketplace ID. Elbuz uses it to pick the Amazon regional server (Europe, North America or Far East). Examples: Germany A1PA6795UKMFR9, Poland A1C3SOZRARQ6R3, USA ATVPDKIKX0DER. Look up your code in Seller Central help or your account settings.
| Country | Marketplace ID | Language of a new listing |
|---|---|---|
| Germany | A1PA6795UKMFR9 | German |
| France | A13V1IB3VIYZZH | French |
| Italy | APJ6JRA9NG5V4 | Italian |
| Spain | A1RKKUPIHCS9HS | Spanish |
| Netherlands | A1805IZSGTT6HS | Dutch |
| Belgium | AMEN7PMS3EDWL | French or Dutch |
| Poland | A1C3SOZRARQ6R3 | Polish |
| Sweden | A2NODRKZP88ZB9 | Swedish |
| Ireland | A28R8C7NBKEWEA | English |
| United Kingdom | A1F83G8C2ARO7P | English |
Turkey, the UAE, Saudi Arabia, Egypt, India and South Africa also run through the European server: Elbuz routes requests there by their Marketplace ID.
How to connect, step by step
- Create a template of type “Amazon” and enter the Marketplace ID first: it decides where “Connect” takes you, the Amazon sign-in for Europe or for North America (US, CA, MX, BR). “Active” and “Orders” are already on in a new template: within 5 minutes of linking, Elbuz starts pulling your entire order history. Elbuz maps marketplace statuses to yours by name; what arrived and how it was mapped is shown in the template's “Order statuses” window. Want to check first? Clear “Orders”.
- Click “Connect”, approve access, enter the code into “Link code” → “Link store”.
- Click “Test connection”.
- In the “Select data to import” card, turn on products, then save and run.
There is one link per Amazon account: if you linked it in the import template, the export template uses the same access, and vice versa.
What goes into the product card
| Amazon data | Source | Product card field in Elbuz |
|---|---|---|
seller-sku | report | SKU, the main key for all operations |
item-name | report | Name (if empty, the SKU is used) |
item-description | report | Full description |
price | report | Price |
quantity | report | Stock |
listing status active | report | Card's active status |
asin1 | report | Link key (ASIN) |
| brand | Amazon catalog | Manufacturer |
| classification (browse node) | Amazon catalog | Category, as a full path from the root |
| product images | Amazon catalog | Images, if the “Photo” checkbox is on |
| parent ASIN of a variation | Amazon catalog | Family (variant link) |
Not imported from Amazon: attributes (the report doesn't have them, so you fill them in your own catalog), old price and barcode. The seller SKU, ASIN and parent ASIN are stored in the card's link, and price and stock updates go back to Amazon by seller SKU.
Why the catalog is built in two steps
Amazon doesn't return the catalog in a single request. First, Elbuz requests a report on your listings and waits for Amazon to prepare it, which takes a few minutes for a large catalog.
The report has the SKU, name, description, price, quantity, ASIN and listing status. Then Elbuz fetches reference data by ASIN (brand, category, photos, variant links) in batches of 20 codes with a pause, because Amazon strictly limits request frequency.
- Request or action
- Reply
- loop — repeats
- Note
Variants and category
Amazon links variants by parent ASIN, and the child items are grouped into one family. No separate options are created: listing names already contain the color and size.
If the category can't be retrieved from the Amazon catalog, the product goes into the service category “Products - amazon”, which is disabled and excluded from exports. Move the product to your own branch: a repeat run doesn't change its place in the tree. More: service categories.
What a repeat run does to your edits
A repeat run looks for an existing card by the fingerprint “manufacturer part number + name + link to the card in the source”. The Amazon report only provides the name, so the card is matched by name: if it matches, the card is overwritten; if not, a new one is created.
- Start or end
- Action or result
- Decision: the path depends on the answer
- Overwritten from the report: name, description, price, quantity, active status, brand and “SKU”, without warning.
- Empty values don't erase yours: the report has no barcode, old price or tags, so values you entered by hand stay; a zero price isn't written to an existing card either. A quantity of 0 is written as is, with the “Out of stock” status.
- Left untouched: photos (added to new cards only), attributes, the place in the category tree.
- Markup rules apply only to newly created cards; an existing card keeps the amount Amazon returned.
To lock a whole card, use the “Do not update” switch (“Import protection” section): the Amazon run won't change it at all. “Fixed Price” protects only the price and old price. General rules: how to lock your own value.
1
Do not update2
Fixed Price- Do not update — closes the whole card from the Amazon import run.
- Fixed Price — the Amazon import run does not check this switch.
Two Amazon marketplaces in one catalog
Each marketplace gets its own template with its own Marketplace ID. What happens next depends on listing names:
- Same names: both templates find the same card, and it keeps the values from the run that finished last. Marketplaces have no priority.
- Localized names (usual on Amazon): these are different cards, and the templates don't interfere with each other.
A card has only one Amazon link: its row (seller SKU, ASIN, product type) is created by whichever template reached the card first. Updates back to Amazon go by that template's SKU. The only way to keep sources apart is the “Do not update” flag.
A listing disappeared or is no longer active
| What happened on Amazon | What happens to the card in Elbuz |
|---|---|
| The listing isn't in the report | The card keeps its last price and stock, nothing is disabled, and the log says nothing about it. The Amazon form has no “delete records missing from the source” checkbox, so remove such cards by hand, or they will go into exports |
| The listing is in the report but not active | The card loses “Active”; the product, photos, categories and link stay |
| Quantity 0 | Status “Out of stock” |
| The listing was renamed | The run creates a new card, and the old one keeps the old figures. Find duplicates in “Products” by filtering “Date added” for the day of the run |
General rule: a product disappeared from the source.
What clearing “Active” does
A disabled card stays in the catalog with all its data; what changes is export selection, since new templates take only active products. Turn it back on and everything is as before.
The active flag comes from Amazon on every run: if you clear “Active” by hand while the listing on Amazon is active, the next import sets it again. To make your decision stick, take the listing off sale on Amazon or set “Do not update” on the card.
How to import Amazon orders
Turn on “Orders” in the “Select data to import” card, and Elbuz polls Amazon and pulls them by itself every 5 minutes (schedule). Amazon doesn't share buyers' personal data: only the city, postal code and country come through from the address.
- Document: “Customer order”, not posted. Stock and reservations don't change until the document is posted.
- Number: the Amazon order number becomes the source number; importing again doesn't create a duplicate.
- Line items are matched to cards by seller SKU ().
- Statuses: Elbuz maps the order state to yours by name (
Unshippedto “Processing”,Shippedto “Shipped”), and the “Order statuses” button lets you fine-tune it. Payment method goes via “Payment statuses”, shipping level via “Delivery types” (the “Related settings” section). An unrecognized state comes in as “New”.
1
Order statuses2
Payment statuses3
Delivery Types4
Import orders from date- Order statuses — maps Amazon order statuses to Elbuz statuses.
- Payment statuses — maps Amazon payment statuses to Elbuz payment statuses.
- Delivery Types — maps Amazon shipping methods to Elbuz delivery types.
- Import orders from date — orders are loaded starting from this date (YYYY-MM-DD).
The first run pulls the entire history; after that, only what changed since the last import date. The date is in the “Advanced” section, in the “Import orders from date (YYYY-MM-DD)” field; leave it empty to pull everything from the start.
The contents of each order are requested separately. If a request fails, the run stops with the red line “Amazon: API error — …”, the orders on the current page aren't saved, and the date doesn't move, so the next run requests them again.
Card stock is driven by the catalog import: the quantity from the Amazon report overwrites stock regardless of posted documents. If you manage inventory in Elbuz, lock those cards with “Do not update”. General mechanics: importing orders.
How to update prices and stock on Amazon
The import fills the base catalog and stops there. Sending data back to Amazon is the job of a separate template of type “Amazon” in the “Data export” window, with its own schedule (export templates).
- Price and stock are sent, one request per SKU with a quarter-second pause (Amazon's limit). The log shows: “Amazon: prices and stock updated, items: 120 (errors: 0)”.
- It works only for cards linked to a listing, that is, cards that came from Amazon; the rest are skipped with the line “Amazon: items without an Amazon listing link skipped: N — to publish them, enable "Publish new products" in the export template”.
- A filled-in Seller ID is required, otherwise you get “Amazon: account is not connected — in this export template click “Connect”, …”.
FBA products: only the price is updated
The price is updated for all products, but stock only for those you ship yourself (FBM). Stock of products Amazon stores and ships (FBA) is managed by Amazon, and Elbuz doesn't touch it.
The log shows the line “Amazon: FBA items — price updated only, stock is managed by Amazon: N”. If the fulfillment channel can't be determined, Elbuz also updates only the price and reports it with the red line “Amazon: fulfillment channel could not be determined — price updated only: N”.
To list products that aren't on Amazon yet, turn on “Publish new products” in the export template. With an or UPC barcode, Elbuz publishes an offer on the existing Amazon product page; without a barcode it creates a new one, and then the product's category must have a mapped Amazon product type. The line “Amazon: new products not published” tells you what's missing.
What goes into a new product page
A new product page is created for a product without a barcode in a category mapped to an Amazon product type. Elbuz sends the name, brand, description, up to 5 bullet points from the first lines of the description, up to 9 photos and the condition “new”.
Texts go out in the marketplace language: Amazon.de gets German, Amazon.fr gets French (table). Elbuz takes the name and description in the language set in the export template's “Description language” field; without a translation, in the main language. In Belgium and Canada, “Description language” picks which of the marketplace's two languages the listing uses.
Product type and attributes are mapped separately for each marketplace: in the category mapping window, on the Amazon tab, choose the marketplace, map the product type, and in the “Amazon attribute” column map the type's required attributes to your attributes.
A listing missing a required attribute isn't sent; the log shows “Amazon: "‹name›" (type ‹code›) — required attributes are empty: ‹list›”. Attributes with units (weight, dimensions) aren't filled by mapping: Amazon lists them in its response, and they go to the log. “Publish readiness” in the mapping window shows unmapped fields in advance. Elbuz takes the country of origin from an attribute, as an ISO code.
- Start or end
- Action or result
- Decision: the path depends on the answer
Scheduled updates
Elbuz pulls orders by itself every 5 minutes if “Orders” is selected in the template and access is granted. This is done by the shared “Marketplace orders” task in the “Job schedule” window, where you can also change the interval. This pass doesn't load the catalog, and orders also picked up by the template's schedule aren't duplicated.
The catalog is updated by the template's own schedule: the “Schedule setup” button. The catalog is prepared as a report, so run it rarely, at night for example: while the catalog is loading, the orders pass is skipped until the next one.
At the end of a run, Elbuz applies markup to new products and recalculates formulas; the last log line is “Data import completed!”. How to read the log: how to check that the import went through.
Scenarios
Build one marketplace's catalog and keep it fresh
What to turn on. A template of type “Amazon” with the “Marketplace ID” of your country; in “Select data to import”, “Products” and “Photo”; a schedule via “Schedule setup”.
What you get. Each report row becomes a card with name, description, price, quantity and SKU, and the Amazon catalog adds brand, category, photos and variant family. Only new cards get photos; remove listings taken down on Amazon by hand.
You manage inventory in Elbuz, Amazon only sells
What to turn on. On the cards, “Do not update” in the “Import protection” section; separately, an export template of type “Amazon” with the Seller ID and Marketplace ID.
What you get. The catalog run doesn't change these cards, and the export sends price and stock from Elbuz to Amazon. The export doesn't touch the listing's name, description or photos.
You only need orders and manage the catalog another way
What to turn on. Only “Orders”, with “Products” off; if needed, a date in the “Import orders from date (YYYY-MM-DD)” field. No template schedule is needed: orders arrive by themselves every 5 minutes.
What you get. The run doesn't touch the catalog, and each order arrives as a “Customer order” document with line items matched by seller SKU. There will be no buyer street address or phone number, because Amazon doesn't share them.
List products on Amazon that aren't there yet
What to turn on. In the export template, “Publish new products”; on the cards, an EAN or UPC, and for products without a barcode, a mapped Amazon product type in the category.
What you get. A product with a barcode becomes an offer on an existing Amazon product page; without a barcode, a new product page with name, description, brand, bullet points from the first lines of the description, and photos. Once accepted, the product gets a link, and from then on its price and stock update with the regular export. Required attributes Amazon didn't receive show up as a red line in the log.
What to do when Amazon won't import
| What you see | Why | What to do |
|---|---|---|
| “Amazon: account is not connected or Marketplace ID is missing — fill in the Marketplace ID, click “Connect”, approve access on Amazon and enter the code shown into “Link code” → “Link store”” | No access from app linking, or the Marketplace ID field is empty | Link with a code and fill in the Marketplace ID (about the field) |
| “Amazon: catalog imported, products: 0” | The report came back empty: you have no listings on this marketplace. Most often, the Marketplace ID is for the wrong country | Check the Marketplace ID; the catalog hasn't changed (wrong Marketplace ID) |
| “Amazon: API error — report timeout” | Amazon didn't prepare the report within 60 checks | Run it again; nothing in the catalog has changed (about breaks) |
| “Amazon: API error — HTTP 429: retry limit reached” | You hit Amazon's request limit: three retries in a row were also refused | In the orders pass, increase the interval of the “Marketplace orders” task; for the catalog, run it less often and not in parallel with another Amazon template |
| “Amazon: items without an Amazon listing link skipped: 12 — …” | This is an export line: these products have no listing link because they didn't come from Amazon | Import the catalog through this connection first, since the import sets the link; products not on Amazon get listed by the “Publish new products” checkbox (export to Amazon) |
If a run breaks off
The order of work: request the report, wait, download it, fetch data by ASIN, and only then write to the catalog in batches of 500. Nothing is written to the catalog until the ASIN fetch is done: a break in the early stages, including a failed ASIN batch, leaves the catalog unchanged. A break during writing leaves the written batches updated. General rules: if a run breaks off.
- Start or end
- Action or result
- Decision: the path depends on the answer
Repeating is safe and creates no duplicates, but the report is requested again: there's no resuming from the break point.
- Report readiness is checked up to 60 times, with the pause growing to 15 seconds; after that, “Amazon: API error — report timeout”.
- Elbuz waits up to 120 seconds for a single Amazon response and downloads the report file with a 300-second limit.
- On HTTP 429, the request is retried up to three times with pauses of 3, 6 and 9 seconds.
The stop button in the Operations center works between ASIN fetch batches, and then nothing is written to the catalog. Once writing to the catalog has started, stopping doesn't interrupt it: the report is processed to the end. Look for the effects by “Date updated” in the “Products” window.
If you entered the wrong Marketplace ID
European codes go to the European server, Far East codes to the Far East server, and any other code (including a mistyped one) to the North American server. “Test connection” replies “Connection works. Amazon”, but it doesn't verify the Marketplace ID itself: it will accept a German code instead of a Polish one.
- A code from another region: the red line “Amazon: API error — …”, the catalog is unchanged.
- A code for a marketplace where you don't sell: “Amazon: catalog imported, products: 0”, the catalog is unchanged.
- A code for a neighboring marketplace where you do sell: the other country's catalog arrives and overwrites your cards wherever names match.
For the third case, search “Products” by “Date updated” for the day of the run; new cards, by “Source - name” and in the “Products - amazon” category. There's no bulk rollback; only the price is kept separately, if price history is on. More: if you imported the wrong data.
FAQ
Where do I get an Amazon access token?
You don't need to enter one: access is granted by linking the app with a code, and the Seller ID is filled in automatically. The token field is only for the test environment (linking).
Why does the first import take a few minutes?
Amazon first prepares a report with all your listings, and then Elbuz fetches the details by ASIN. That's normal, not a freeze (two steps).
I sell on Amazon in several countries. What should I do?
Create a separate template for each marketplace with its own Marketplace ID, and the products will come together in one catalog (two marketplaces).
Do orders come with buyer details?
No. Amazon doesn't share personal data: you get the order contents, and from the address only the city, postal code and country.
Will a repeat run overwrite my edits in the card?
Yes: it overwrites the name, description, price, quantity and active status. It doesn't touch the barcode, old price, tags, photos, attributes or category. To lock a card, use “Do not update” (repeat run).
Can I keep my own price on some Amazon products?
Yes: turn on “Fixed Price” in the card (“Import protection” section). The run won't change the price and old price, and other fields update as usual (repeat run).
Where to find it and who has access
- Menu
- Directories → Operations → Data import
- Template
- new template → type “Amazon”; one template = one account and one marketplace
- Access right
- the “Import” window in “Group permissions”
- Have ready
- your Seller Central sign-in and the Marketplace ID of your marketplace
1
Seller ID2
Marketplace ID- Seller ID — filled in automatically when the Elbuz app is linked to the seller account.
- Marketplace ID — the Amazon marketplace the catalog is imported from.
How import templates work in general: data import overview.
Related topics
- To understand how an import template handles any source, see Importing data into the catalog.
- If you're connecting other marketplaces via API too, see Catalog import via API.
- If prices and stock from Elbuz should go to Amazon, see Export templates.
- If the catalog is imported and you need to set up prices and stock, see where to start and where to go next.
