-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recalculate totals on order change #17769
Comments
Hi @Hlavtox, Thanks for your report. Thanks! |
Hello, Wdyt?
Thank you very much for your time guys :) |
Second option is what we aim for but as you can imagine this is very complex. We have already started gathering all issues about rounding, you can find the Price & taxes epic here : #9703 Of course, this needs a deep functional and technical study before we can really start working on it. |
Personally, I wouldn't rush it and settle for some “hackjobs”. Even if we temporarily fix it by Better to think it through. It waited a few years, it can wait for some more time. Proper tax and discount calculations in FO are more important. We (merchants) can always tell a customer: “Make a new order, we don't change them.” 👍 |
Perfect :), thank you very much @colinegin @Hlavtox I suggest closing this issue and continuing discussion there in #9703. wdy? |
Hi guys, just for your information, I just created a new EPIC dedicated to rounding issues. You can find it here : #19445 Have a nice evening ;) |
Hi guys, I was browsing the code for the migrated admin order page and there is still a lot of code that could (and does) cause trouble.
Whatever changes you do, add or remove products, add or remove discounts, it adds or subtracts the amounts from the order and invoice. But this creates room for errors, negative totals, rounding errors, because it works with rounded values. (Like #13809)
I don't know if you guys had a discussion about this, but I think it would be good (if there is time) to change to logic to completely recalculate the order every time something changes. This would eliminate all the trouble there is.
The text was updated successfully, but these errors were encountered: