Issue with Magento 2 Tax Calculations not showing correctly on mini cart

[ashala-hapuarachchi]

Preconditions and environment

• Magento version - 2.4.5
• Set catalog prices to be Excluding Tax and have different tax rates per shipping region

Steps to reproduce

We have one store for Canada on our magento 2 website that show price excluding tax on the product page. Tax is only calculated at the checkout once you enter the shipping address. The calculation happens correctly here and the order summary is updated fine.

However if the customer decides to go back (lets say to the home page or any other product page) the mini basket shows same total for excluding and including tax. This even though the shipping address is now selected. You do see the correct totals on the basket page or checkout. It is just the mini basket that is facing the issue.

We initially thought it is something to do with our theme or custom modules. However going back to the default Luma theme and removing custom modules I still see the issue. One thing we did notice is that the mini-cart updates after a certain time, so it looks as if there is some sort of cache around the mini-cart and it does not refresh immediately.

If anyone has any ideas on this that would be really helpful.

Expected result

Including tax subtotal figure in mini-basket should show value with tax included.

Actual result

Including tax subtotal figure in mini-basket should shows value excluding tax.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ashala-hapuarachchi. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://8895fdb61d7308f73cd3dfec13dbb17c.instances-prod.magento-community.engineering
Admin access: https://8895fdb61d7308f73cd3dfec13dbb17c.instances-prod.magento-community.engineering/admin_4218
Login: 9c6cb3d4
Password: 1affa8d1fa57

[engcom-Bravo]

Hi @ashala-hapuarachchi,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is still reproducible.Kindly refer the screenshots.

Mini cart showing value as excluding tax.

Hence confirming the issue.

Thanks.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12749 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[ashala-hapuarachchi]

Hi @engcom-Bravo,

Thanks for looking into this. Just to add something I did find out was that if you delete the mage-cache-sessid cookie and reload the page it will show the totals correctly. In case that is helpful in looking into the issue.

Thanks,
Ashala

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[engcom-November]

This issue has been resolved and is now functioning as expected. Please find the attached screenshot for reference.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

This issue has been resolved and is now functioning as expected. Please find the attached screenshot for reference.