Background knowledge:
In order for our system to communicate with Amazon via the interface, a valid token must exist.
This token, which must be activated per seller account, allows us to synchronise data through our developer access.
In other words: if the token is not valid/expired or even does not exist at all (in the case of a new plentymarkets system and/or new Amazon account), we cannot synchronise any data with Amazon for you. This means we cannot exchange product data, stock, prices, orders, invoices, etc. with Amazon.
How do I find out if my token has expired?
There is currently no explicit check for this. This check will be available with the new Amazon basic settings UI.
However, if you click on Setup » Markets » Amazon » Reports » Processing in the menu and then click Search for the respective account, and no new reports of any report types have been displayed for a long period, it is likely that the token has expired, meaning no data is being synchronised between Amazon and us in either direction.
So how do you update your token?
Correct procedure?
Go to the menu Setup » Markets » Amazon » Settings for the Amazon account for which you want to update the token. In the Settings tab, you will find the button Allow access. Click this button and you will be guided through the process. At the end, you will return to our basic settings and save them once.
Incorrect procedure?
Updating the token directly in Seller Central itself, i.e. without using the button described above, no longer works. The reason is that we receive and store information relevant to synchronisation through this process. If the procedure is not followed, we do not receive this information and thus cannot synchronise any data.
What else needs to be done?
After updating the token, orders received from that point onwards will be imported again.
However, orders that were placed on Amazon during the period when the token was expired must be requested again as described here.
Stock levels, prices or shipping confirmations will be transferred automatically afterwards.
Comments
0 comments
Article is closed for comments.