How can Saleable Quantity be higher than physical quantity?

[adamlavery]

Preconditions and environment

OS 2.4.3-p1

Steps to reproduce

No idea how to reproduce something that should never be able to happen.

Expected result

Saleable Quantity should never be higher than physical quantity

Actual result

How does this happen? How can saleable quantity be 2 when physical quanity is 0?

There is just one stock source (default). Quantity is correct but where does it get saleable quantity from? That is, what database records contain the information that it is displaying for Default Stock.

To confirm, there are no reservations for this product, which in any case should reduce saleable quantity not increase it.

Additional information

As a result of this discrepancy that product can be purchased even though there is no stock. Until whatever has messed up in the data can be corrected, only way to deal with it is to manually set the product out of stock so it cannot be ordered.

Looking for a clue as to where this data comes from so it can be manually corrected. Given Knockout destroys any useful link between what is displayed and where it comes from, without knowing how it was put together how can we know which bit of code added that value? Yes it's a Data Provider, but which bit of code in the mass of XML and modifyData calls actually does this value?

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

[adamlavery]

Please don't ask to reproduce this. As noted this scenario shouldn't be possible so reproducing is a non-starter. What's needed is to look at the code the generates the Saleable Quantity figure and work out how that can be wrong and cause this.

[FadedOut]

@adamlavery

Yeah I don't think that looks right. Something might be misconfigured maybe?

A shot in the dark, but try checking the settings here:
Store Config > Catalog > Inventory > Product Stock Options (Out of Stock threshold)

Also check to make sure the indexing is running correctly (check cron.log). Maybe just re-run the reindex command just in case. Maybe also try just changing the number for "Out of Stock threshold" then run the reindex command. Because I have mine set to 30 there and the "Salable quantity" might say 100 but "Quantity" will say 130 - which is how it should be (I'm on Magento 2.4.5-p1 just for reference)

Hopefully this helps because that's a pain (to manually change the stock to in/out) and shouldn't need to be done that way.

If the above don't help, was there an update recently then you noticed this started happening? Maybe it was an update that caused it?

[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).
     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!

---

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

[engcom-Dash]

@magento give 2.4-develop instance

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Dash, here is your Magento Instance: https://988851969daa02982321ff56075a8295.instances.magento-community.engineering
Admin access: https://988851969daa02982321ff56075a8295.instances.magento-community.engineering/admin_0861
Login: 22d63b7a
Password: 359caa22d844

[engcom-Dash]

Hi @adamlavery ,

We are trying to reproduce the issue in 2.4-develop instance...we are not able to reproduce because we are getting Expected result.
Screenshots:

Steps:
1.Install Magento instance
2.Go to catalog---> Products
3.saleable quantity not greater then quantity

Let us know if we are missing anything!!!

Thanks!!!

[adamlavery]

As stated at the start, this should not happen. How it's happened is anyone's guess hence being able to reproduce it is impossible. Neverthess it has happened. Question now is how can it be corrected. As far as I'm aware Saleable Quantity is calculated as quantity minus any reservations. There are no reservations but even if there only 0 minus a minus produces a positive result!

We therefore need to look at the code that calculates the value that is presented on the product grid to detemnine why it is wrong. However, the complex nature of the new UI combined with Knockout makes tracking this back to source near impossible. Therefore can someone point to where this value gets put into big blob of data that knockount uses? Then perhaps with some debugging we can figure out why it is wrong.

Thanks.

[FadedOut]

As stated at the start, this should not happen. How it's happened is anyone's guess hence being able to reproduce it is impossible. Neverthess it has happened. Question now is how can it be corrected. As far as I'm aware Saleable Quantity is calculated as quantity minus any reservations. There are no reservations but even if there only 0 minus a minus produces a positive result!

We therefore need to look at the code that calculates the value that is presented on the product grid to detemnine why it is wrong. However, the complex nature of the new UI combined with Knockout makes tracking this back to source near impossible. Therefore can someone point to where this value gets put into big blob of data that knockount uses? Then perhaps with some debugging we can figure out why it is wrong.

Thanks.

No need to "track it" as it is not default behavior, it is something happening with your site and your site only.

Read what I posted earlier to you and check configurations (and indexing). Or it was an update conflicting with your setup. What you're seeing is not happening on a normal working installation and I have never seen that happen before - hence I don't believe this to be a "bug".