Cart price rule is not being applied in the sweden store view when the postal code contains a space.

[imran9935]

Preconditions (*)

Tested in this versions:

1. Magento Developer branch

Description (*)

When applying a Cart Price Rule in the Sweden store view, the discount is not applied correctly if the postal code contains a space. For example, the postal code 100 00 causes the cart price rule to fail, Additionally, when entering a Swedish postal code without a space (e.g., 10000), it is giving a validation warning (screenshot-1).

Screenshot 1:

Screenshot 2:

Steps to reproduce (*)

1. Access magento admin panel
2. Create a Cart Price Rule with condition (screenshot-2)
3. Create Sweden store view
4. Go to the frontend Sweden store view
5. Add a product to the cart
6. Enter a postal code with a space (e.g., 100 00) during checkout, discount is not applied
7. Enter a postal code without a space (e.g., 10000), it gives warning

Expected result (*)

Cart Price Rule should apply correctly when a Swedish postal code is entered, and without a space it should not trigger any validation warning.

Actual result (*)

Cart Price Rule is not applied when a Swedish postal code is entered, and without a space it triggers a validation warning.

Additional information (*)

When we create the condition as in screenshot-2 and go to the Swedish store view on the checkout page, using a zip code without a space gives a validation warning (screenshot-2). However, when the user enters the standard Swedish postcode format with a space, the discount is not being applied. This behavior is confusing, as the system rejects the incorrect format but also fails to apply the discount on the correct format.

[m2-assistant]

Hi @imran9935. 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.

• 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

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