Magento2: product with salable qty 0 is not considered out of stock

[ioweb-gr]

I'm not sure if you consider this expected behaviour but it's a bit confusing for shop onwers and customers so I'll just document my experience here.

Preconditions (*)

1. Magento 2.3.4

Steps to reproduce (*)

1. Set shop to hide out of stock products from Stores -> Configuration -> Catalog -> Inventory
2. Create a product with qty 1
3. Order the product once
4. Do not handle the order
5. The product status is:
6. stock: status in stock
7. qty: 1
8. salable qty: 0

Expected result (*)

The product does not show in the frontend of the store because it's not salable (the same as out of stock effectively)

Actual result (*)

The product shows up in the frontend without an add-to-cart button because the product is in stock but not salable.
If the shop owner cancels the order the product reappears as salable.
If the shop owner processes the order the product hides from the catalog as it becomes out of stock.
So the product is hanging on an intermediate state which is not expected by the shop owner

It's a bit confusing for the shop owners. Otherwise there needs to be a second setting in catalog to hide products that are not salable. The customer is also confused because he sees the product but cannot order it.

[m2-assistant[bot]]

Hi @ioweb-gr. 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.

@ioweb-gr do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

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

[m2-assistant[bot]]

Hi @sudheers-kensium. 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.

[sudheers-kensium]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @sudheers-kensium. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @sudheers-kensium, here is your Magento instance.
Admin access: https://i-27223-2-4-develop.instances.magento-community.engineering/admin_1ef3
Login: e1d5e376 Password: 1c3fb2b0f43c
Instance will be terminated in up to 3 hours.

[sudheers-kensium]

@ioweb-gr I am not able to reproduced the issue and it is working as expected on Magento 2.4-develop instance. So I am closing this issue.

[Mobecls]

we actually have the same issue. Products with Salable qty are showing on frontend and not considered as out of stock. Reindex is not helping. And we don't have repo steps...

[fedekrum]

I have the same issue on 2.4 release
Why has this issue been closed?

[ioweb-gr]

Sometimes I'm confused because people here seem to close issues without trying to reproduce correctly or ask clarification. So it ends up lost forever.

The issue is reproducible with the steps provided.

[frezelth]

Same problem here including on 2.4.1.
It's kind of blocking, do we have a workaround? Why is this issue closed?

[frezelth]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @frezelth, here is your Magento Instance: https://a4ba0f5864e5f06e973266b2c8a97bea-2-4-develop.instances.magento-community.engineering
Admin access: https://a4ba0f5864e5f06e973266b2c8a97bea-2-4-develop.instances.magento-community.engineering/admin_f98c
Login: 37553578
Password: b4440240aa5e

[frezelth]

Reproduced in the latest 2.4-develop.

• Display a product that has 100 items in stock.
• Add 100 items to cart
• Complete order
• Go back to product, still showing in stock but not possible to add it to the cart as salable qty is 0

[ioweb-gr]

Hopefully they'll reopen it but I highly doubt it.

[frezelth]

Still seems very random, because I was only able to reproduce this behaviour once. I tried with other articles and it worked ok.

[frezelth]

Definitely something wrong. After reindexing, products that were out of stock are now back in stock even if they have salable quantity to 0.

[s-kerdel]

Is there any update on this? This is blocking our instance from going live & is very bad for the user experience.
The issue is closed while the issue is still present, just like several other issues stating the exact same issue.

My thoughts: it seems like isSalable/getIsSalable/isSaleable returns 'true' while the actual 'salable' quantity is 0?
Also, it looks like isAvailable() does not take the above condition in consideration.

Note: just for clarity, this issue is still present in Magento 2.4.1!

[Kishorchhugani]

I have the same issue on 2.4.1
Any one have any solution for this?

[SchranzKatharina]

We also have this issue on 2.4.1 and it is really frustrating!

[engcom-Bravo]

A similar issue has been Confirmed with High Priority https://github.com/magento/magento2/issues/31117
Please follow all the updates on that issue.
In order not to have two duplicates, we are closing this issue and focus on https://github.com/magento/magento2/issues/31117

Thank you

[m2-assistant[bot]]

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