Skip to main content

Amazon Best practice: MFN order import

This best practice deals with MFN orders (MFN = Merchant Fulfillment Network, i.e. shipment by the seller) that are not imported. We assume that the order import is activated in the basic settings for Amazon.

1. MWS registration

MWS registration allows our developers to access your Amazon account. When the registration is finished, the access rights are displayed in your seller central within Settings » User permissions in the Amazon MWS Developer Permissions area. If we are not granted access rights, we can neither retrieve data from nor send data to Amazon (as requests are blocked by Amazon).

Check whether developer permissions are set up. To do so, go to Settings » User permissions in the Amazon seller central. Another indicator that there are no developer permissions is this error message: Error:Access to Reports. (GetReportScheduleList) is denied. You will receive this error message for almost all requests if you did not set up any developer permissions. If you set up scheduled reports, then error messages are displayed in the logs or within Setup » Markets » Amazon » Data exchange » Reports. How to set up scheduled reports is described below.

How to carry out the MWS registration is described in our manual.

2. Auth token expired

The Auth token is generated during the MWS registration. The token is used for the synchronisation between plentymarkets and Amazon and it is directly linked to the authorisation. The token has an expiry date. This is to ensure that deactivated interfaces no longer have access after the token is expired. Vice versa, this means that the token must be updated from time to time. When the token has expired, developer permissions granted with the MWS registration are no longer valid and no synchronisation can be carried out.

Check whether the token has expired by viewing the developer permissions in your seller central. Another indicator that the token has expired is the error message Access denied.

You can update the Auth token via this link . (The expiry date is set in the future. This ensures that the permissions are valid again.)

3. Wrong access data

In order to enable contact between our system and your Amazon account, the access data saved in the basic settings must be correct.

If the seller token is not saved correctly within the basic settings, the error message ERROR: AuthToken is not valid for SellerId and AWSAccountId is issued.

The correct token and your seller ID (merchant ID) can be found via the MWS registration (at the end of the registration). As an alternative, you can enter the merchant ID into the field for the seller token.

After you have changed the seller token in the basic settings for Amazon, click on refresh token under Setup » Markets » Amazon » Data exchange » Reports » Tab: Token Refresh. This way, the changes apply immediately.

4. Scheduled reports

If all of the issues mentioned above are solved, you can start the synchronisation. In order to import orders, Amazon generates reports which contain the orders. We retrieve those reports.

The generation of the reports is not preset in the Amazon settings. You need to carry out the settings.

Go to Setup » Markets » Amazon » Data exchange » Reports » Tab: Scheduled reports to set up a continual automatic generation of scheduled reports. This function is called scheduled reports.

  1. Select the Amazon account.

  2. Select the interval under MFN Orders.

  3. Click on the gear-wheel icon Schedule MFN order report.

We recommend to use 15 minutes as interval, as reports from Amazon that are not marked as retrieved are retrieved every 15 minutes.

Click on Import report list to check whether your settings were saved.

Viewing the scheduled reports
Figure 1. Viewing the scheduled reports

As a result, the schedulers that you activated for your Amazon account are displayed. The report type Get Orders Data is required for the MFN order import. It should be set to 15 minutes. This setting may cause orders to be imported late (for example if the interval is set to weekly).

5. Further error messages

If you receive the error message The seller does not have an eligible Amazon account to call Amazon MWS., it may be that our system is not authorised to access Amazon. Check the developer permissions as described above. If they are not available, add the permissions via the MWS registration. If this does not help, contact Amazon. (Either your seller account is no power seller account and therefore the Amazon MWS API cannot be used, or your account is not properly activated).

To top