Tax Class set to None when creating new configurable variations in multi store mode

[dphilipps]

Preconditions and environment

Magento 2.4.5-p1
Multi store (Two stores, each with its own website)

When creating new variations of an existing configurable product in Store View Scope, the 'tax class' value in the new simple products is set to 'None' instead of the value set in the parent (the configurable). This results in no tax being added to these products in the cart and under charging customers for tax.

When creating a NEW configurable product, the initial child products are created correctly, with 'tax class' set as per the parent.

This bug is not present in single store mode or when creating new variations in 'All Store Views' scope.

This is present in a fresh multi store install of Magento 2.4.5-p1 with the Luma demo store.

Steps to reproduce

1. Ensure multi store is enabled (with at least 2 stores configured)
2. On product grid set filter Store View: Default Store View
3. Create a Configurable product with 'tax class' = 'taxable goods'
4. Edit Configurations
5. Confirm scope setting 'Scope: Default Store View'
6. Create variations and child products
7. Save product
8. Verify child products have 'tax class' = 'taxable goods'
9. Edit the configurable product and 'Edit Configurations' to create new variations
10. Save product
11. Check new child products 'tax class'

Expected result

New child product 'tax class' should be 'taxable goods'

Actual result

New child product 'tax class' is 'none' at 'All store views' and 'Default store views' scopes.

Additional information

I have verified this on current ver. dev-develop:

https://www.loom.com/share/cc6429e224cb4443b84674fc94e5dbb3

This is a very serious issue as store administrators may not notice child products are created with no tax class set, resulting in customers making purchases without tax being added at checkout and the merchant suffering a shortfall in the amount of tax collected for the order.

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 @dphilipps. 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.

[dphilipps]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @dphilipps. Thank you for your request. I'm working on Magento instance for you.

[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.

[magento-deployment-service]

Hi @dphilipps, here is your Magento Instance: https://8bbe3360eed9855627958e31d3331f80.instances-prod.magento-community.engineering
Admin access: https://8bbe3360eed9855627958e31d3331f80.instances-prod.magento-community.engineering/admin_fecf
Login: 67a21b82
Password: 34c6e3bb447b

[dphilipps]

Video demonstrating the issue on the above develop instance.

https://www.loom.com/share/cc6429e224cb4443b84674fc94e5dbb3

[engcom-Bravo]

Hi @dphilipps,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

• Ensure multi store is enabled (with at least 2 stores configured)
• On product grid set filter Store View: Default Store View
• Create a Configurable product with 'tax class' = 'taxable goods'
• Edit Configurations
• Confirm scope setting 'Scope: Default Store View'
• Create variations and child products
• Save product
• Verify child products have 'tax class' = 'taxable goods'
• Edit the configurable product and 'Edit Configurations' to create new variations
• Save product
• Check new child products 'tax class'

.

Child Products are created with Tax class as None.In frontend tax is not applying to the products.

Hence confirming this issue.

Thanks.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-8227 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.

[dphilipps]

Thanks for the prompt confirmation of the issue @engcom-Bravo

[dphilipps]

Good news a PR has been created. Could you please provide a link to the PR @engcom-Hotel ?