Amazon Data Takeover
This page guides you through taking over an Amazon channel that you have run with another system so far. Eight steps bring marketplaces, listings, open orders, prices and stock, the FBA opening stock, the order history, and images and product data into Business Central. Until you release a marketplace, Business Central sends neither prices nor stock for it – your previous system stays in charge until then.
You do not need this page for a channel that you start fresh with Business Central.
Opening the Page
- Via search: Amazon Data Takeover; also via the search terms Amazon takeover, cut-over date, existing Amazon listings, migration, open Amazon orders, FBA opening stock, Amazon order history, Amazon images and product data
- Via the Amazon Administration → Data Takeover (menu Related and group Listings)
- Via the hub cockpit Data Takeover: every Amazon line opens this page with Open.
- From the messages Prices and stock are not released yet and The marketplace cannot be released yet → Open Data Takeover
You open the step pages (marketplaces and cut-over dates, listings, Assign SKUs, Review and Release) from here; their help is further down on this page.
Workflow
Work through the steps per marketplace in this order. The open orders come before the release: only once they are in Business Central does the inventory formula count their quantities as sold – and the release sends these quantities to Amazon. The order history and the images and product data can follow at any time.
| No. | Step | Prerequisite | What it does | Where it runs |
|---|---|---|---|---|
| 1 | Marketplaces and Cut-over Date | – | Set and apply the cut-over date per marketplace. | on its page |
| 2 | Take Over Listings | Step 1 | Reads every listing with product type, prices and quantity from Amazon and assigns it to your item. Changes nothing at Amazon. | Run |
| 3 | Assign SKUs | Step 2 | Assign or ignore SKUs without an item. No item is created. | on its page |
| 4 | Take Over Open Orders | Steps 1 to 3 and the cut-over date reached | Brings over every open order that you ship yourself as a running order with a sales order. | Run |
| 5 | Review and Release | Steps 1 to 4 | Compare prices and quantities, create a price list draft if needed, release the marketplace. | on its page |
| 6 | FBA Opening Stock | FBA set up, step 2 | Proposes Amazon's FBA stock as opening stock in the FBA adjustment journal. | via Open |
| 7 | Order History | Step 1 and the cut-over date reached | Takes over the orders of the months before the cut-over date for sales figures and item history, without documents and without buyer data. | Run |
| 8 | Images and Product Data | Step 3 | Takes over the images of your own listings and fills empty product data of the Amazon items. | Run |
Step 6 applies to the seller account as a whole, all other steps per marketplace.
Fields
At the top of the page:
| Field | Description |
|---|---|
| Marketplace | Marketplace whose steps the page shows. Blank shows all marketplaces of the takeover combined: a step is then done when it is done on all of them. Run and Run in Background apply to the marketplace chosen here or, if the field is blank, to all marketplaces of the takeover. |
| Takeover | The marketplaces of the takeover, e.g. 3 marketplaces with a cut-over date. These are the marketplaces with a cut-over date; as long as none has one, all marketplaces you take part in. |
| Order History (Months) | How many months of order history step 7 reads back from the cut-over date, 1 to 24 (default 24). A shorter period is taken over faster; you can read a longer one later, the takeover goes on where it stopped. The setting applies to the seller account. |
One line per step:
| Field | Description |
|---|---|
| No. | Number of the step. Work through the steps in this order. |
| Step | Name of the step. Choosing it opens the step like Open. |
| Status | Where the step stands, highlighted in color (see below). Across all marketplaces e.g. 2 of 3 marketplaces. |
| Result | What the last run did or what is still open, e.g. 120 listings: 112 assigned, 6 open, 2 ignored or 18 of 24 months taken over. Across several marketplaces the field stays blank; choose a marketplace at the top to see its result. |
| Last Run | When the step last ran through. Across all marketplaces the oldest last run, and only if the step is done on all of them. |
| Last Run By | User who last ran the step (hidden by default). |
| Description | What the step does. |
| Prerequisite | What has to be done before the step, e.g. Steps 1 to 3 and the cut-over date reached. |
Status of the Steps
| Status | Meaning |
|---|---|
| Not Started (grey) | The step has not run yet. Result says what it is waiting for, e.g. From 11/01/2026, the cut-over date or Needs a cut-over date (step 1). |
| In Progress (yellow) | The step has started but is not finished – e.g. 5 SKUs open, Proposed - check and post the FBA adjustment journal or x of y months taken over. Across all marketplaces, this reads x of y marketplaces. |
| Done (green) | The step is done – across all marketplaces only once it is done on each of them. |
| Outdated (yellow) | The step has to run again, e.g. because the cut-over date was changed (Cut-over date changed to … - apply it again), because SKUs were left without product type and prices, or because open orders could not be taken over. |
| Failed (red) | The last run stopped with an error; Result shows the message. An earlier successful run stays in Last Run. |
| Not Applicable (grey) | Step 6 only: The account does not use FBA. |
If even one marketplace is Failed or Outdated, the combined line shows this status.
Actions
| Action | Description |
|---|---|
| Open | Opens the selected step: the marketplaces and cut-over dates, the listings, the SKUs to assign, the Amazon Orders, the comparison with the release, the FBA opening stock, the orders of the history, or the assigned listings with their product data – each for the marketplace at the top, otherwise for all marketplaces of the takeover. |
| Run | Runs the selected step right away after a confirmation (Run the step … for … now?), for the marketplace at the top or for all marketplaces of the takeover. Only for steps 2, 4, 7 and 8; the other steps work on their pages. Each marketplace runs on its own: if one fails, the others keep their result. The message gives the result per marketplace. |
| Run in Background | Starts the selected step as a one-time job in the job queue (Amazon data takeover: <step>) – for a large catalog and for the order history, which takes about one minute per month. The result appears on this page once the run is done (Refresh). If the run stops, for example at Amazon's request limit, start it again. Without the permission to schedule background jobs, run the step with Run. |
| Refresh | Reads the state of the steps again. |
| Marketplaces and Cut-over Dates | Opens the marketplaces of the takeover with their cut-over dates. |
| Taken-over Listings | Opens every SKU that the takeover found at Amazon, with what became of it (see Listings Taken Over). |
| Data Takeover of All Channels | Opens the hub cockpit Data Takeover with the takeover steps of all sales channels in merchantCENTRAL. |
Data Takeover hub cockpit
The cockpit shows the eight Amazon steps with their status across all marketplaces of the takeover. Open leads here; Run starts steps 2, 4, 7 and 8 for all marketplaces of the takeover, the other steps open this page. Users without permissions for the Amazon connector see no Amazon lines there.
Marketplaces and Cut-over Dates
Step 1. The page Amazon Takeover - Marketplaces and Cut-over Dates shows the marketplaces you take part in. Here you set from which day Business Central runs your Amazon business on a marketplace, and you apply the cut-over date. One shared cut-over date for several marketplaces is just as possible as a separate one per marketplace.
| Field | Description |
|---|---|
| Marketplace Code | Short code of the marketplace, e.g. DE. |
| Marketplace Name | Name of the Amazon marketplace. |
| Cut-over Date | Date from which Business Central runs your Amazon business on this marketplace. Orders placed before it stay in your previous system, except open orders that you ship yourself; so do returns for orders that are not in Business Central, and settlements that start before the cut-over date. Leave it blank for a marketplace that you start fresh with Business Central. Can be changed directly in the line. |
| Status | Whether the cut-over date is applied and the sales channel is enabled: No cut-over date yet, Cut-over date 11/01/2026 (green when applied), Cut-over date changed to … - apply it again or The sales channel is not enabled - apply the cut-over date again (both red). |
| Cut-over Applied | Cut-over date to which the start dates of order import, returns, invoice upload and settlements were set. If it differs from the Cut-over Date, apply the date again. |
| Sales Channel Enabled | Whether the sales channel of the marketplace is enabled in merchantCENTRAL. Order import and the price and stock sync run only for enabled sales channels; applying the cut-over date enables it. |
| Use for Orders | Whether the orders of this marketplace are imported. |
| Use for Listings | Whether you list on this marketplace from Business Central. |
| Use for Inventory | Whether Business Central sends the stock of this marketplace – after the release. |
| Use for Pricing | Whether Business Central sends the prices of this marketplace – after the release. |
| Prices and Stock Released At | When you released the marketplace (step 5). Before that, Business Central sends neither prices nor stock for a marketplace with a cut-over date. |
| Country Code | Country of the marketplace (hidden by default). |
The four Use for … switches work as on the Amazon Marketplace Participations page.
| Action | Description |
|---|---|
| Set Cut-over Date | Opens the Set Cut-over Date dialog and sets the date for all selected marketplaces. Afterwards, change the date of a single marketplace in its line if it switches later. |
| Apply Cut-over Date | After a confirmation, applies the cut-over date of the selected marketplaces (see What Applying Does). Does not start an import. Selected marketplaces without a cut-over date are skipped; if none has one, you get the message Set the cut-over date of the selected marketplaces first. |
| Release Marketplace | Releases the selected marketplace without the comparison from step 5 – with the same prerequisites and the same confirmation as there (see Release). |
| Fetch from Amazon | Reads the marketplaces you take part in from Amazon again. |
| Sales Channel | Opens the Marketplace Sub-Account of the marketplace in merchantCENTRAL with its price lists and its language. |
Set Cut-over Date
The dialog asks for the date that Set Cut-over Date writes to all selected marketplaces.
| Field | Description |
|---|---|
| Cut-over Date | Date from which Business Central runs your Amazon business on the selected marketplaces. Orders placed before it stay in your previous system, except open orders that you ship yourself. Required. |
You cannot change a cut-over date in every state:
- After the release no longer – revoke the release first (Revoke Release in Review and Release).
- After applying it can no longer be cleared: clearing does not undo a takeover. Another date is possible; apply it again afterwards.
- Before the order history already taken over (step 7) it cannot be set: the orders of those days would otherwise be left without documents. The message names the earliest possible date.
What Applying Does
- The sales channel of the marketplace is enabled; if it is missing in the hub, it is created.
- The order import starts on the cut-over date (start of the day). Before the cut-over date it imports nothing for this marketplace and says so. From then on it takes over all orders placed since the cut-over date; older ones only if they are open and you ship them yourself.
- Returns – with FBA also FBA returns, FBA reimbursements and the other FBA reports – are read from the cut-over date. Returns for orders that are not in Business Central are skipped; your previous system handles them.
- Upload Invoices From is set to the cut-over date (see Amazon Marketplace Participation).
- Settlements are imported if they start on the cut-over date or later (add-on module, see Settlements).
Applied again with the same date, the action only enables the sales channel and resets no import.
Take Over Listings
Step 2, with Run or Run in Background. For each marketplace of the takeover:
- Amazon creates the report of all listings. If it is not ready after five minutes, the next run picks it up; the step discards a failed or unreadable report, and the next run requests a new one.
- Every SKU of the report goes onto the list of listings taken over, with ASIN, bar code, fulfillment channel, status, title, price and quantity.
- For each listing the step reads the details from Amazon: product type (price and quantity changes need it), consumer and business price, quantity, discoverability and buyability. If Amazon throttles the requests, the next run goes on with the SKUs this one did not reach; the result names them (… without product type and prices - run the step again), and the status is Outdated until then.
- Every SKU whose item is found is assigned – via an existing listing with this SKU, the item number or a bar code. If the bar code belongs to a unit of measure other than the base unit, the SKU becomes the pack offer of the item. For the rest, the step looks for a suggestion for Assign SKUs.
A newly assigned listing gets its status from the details: a listing that buyers can find is active, even if it is sold out (Amazon's report calls it Inactive). A listing that Business Central already syncs keeps its status. Another run updates the list: SKUs that are no longer in the report drop out of the views; assignments and decisions stay. The step creates no items and changes nothing at Amazon.
The Result reads e.g. 120 listings: 112 assigned, 6 open, 2 ignored.
Listings Taken Over
The page Amazon Takeover - Listings (Open on step 2 or Taken-over Listings) shows every SKU that the takeover found in the listings report, and what became of it. It is read-only.
| Field | Description |
|---|---|
| Marketplace Code | Marketplace on which the SKU is listed. |
| SKU | SKU of the listing at Amazon. |
| State | What became of the SKU: Open, Assigned, Pack Assigned, Item Has Another SKU or Ignored (see Assign SKUs). |
| Item No. | Item to which the SKU is assigned. |
| Variant Code | Variant of the item (hidden by default). |
| Unit of Measure Code | Unit of measure of a pack listing, i.e. a multipack of the item (hidden by default). |
| Matched By | How the SKU found its item: Existing Listing, Item No. or Bar Code (step 2), Common Item No. or Vendor Item No. (accepted suggestion) or Manual (Assign Item). |
| Title | Title of the listing at Amazon. |
| ASIN | Amazon product that the listing offers. |
| Product ID | Bar code (EAN, UPC or ISBN) with which the listing was created (hidden by default). |
| Product Type | Amazon's product type of the listing. Price and quantity changes need it. |
| Fulfillment Channel | Whether you ship the orders of the listing (MFN) or Amazon does (FBA). |
| Amazon Status | Status of the listing in Amazon's listings report: Active, Inactive or Incomplete. |
| Buyable | Whether buyers can buy the listing right now (hidden by default). |
| Amazon Price | Consumer price at Amazon when the takeover read the listing – in Europe including VAT. |
| Amazon Business Price | Price for business customers at Amazon; 0 without a business offer. |
| Currency Code | Currency of the Amazon prices, as Amazon gives it (hidden by default). |
| Amazon Quantity | Quantity that Amazon offered. Amazon keeps it only for listings that you ship yourself (MFN). |
| In Listings Report | Whether the listing was in the report at the last run (hidden by default). |
| Details Read At | When the takeover last read product type, prices and quantity (hidden by default). |
| Product Data Read At | When step 8 read the images and product data of the listing (hidden by default). |
| Assigned At | When the SKU was assigned to its item (hidden by default). |
| Action | Description |
|---|---|
| Assign SKUs | Opens the SKUs that are still waiting for an item. |
| Review and Release | Opens the comparison of prices and quantities with the release. |
Assign SKUs
Step 3. The page Amazon Takeover - Assign SKUs shows the SKUs for which step 2 found no item, and the SKUs whose item is already listed on the marketplace under another SKU. For each one you decide: accept the suggestion, assign an item, or ignore it. No item is created. The step is done as soon as no SKU is open any more.
| Field | Description |
|---|---|
| Marketplace Code | Marketplace on which the SKU is listed. |
| SKU | SKU of the listing at Amazon. |
| State | Open (red), Item Has Another SKU (yellow), Assigned or Pack Assigned (green), Ignored (grey). |
| Title | Title of the listing at Amazon. |
| Suggested Item No. | Item that the SKU might belong to (highlighted in green). |
| Suggested By | How the suggestion came about: Common Item No., Vendor Item No. or Bar Code (a pack whose single item is not listed yet). |
| Item No. | Item to which the SKU is assigned. |
| Variant Code | Variant to which the SKU is assigned. |
| Other SKU | SKU under which the item is already listed on this marketplace. A marketplace takes one SKU per item and variant. |
| ASIN | Amazon product that the listing offers. |
| Product ID | Bar code with which the listing was created. |
| Fulfillment Channel | MFN or FBA. |
| Amazon Status | Status in the listings report. |
| Amazon Price | Consumer price at Amazon. |
| Amazon Quantity | Quantity at Amazon (MFN only). |
| Product Type | Amazon's product type (hidden by default). |
SKU Status
| Status | Meaning |
|---|---|
| Open | No item yet. A suggestion appears in Suggested Item No. if the Common Item No. or the Vendor Item No. matches exactly one item; two matches give no suggestion. |
| Item Has Another SKU | The item is already listed on this marketplace under the SKU in Other SKU. Ignore the SKU or assign it to another item or another variant. |
| Assigned | The SKU has become an Amazon item. |
| Pack Assigned | The SKU is the pack offer of an item: its bar code belongs to a unit of measure other than the base unit. A pack is only assigned once the single item is listed on the marketplace – until then the SKU stays open, with the item as the suggestion. Then assign the SKU of the single item first and run step 2 again. |
| Ignored | You leave the SKU to Amazon: Business Central sends neither price nor stock. Orders with this SKU are put on hold as orders with an unknown SKU. |
| Action | Description |
|---|---|
| Accept Suggestion | Assigns the selected SKUs to their suggested items. With several lines after a confirmation; the message names the assigned SKUs and those that stayed open (already assigned, or item listed on the marketplace under another SKU). |
| Assign Item | Assigns the selected SKU to an item that you choose from the item list (the suggestion is preselected) and – if it has variants – to one of its variants. |
| Ignore | Ignores the selected SKUs, with several lines after a confirmation. |
| Reopen | Puts the selected ignored SKUs and those with Item Has Another SKU back on the list of open SKUs. |
| Item | Opens the item card of the assigned item or, if none is assigned yet, of the suggested item. |
A SKU that you assign after the marketplace is released goes to Amazon with its price and quantity at the next sync.
Take Over Open Orders
Step 4, with Run or Run in Background – from the cut-over date and only once it is applied. Before that, your previous system still ships the orders.
The step brings over every open order that you ship yourself (MFN, not shipped yet or only partially shipped), regardless of its age – the regular order import starts only on the cut-over date and would never see older orders. Amazon keeps orders up to two years back. As with the order import, each order becomes a running order with a sales order, in its own transaction:
- A partially shipped order comes with the remaining quantity, the shipping costs pro rata. If Amazon does not report how many units are already shipped, it is not imported, so that nothing is shipped twice.
- An order with an unknown SKU is put on hold (see Amazon Orders).
- An order that fails is listed in the Amazon Order Import Errors and does not hold up the others.
- Orders that Amazon ships (FBA) and orders already shipped stay in the previous system.
Across all marketplaces, the step runs only for the marketplaces whose cut-over date is applied and has begun; marketplaces with a later cut-over date do not count as failed. The Result reads e.g. 40 orders taken over, 3 in Business Central already, 1 on hold, 0 failed. With failed orders the step is Outdated, and the marketplace cannot be released. Open shows the Amazon Orders.
Review and Release
Step 5. The page Amazon Takeover - Review and Release compares, per assigned SKU and per pack, the prices and quantities of Business Central with those of Amazon – what the sync sends after the release. If the comparison fits, you release the marketplace.
| Field | Description |
|---|---|
| Marketplace Code | Marketplace of the SKU. |
| SKU | SKU of the listing. |
| Item No. | Assigned item. |
| Variant Code | Variant (hidden by default). |
| Title | Title of the listing at Amazon. |
| Fulfillment Channel | MFN or FBA. |
| Amazon Price | Consumer price at Amazon when the takeover read the listing. |
| Business Central Price | Consumer price that Business Central sends after the release, the way Amazon shows prices – in Europe including VAT. 0 if the item has no price in the price list of the sales channel. Highlighted in red if it differs from the Amazon price. |
| Price Difference % | Difference of the Business Central price from the Amazon price, as a percentage of the Amazon price. |
| Amazon Business Price | Price for business customers at Amazon. |
| Business Central Business Price | Business price that Business Central sends after the release; 0 without a business price. |
| Amazon Quantity | Quantity at Amazon (MFN only). |
| Business Central Quantity | Quantity that Business Central sends after the release, according to the inventory formula of the sales channel – including 0. Highlighted in red if, for an MFN listing, it differs from the Amazon quantity. Amazon keeps the quantity of an FBA listing itself. |
| Price Note | Why the item has no Business Central price, e.g. because no price list is assigned to the sales channel. |
| Product Type | Amazon's product type; red if it is missing – then run step 2 again. |
| Amazon Status | Status in the listings report (hidden by default). |
| Action | Description |
|---|---|
| Release Marketplace | Releases the marketplace of the selected line (see Release). |
| Revoke Release | After a confirmation, revokes the release of the marketplace of the selected line: Business Central sends neither prices nor stock for it until you release it again. What has already been sent stays at Amazon. Only after that can the cut-over date be changed again. |
| Refresh Business Central Prices | Reads the prices of the marketplace of the selected line again from the price lists of its sales channel, including those of the packs – for example after you have changed or assigned a price list. |
| Create Price List Draft | Creates a sales price list AMZ-<Marketplace>-B2C as a draft with the Amazon consumer prices of the marketplace of the selected line, including VAT, one line per assigned SKU. Afterwards the action asks whether to open the price list. |
| Create Business Price List Draft | As above with the Amazon business prices, as AMZ-<Marketplace>-B2B. |
Price list draft
The draft helps if your Amazon prices were maintained only in Seller Central so far. It applies to the customer price group AMZ-<Marketplace> (prices including VAT), which is created with the first draft – not to all customers, so that once activated it does not price the other sales in Business Central. Business Central never writes into a price list that is in use: review and activate the draft and assign it to the sales channel yourself, the business draft as its business price list (see Marketplace Setup). If the takeover has no Amazon prices of the marketplace, run step 2 first.
Release
For a marketplace with a cut-over date, Business Central sends neither prices nor stock until it is released and its cut-over date has begun. This applies to the price and stock sync, the offer sync and the listing of offers; started manually, these actions report Prices and stock are not released yet with Open Data Takeover.
You can release a marketplace only once
- its cut-over date is applied (and has not been changed since),
- the cut-over date has begun – until then your previous system sends prices and stock,
- Take Over Open Orders has run since the cut-over date without any order failing. Import failed orders again from the Amazon Order Import Errors or run step 4 again.
Otherwise the action reports The marketplace cannot be released yet with the reason.
The confirmation tells you what happens: from the next sync, Business Central sends the price and quantity of every assigned SKU once – even a quantity of 0, because the Amazon values from step 2 can be days old – and withdraws the business offers of items without a business price in Business Central. A price that is far off the Amazon price waits in the price check for your approval; packs do not go through the price check, the comparison shows their prices. If SKUs are still open or open orders are on hold because of an unknown SKU, the confirmation gives their number: Business Central sends nothing for open SKUs, and the items of orders on hold count as available stock until the orders become sales orders.
After that, step 5 is Done (Released on …), and the message gives the number of released SKUs.
FBA Opening Stock
Step 6, only if Enable FBA is turned on in the Amazon Settings; otherwise Not Applicable. The step applies to the seller account as a whole. It posts the stock that Amazon stores for you once as opening stock to the FBA location.
Open on step 6 asks whether Amazon's FBA stock should be read and proposed as opening stock in the FBA adjustment journal. The suggestion first reads Amazon's FBA stock – with the European fulfillment network (Pan-EU), the shared stock of the marketplaces counts once – and then writes the difference to the FBA location into the item journal from FBA Adjustment Journal Template and FBA Adjustment Journal Batch; on a location without stock, this is Amazon's entire stock, valued at the unit cost of the items. It is the same suggestion as Suggest FBA Adjustments in the Amazon Items list; the message names the suggested lines and the skipped items. Then the journal opens. Nothing is posted: review and post it yourself. If the suggestion is already in the journal, Open opens it without asking.
| Status | Meaning |
|---|---|
| In Progress | Proposed - check and post the FBA adjustment journal. |
| Done | There is a positive adjustment on the FBA location (Opening stock posted on the FBA location), or the suggestion had nothing to suggest and skipped no item. |
| Outdated | The suggestion skipped items, or it has disappeared from the journal without being posted – propose the opening stock again. |
Order History
Step 7, with Run or Run in Background – from the cut-over date and only once it is applied. The step takes over the orders of the months before the cut-over date into the hub's Marketplace Orders, for sales figures and the history of items and marketplaces. How many months is set by Order History (Months) at the top of the page (at most 24; Amazon keeps orders two years back).
- What is taken over: only orders that Amazon has finished, with status Shipped or Cancelled, with date, amounts, currency, ship-to country and whether Amazon shipped; one line per position (item via the SKU as in the order import, quantity, price, tax) as well as lines for promotion discounts, gift wrap and shipping.
- What is not taken over: no documents – the orders never become sales orders – and no buyer data: no name, no address, no postcode, no city, no purchase order number of the buyer. Buyer Data Anonymized On is set right away.
- Which orders: only orders placed before the start of the cut-over date; orders of the cut-over date itself are left to the order import. Orders the hub already knows stay unchanged. Orders of other marketplaces and orders that Amazon ships for other sales channels (Multi-Channel) are left out. The step recognizes the marketplace by the Domain Name of the marketplace participation; if it is missing, run Get Marketplace Participations in the Amazon Administration.
- Orders not finished yet (e.g. FBA orders shortly before the cut-over date) are read again by a later run; until then the result shows Orders from … on were not finished at Amazon yet - run the step again in a few days. Orders that Amazon has still not finished 60 days after they were placed (e.g. never paid) stay out for good; the result gives their number.
The step reads Amazon's report of all orders in periods of 30 days backwards from the cut-over date; each period is saved on its own. After the first reports, Amazon creates about one per minute, so 24 months take around half an hour per marketplace – use Run in Background. If the run stops at the request limit or a report is not ready after five minutes, the next run goes on from there or picks up the report; the result says so (Amazon's request limit is reached - …, Amazon is still creating a report - …).
Per marketplace, the step runs only once at a time. If it is already running – in the background or for another user – a second run reports when the running one last saved its progress; a run that has not saved anything for 20 minutes counts as stopped.
| Status | Meaning |
|---|---|
| Not Started | No run yet; Result says what the step is waiting for (Needs a cut-over date (step 1) or From …, the cut-over date). |
| In Progress | x of y months taken over: y is the number of months set, fewer where Amazon delivers no older orders. Followed, if applicable, by the note on unfinished orders or a pending report. |
| Done | The history goes back as far as set, and no order is waiting for Amazon to finish it any more. |
| Outdated | The cut-over date was moved: Cut-over date moved to … - run the step again for the days up to it (or … changed to … - apply it again, as long as it is not applied). |
| Failed | The run stopped; Result shows the message. |
Open on step 7 shows the orders of the history in the Marketplace Orders: Amazon orders without a sales order, Shipped or Cancelled, without buyer data – for a chosen marketplace, those before its cut-over date.
Migrate Historical Orders in the hub
Migrate Historical Orders on the hub card Marketplace Setup of the AMAZON marketplace runs this step for all marketplaces whose cut-over date is applied and has begun. The hub reports the number of orders taken over; an Amazon message per marketplace appears only if a marketplace has stopped or failed. Without such a marketplace, the action ends with an error message.
Images and Product Data
Step 8, with Run or Run in Background. For every assigned SKU that it has not read yet, the step reads your own listing at Amazon. Packs are left out. Nothing is changed at Amazon.
- Images: the main image and up to eight more images of your own listing go into the item gallery – never images from the Amazon catalog, because they can belong to third parties. An image that is already on the item as a file (such as a supplier's manufacturer photo) is confirmed for Amazon instead of copied. If Business Central has not sent any image of the item to the Amazon channel yet, the channel takes over the gallery once: what was on the item before is excluded for Amazon, and the images of the listing are confirmed for Amazon in its order and with its main image as the cover image. An arrangement already made in Business Central stays. Listings of variants deliver no images.
- Product data: Brand, Manufacturer, manufacturer part number, Length, Width, Height (cm), Net Weight and Gross Weight (kg) on the Amazon item – only into empty fields. The source is your own listing, for anything missing the Amazon catalog. Title, bullet points and description are not taken over.
Each SKU is read only once: an image that you later delete on the item does not come back; SKUs that you assign later are read by the next run. If Amazon throttles the requests, the next run goes on with the remaining SKUs. Like step 7, the step runs only once at a time per marketplace.
The Result reads e.g. 112 listings read: 340 images added, product data filled in for 98, followed if applicable by images that a full gallery could not take, SKUs not read with Amazon's status code (run the step again; status Outdated), and listings without catalog data. As long as assigned SKUs are not read, the step is In Progress (x SKUs not read yet). Open shows the listings taken over with state Assigned; show Product Data Read At to see which ones have been read.
Tips
Order on the cut-over date
Before the cut-over date: steps 1 to 3 (apply the cut-over date, take over listings, assign SKUs), a price list draft if needed. On the cut-over date, as soon as your previous system no longer ships anything: step 4, then release in step 5, then step 6. You can run steps 7 and 8 at any time after that.
Import Existing Listings
Import Existing Listings in the Amazon Items list runs step 2 – even without a takeover. It then applies to the marketplaces with Use for Listings, otherwise to the home marketplace. SKUs without an item wait in Assign SKUs; quantity and price of newly assigned listings go to Amazon once at the next sync.
Images of single items
Download Amazon Images on the Amazon Item Card and in the Amazon Items list, as well as Download Images in the image FactBoxes, fetch the same images of your own listing, with the same rules as step 8.
Cut-over date and release
As long as a marketplace is not released, Business Central sends neither prices nor stock for it – not even when the jobs are running. Do not forget the release as soon as your previous system is switched off; otherwise prices and quantities at Amazon stay at the old state.