Amazon MWS API: some orders are missing when loading orders

Question

I have implemented a system to download Amazon seller orders. The system works as follows:

• We start ordering from 12:00 to 14:00, so I tell Amazon (through their Java client): "Give me all orders from 12:02 to 2:00 (two minutes difference for placing pending orders, as described Amazon in their API).
• We fully load these orders: if more than a hundred we use the next token, and as soon as we have all of them, we use the listOrderItems operation for each order to get positions.

Some of these orders are pending, and if so, we save them in our database and check them the next time to see if they are ready for download. Our next job will work during the next two-hour interval, requesting all orders from 2:00 to 3:58.

This operation worked fine, but our customers started reporting missing orders from the end. Apparently, from time to time, the order slips through the notorious cracks, and we do not know why. To fix this, we set a 30-minute overlap so that every time we ordered orders, we watched 30 minutes in the past. In addition to the penalty for loading redundant orders, we need to check the database to see if the order has already been processed, so it slows down a bit.

And to wipe the salt in the wound, she still hasn't fixed the problem! This does not happen so often, but 0-4 orders appear on average per day.

Answer 1

Receiving orders through ListOrders seems to have a number of pitfalls.

Below is the response from MWS Support ,

Please note that the order is filled only in ListOrders data when it cleared some internal checks (mainly for fraudulent orders). This means that there will be a delay between when the order is and when it appears in API requests (or in SalesCentral, for that matter). This delay is usually several minutes, sometimes half an hour and very rarely several hours.

unshipped . --- 7 , , , API ListOrders. order --- 17 , . , .

, , , .

, - GetReportList, _GET_ORDERS_DATA_ , , - , . "" Amazon . , .