Media
1 item
Description
This extension extracts order history from your Amazon account. Amazon used to provide csv reports for US customers only, but it… This extension extracts order history from your Amazon account. Amazon used to provide csv reports for US customers only, but it didn't include digital orders, shipping, total amount, or payment information. Sometime in the middle of 2020, Amazon withdrew the feature even in the USA. This extension aims to fill the gap. How to Use ---------- After you install the extension, you won't see anything until you view your order history on the website (Your Account -> Your Orders). Get to your orders page, then click on the extension icon at the top right of the Chrome window; look for an orange upper case A. Once you do this, you should see buttons with years on the extensions pop-up window. Clicking on one of these buttons causes the extension to sift through all of your order pages and show you a searchable, sortable table with all of the orders in. It can take a few seconds to get all of the pages. A blue button enables you to download a CSV (viewable in Excel and other spreadsheet programs) of the order table the extension has assembled. It's better not to have more than one amazon tab open while the extension is doing stuff. I (Philip) find the Items CSV more useful: https://github.com/philipmulcahy/azad/blob/master/doc/img/items_csv_2023-12.png Here's a slightly more wordy quick-start guide: https://github.com/philipmulcahy/azad/blob/master/README.md#quick-start-instructions Currently supported: amazon.com.au, .ca, .de, .es, .in, co.uk, com, .com.mx (partial), .ae (experimental). For at least some of these sites, I know that the extension is missing some of the native language strings it needs to find your data. Many users, particularly in Germany seem to use the english version of their country's site to get better results, but if you want better results in your language, you can help me by providing order debug information and marked up screenshots showing me where the missing/wrongly scraped data can be found. For other Amazon sites, please submit debug information as described in https://github.com/philipmulcahy/azad/blob/master/README.md Bug reports are gratefully accepted (see github link below), with extra points awarded for: 1) reproducibility - if you describe it well and I can reproduce it then it's normally straightforward to fix. 2) staying in contact - fire and forget bug reports are often impossible to reproduce and are seriously demotivating. 3) using courteous language. 4) using English - you're not paying me and while I can scrape by in French and German, I'm spending more of my spare time on this project than you are, and it's not about learning human languages. 5) having read the (very brief) instructions - and if English is not your favorite language, you have two choices: i) Google translate (don't send it to me!) ii) Sending me a translation (better than Google's) of the instructions. I will figure out how to incorporate it and list you in the credits. Feature requests: if there's a github ticket outstanding for the same thing, please add your thoughts there rather than making a new one. You can signal your sincerity by clear communication and responsiveness to follow-up queries. Changes 1.16.24 --------------- #417 1) Fixed "Failed to scrape for some .com users" caused by site removing some html used by the extension. 2) Ported build scripts to js (from .sh) so that build works on windows. Both parts were contributed in draft form by Eric Jorgensen, aka @nebosite, who uses Azad to feed his Budgito tool (https://github.com/nebosite/budgito). Thank you Eric! Changes 1.16.23 --------------- Not used. Changes 1.16.22 --------------- #312, #327, #359, #367, #368, #414 Numerous reliability improvements and tech-debt repayments. The only functional change that stands out is the inclusion of "strategy stats" of recent scrapes in order debug json dump files. These statistics count how often each alternative scraping strategy is successful at various points in the code, without leaking personally identifiable information. Changes 1.16.21 --------------- #369 Improved scraping of returns refund amount (at order level, not item level). #385 Improved reliability of order debug json dump file creation, plus additional console logging. #??? Many non-functional code health improvements, now passing eslint with no warnings or errors. Source Code ------------- https://github.com/philipmulcahy/azad contributors (Thank you!): https://github.com/philipmulcahy/azad/graphs/contributors Premium Features --------------- Please read: https://github.com/philipmulcahy/azad/blob/master/doc/commercial_features.md Donations --------------- If you'd like to thank me financially, please don't! Don't worry: just redirect your gratitude here instead: https://www.justgiving.com/fundraising/azad-pah Donations entitle you to nothing except a warm feeling of righteousness/generosity. Premium Subscriptions --------------- It is necessary to subscribe ONLY if you want to use a small set of features aimed at commercial users. Paying for an annual subscription also entitles you to any new subscription-only features I might add during your subscription period. Please see the blurb in the subscription flow for more details, also: https://github.com/philipmulcahy/azad/blob/master/README.md#subscribe-to-premium-features. I offer no warranty of any kind: this is a personal project that you are welcome to use and contribute to. I am a human being, not a corporation and I don't make my living from this extension. Please bear that in mind before complaining about bugs or making false statements in your reviews of this product - others have been there ahead of you: The most amusing (and demotivating) posts tend to fall into one or more of the following three categories: i) I ordered stuff from you and it hasn't arrived: no stars for you Philip (I am not Amazon, and you haven't given me any of your money). ii) Your extension stole my credit card details (It never sees your card details - only stripe.com gets those - and it carefully avoids seeing your amazon login credentials as well - you are free to inspect the source code to verify this) iii) You have to pay, and it still doesn't work. (You don't, and I'm sorry it's not working for you - would you like some help?) Strangely none of the authors ever follows up with evidence or indeed any reasoned feedback at all. New Commercial Features --------------- If you seek new commercial features, please read https://github.com/philipmulcahy/azad/blob/master/doc/commercial_features.md before even thinking about contacting me directly. I am bored of reading proposals from malware distributors.