Catalog price rule not applied when customer adds VAT number at checkout

[ludo-mon-key]

We have noticed that if the "Configuring VAT ID Validation" is activated when a user adds a product to the cart to which a catalog rule is applied and enters a VAT number at checkout, the system disapplies the catalog rule.

Preconditions (*)

Magento version 2.4.3-p1

Steps to reproduce (*)

Important: By the way, this is the default issue in both Blank and Luma themes with sample data

1. in Admin configure the VAT ID Validation following the instructions at the link: https://docs.magento.com/user-guide/tax/vat-validation-configure.html
   Here are the screenshots:
   

2. Create a catalog rule and apply it to all "Customer Groups"
   

3. In Front End, add a product with the catalog rule applied to the cart
   

4 Go to Checkout

5 In Checkout entered VAT number, in the case of the screenshots we used a domestic VAT number

Expected result (*)

The price of the product should have the catalog rule applied, in our case $ 33.60

Actual result (*)

The price of the product is without catalog rule applied, in our case $ 42

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ X] 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 @ludo-mon-key. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Delta. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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.

[ludo-mon-key]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @ludo-mon-key. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @ludo-mon-key, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[ludo-mon-key]

https://github.com/magento give me 2.4-develop instance

[ludo-mon-key]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @ludo-mon-key, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[ludo-mon-key]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @ludo-mon-key. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @ludo-mon-key, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[ludo-mon-key]

@engcom-Delta no reply? Do you need any other information?

[ludo-mon-key]

@magento-devops give me 2.4-develop instance