Extension Stops at Incomplete Pagination When Pulling Amazon Orders

[TrtlyUndrCtrl]

I order a large number of items from Amazon, and I was trying to pull all of my 2025 orders by selecting the 2025 option in the extension. Unfortunately, the extension only retrieves a little over half of the orders for the year.

What I Observed:

• When I first load all of 2025’s orders on the Amazon website, the pagination at the bottom shows pages 1 through 51.
• The extension stops scraping right around page 51.
• However, if I manually click on page 51, Amazon updates the pagination to show the true last page, which is page 95.
• The extension doesn’t seem to detect these additional 44 pages and therefore misses the rest of the orders.

The same behavior occurs when I try to pull my 2024 orders:

• Initially, Amazon shows pages ending at 51 again.
• But when I keep clicking the last page repeatedly (5 times in total), the actual total is 224 pages.
• The extension never goes past the first displayed "last page" number.

Likely Cause:

It looks like the extension assumes the first “last page” number shown by Amazon is the final page. In reality, Amazon only updates the true last page after navigating deeper into pagination.

Impact:

• For users with a high volume of orders (like me), the extension fails to retrieve all data.
• The issue prevents complete exports for entire years.

[TrtlyUndrCtrl]

I actually just figured out that the startIndex attribute can be set to an impossibly high number such as 99999999 and this will immediately show the true count of pages.

https://www.amazon.com/your-orders/orders?timeFilter=year-2024&startIndex=9999999

This attribute can be set to control the page number if you start at 0 and add 10 each time for the number of pages that it shows then it will ensure all of the orders are picked up. You can alternately just have it go through and add 10 to the startIndex until Amazon displays a blank order page. Either one would work I would think.

[philipmulcahy]

Hello @TrtlyUndrCtrl !

This appears to be an amazon bug (but I guess you've figured that out already) - there is discussion of it on a recent (closed) azad bug ticket where I jumped through some hoops in a (then believed successful) effort to work around the fact that amazon sometimes reports different numbers of annual orders as you work through the index pages of that year.

I believe the most recent relevant code change adopted a "bayesian" approach - as it parses the fetched index pages, it observes the claimed number of orders for the year (which we know sometimes changes), and if it sees that the number has increased then it extends the loop that's been generating the urls and queuing them.

One of your outlined strategies seems problematic because the index pages are fetched in parallel (currently up to six at a time). Losing that parallelism would slow scrapes down a lot. (I hear you correctly pointing out that slow is better than wrong).

Do we know for sure that the "infinity" page actually returns the true number, or if it's just another roll of the dice (one that is guaranteed not to return any orders)?

I would dearly love to roll back the "bayesian" code - it makes me shudder every time I think of it.

[TrtlyUndrCtrl]

I have tried it with multiple years and multiple accounts and every time the "infinity" page will show the correct last page

[philipmulcahy]

Thank you - I am going to experiment (when I get some time), with a view to retiring the bayesian code.

[TrtlyUndrCtrl]

My pleasure! I'll be eagerly awaiting a fix as I am unable to import anything until then. I know this is a free time thing for you do I don't expect you to drop everything and fix this immediately.

Note: Sorry for the closing and reopening of this ticket that was not intentional

[TrtlyUndrCtrl]

While collecting more details, I noticed a change today: when I load Orders and switch filters, the order totals and final page now appear immediately. I’m not sure if Amazon shipped a permanent change or if this behavior is intermittent, but I wanted to share the “infinity” links you can use for quick reference when you update the code.

Reference links (jump to final page via startIndex=9999999):

Last 30 days
https://www.amazon.com/your-orders/orders?timeFilter=last30&startIndex=9999999

Past 3 months
https://www.amazon.com/your-orders/orders?_encoding=UTF8&startIndex=9999999

Full year (replace YYYY with a 4-digit year)
https://www.amazon.com/your-orders/orders?timeFilter=year-YYYY&startIndex=9999999

[TrtlyUndrCtrl]

I am happy to report that I've run azad with the 2025 option and it appears to have pulled all of the orders successfully! So, this can be put on a back burner assuming Amazon doesn't revert back whatever changes they've made to make things show correctly the first time.

[philipmulcahy]

this feels like Amazon have more than one version of the code that impacts this problem in production, and people are getting lucky/unlucky depending on which amazon endpoint/server they are getting on the day. I would like to be able to handle all versions that users are encountering, so let's keep this ticket open for now.