Coupon for single use can be used multiple times

[HenKun]

Preconditions and environment

• Magento version 2.4.6-p2
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Create a cart rule with coupon usage and usage per coupon = 1
   

2. Add fixed cart as Action
   

3. Generate coupon code (used is no, used times is 0)
   

4. Open browser 1, apply coupon code an go to last checkout page
   

5. Open browser 2 (or incognito tab), apply coupon code an go to last checkout page
   

6. Place order in browser 1 and 2 simultanously (a few seconds might be ok)

7. Both orders are successfull
   
   
   

8. Control coupn code usage. It is used and "times used" is 2
   

Expected result

Coupon can only be used for one order

Actual result

Coupon can be used multiple times, if fast enough

Additional information

Related:

https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/miscellaneous/coupon-code-used-more-than-once-adobe-commerce.html?lang=en
#23907
#35077

In this case, the consumer is correctly set up, so the coupon code usage is raised correctly. However, due to the queue mechanism, this is not done fast enough, so a customer can place multiple orders with the same coupon code within the time period the system needs to raise the coupon usage.

This can be exploited by customers, e.g. if coupon codes are used as simple gift cards.

Maybe it isn't a good idea to use queues in this scenario where it relies on an immediate raise of the coupon code usage?
Or a coupon code should already be blocked when it is applied to the quote.

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

[HenKun]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @HenKun. 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 @HenKun, here is your Magento Instance: https://e8d12c1de32a4407b2a6fa73cee90089.instances-prod.magento-community.engineering
Admin access: https://e8d12c1de32a4407b2a6fa73cee90089.instances-prod.magento-community.engineering/admin_1332
Login: 2855f26a
Password: 70e16008704e

[HenKun]

The issue can be reproduced on generated instance.
However:

• Multiple coupon codes per rule are not generated, I had to use the specific primary coupon code.
• Fixed amount discount for whole cart isn't working at all, no discount is applied. I had to use Fixed amount discount

Nonetheless, the issue is reproduced under these conditions. Further orders (after both orders are processed) with the same coupon code fail, so it can be concluded the queue works, but is not fast enough.

[achourey]

Hi @HenKun ,

I am also facing the same issue. Please let me know if you find any solution for this issue.

Thanks in advance

[HenKun]

The problem won't be easy to solve. This needs to be done completely or at least partially synchronous. I hope Magento will care for this issue

[m2-assistant]

Hi @engcom-Dash. 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.