mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-11 04:32:39 -05:00
[Feature] Amazon Order / Item import #1963
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1963
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @axjasf on GitHub (Mar 12, 2025).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
We order a lot of things through Amazon - but the categorization is always manually done on the master transaction. This does not reflect reality: Many Amazon Orders hold Items from very different categories and are split into one or more payments, obfuscating what the real categorization of Amazon orders should be.
Describe your ideal solution to this problem
Using https://github.com/philipmulcahy/azad to download orders and items into csv files, a categorization engine could categorize these items (e.g. with the help of machine learning methods) and split Amazon transactions proportionally based on the categories in the orders.
Teaching and learning
No response
@github-actions[bot] commented on GitHub (Mar 12, 2025):
✨ Thanks for sharing your idea! ✨
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).
The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+
Don’t forget to upvote the top comment with 👍!
@youngcw commented on GitHub (Mar 12, 2025):
Can't you make the amazon transaction a split? That would break it up into different categories
@axjasf commented on GitHub (Mar 12, 2025):
I have hundreds of Amazon orders every year with very disjoint items. It would be an awesome feature. I've prototyped it before, but I am not wanting to build a system from scratch.
@DennaGherlyn commented on GitHub (Jun 10, 2025):
This is something similar to what I'd like to have. Automatic split transactions based on an Amazon purchase ID.
Like you get a transaction with a note property like
###-#######-####### AMZN Mktp DE XXXXXXXXXXXX. Where ###-#######-####### is your order ID. Looking up the order ID would show which items where purchased and put each in it's own split transaction. Then based on what the split notes say it could be automatically or manually get categorised.Sadly it's not that simple as Amazon splits bank transactions from orders based on when they are shipped, so it needs some solid logic behind it.
I don't think that adding LLM just for Amazon transactions would be the right way. If LLMs get implemented then it should be available for all transactions.
This is something I've thought of for a while. I can't make any promises, since I have already so much on my plate, but I'd like to look into this some more.