-
Notifications
You must be signed in to change notification settings - Fork 12
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
Order level adjustments break re-reporting an order #178
Comments
It's not really a bug... we added a configuration option so that people can provide a calculator that allows people to implement the behaviour that they want. The reality is that no behaviour we do here will actually be "correct". |
Yeah I agree... the tricky bit is that this will currently break the default refunding behavior with no feedback. We may at least want to display a clear message to the user about what happened and why and direct them to implementing their own behavior. |
Something to double check - We need to make sure we are using the |
Update: This has been checked.
|
Closing in favour of #180 which describes implementing the error reporting and preventing the creation of a REFUND transaction without a corresponding CREATE transaction and getting TaxJar in a bad state. |
If you try to make an order level adjustment and then a new payment to process a refund for an order, the system will try to do two things
However, order level adjustments are not taken into account when reporting the total order amount to Taxjar. This causes Taxjar to throw an error when trying to report the new amount.
This is because order level adjustments are not compatible with tax - creating an order level adjustment will not adjust the total tax collected. For this reason, we can't even split the amount of the order level adjustment between items.
To get the correct totals with the order level adjustment, we would need to convert the order level adjustment to individual line item adjustments and recalculate the order and tax.
The text was updated successfully, but these errors were encountered: