-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
How does "Calculate taxes automatically" work in Medusa v1? #10879
Comments
hi @u11d-michal-miler, thank you for reaching out about this subject, indeed, when the automatic taxes are disabled, it is supposed to prevent the the taxes to be computed every time we get the totals unless |
Hello @adrien2p, |
Indeed, when calling this end point, the taxes are forced, if you look at the method being called by this end point here |
OK. In that case we need to carefully go through the checkout flow and identify places where taxes fetching is forced by Medusa code. Thank you for your help, @adrien2p! |
It is a pleasure, should I close this ticket for now then? |
Sure, I believe the ticket can be closed. |
What Medusa version and documentation are you using?
v1
Preliminary Checks
Issue Summary
Could someone clarify what disabling the "Calculate taxes automatically?" option in Medusa Admin V1 actually does?
The admin panel provides the following explanation:
We use a 3rd party tax provider and want to optimize API calls. However, even with the checkbox disabled,
AbstractTaxService.getTaxLines
method is still invoked numerous times.I expected that disabling the checkbox would stop automatic tax calculations and require us to trigger them manually. However, it seems the calculations are still performed as before. Is it possible to explain how this flag works and provide guidance on minimizing the number of calls to the 3rd party tax provider? I feel the current documentation is not meaningful enough.
Thank you for your help!
Manual taxes doc: https://docs.medusajs.com/v1/modules/taxes/storefront/manual-calculation
How can this issue be resolved?
No response
Are you interested in working on this issue?
The text was updated successfully, but these errors were encountered: