How to Integrate Amazon MWS with Daton
Learn how to seamlessly connect Amazon Merchant Web Services (MWS) with Daton, enabling you to streamline your data integration process and maximize the potential of your Amazon business.
How to Integrate Amazon MWS with Daton
Learn how to seamlessly connect Amazon Merchant Web Services (MWS) with Daton, enabling you to streamline your data integration process and maximize the potential of your Amazon business.
Amazon MWS Merchant Token
Please grant access to our Developer ID by following the steps outlined in this document: https://docs.sarasanalytics.com/faqs/source-api-keys/amazon-mws-merchant-token-and-auth-token
Integrate AmazonMWS with Daton
- Sign in to Daton.
- Select AmazonMWS from the list of Integrations.
- Provide Integration Name, Replication Frequency, and History. The integration name would be used in creating tables for the integration and cannot be changed later.
- Provide Merchant/Seller ID, MWS Auth Token, and Marketplaces listed in. You can get your details from the MWS Auth Token.
- Post successful authentication, you will be prompted to choose from the list of available tables.
- Then select all required fields for each table.
- Submit the integration.
Workflow
- Integrations would be in the Pending state initially and will be moved to the Active state as soon as the first job loads data successfully into the configured warehouse.
- Users would be able to edit/pause/re-activate/delete integration anytime.
- Users can view job status and process logs from the integration details page by clicking on the integration name from the active list.
Known Issues
- Cancelled reports - Report requests can get cancelled if there is any parallel process using the same requests or when users manually request for these reports from console. Daton will try again in subsequent jobs in case of cancelled or failed report requests and there will not be any loss of data.
- Changes in fields and datatypes - We have observed that there could be changes by Amazon in the report field names. While we are trying to make the migration process as seamless as possible, it may be required to reload the reports if any names or datatypes change.
- Presently, daily reports will be processed 2 times in a day to account for failure reports. We will optimize this further in our upcoming releases and try to process only one successful job.