Java – Amazon – MWS: differences between reports and order lists

I'm trying to integrate Amazon mall orders into our system I did it with Magento before and thought it should be easy, but somehow I got stuck

I downloaded the Java API from Amazon and started using these examples So far everything has been so good - I can let them run But playing with the reports API and orders API, I began to wonder which one I would use if I just wanted to put undelivered orders into our system 1. Using the report API to perform this operation seems very complex and involves a large number of calls to MWS This was recorded by Amazon here 2. Using the orders API seems very simple I just need to create a listordersrequest, define the order types I want, and finally get them through the listorders call So my question is: what is the reason for choosing the reports API on the orders API?

It seems that Amazon recommends the reports API, but I really don't understand why it should be so complicated Why do I get reports when I can get orders directly?

Solution

Both methods are feasible This is why I chose the reports API:

>Reports are more scalable I believe that the MWS report can return an unlimited number of records Listorders can only return up to 100 orders You can use listordersbynexttoken to get more, but this will limit the problem and it is unclear whether you are just paging by offset (which may lead to lost / duplicate orders) or whether it is a snapshot. > You can confirm reports and filter unconfirmed reports Orders can also be confirmed, but I don't think there is a way to filter listorders according to the confirmation status. > Reports can be scheduled to be generated automatically every 15 minutes This means that it may not be as many as you think: in fact, there are only three intervals: one report listing unconfirmed orders, one for extracting the report you want, and the other for confirmation