Product is oversold when multiple people purchase same product at the same time

[secomm-dev]

Preconditions (*)

1. Magento 2.3.x
2. A product with QTY = 1, Saleable-QTY = 1
3. Any payment method, any shipping method
4. Any environment (standard LAMP following Magento recommendation)

Steps to reproduce (*)

1. Multiple people add the product into cart. E.g. 10 people working on 10 different devices
2. Proceed to Checkout
3. Enter all required information: shipping address, shipping method, payment method
4. At the very same time (millisecond), all people hit Submit button

Expected result (*)

1. Only 1 Order should be created
2. QTY remains 1
3. Saleable-QTY becomes 0

Actual result (*)

1. Multiple orders are created (it's a random number, but definitely more than 1)
2. QTY remains 1
3. Saleable-QTY becomes a negative number which equal to the number of orders that should have not been created (but have been)

Additional Information

• If we remove MSI related modules, the issue is gone. Orders are created and stocks are reduced correctly. Therefore, I think this issue is related to MSI workflows and algorithm.
• We have experienced this issue on both live and development environments.
• On live environment, this issue is likely to happen when there is high traffic with some products are on promotion in limited period, which attract customers to purchase same product(s) at the same time.

---

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.

[m2-assistant[bot]]

Hi @secomm-dev. Thank you for your report. To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

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

[m2-assistant[bot]]

Hi @sambath1293. 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: :point_down:

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

[sambath1293]

Hi @secomm-dev The issue specific for MSI should be reported in the MSI repo

fyi: @sidolov @smoskaluk @sdzhepa

It seems this issue MSI specific and should be fixed in MSI repository.

EngCom team, please confirm and transfer this issue to the https://github.com/magento/inventory/issues

Closing this issue

[secomm-dev]

Hi @sambath1293 thank you.

I have moved the issue to Inventory repository.