qty is zero and salable is zero and product in stock in admin

[salah11172]

Preconditions and environment

• Magento version
• Anything else that would help a developer reproduce the bug
  2.4.5

Steps to reproduce

1-place order to product have qty =1
2- and complete order
3-the qty and salable will be zero and in admin in product page still show in stock

Expected result

Expected product out of stock if salable qty is zero

Actual result

product show in stock flag

Additional information

No response

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

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

[FadedOut]

@salah11172 This is a long-time issue (years) and requires modification of a file. Who knows if it will ever properly be fixed. It was supposed to be fixed in 2.4.6 but nope, still broken. Supposedly it's fixed in 2.4.7-beta but will probably be broken again by actual release of 2.4.7. This is usual of Magento. And they'll tell you to put your live production server on a beta build (2.4.7-beta) to get the fix instead of just pushing the fix to everyone. Terrible.

For the community fix if you want to have it working properly for now you could modify the file as noted in my ticket here: #35319 (comment) by another member. Make sure to make a backup of the original file before modifying just in case if you make a mistake modifying the file. But the fix does work, I used it since 2.4.4 up to 2.4.6-p1.

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

[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://d10338f5ad95d91c8ec6513f63f9a807.instances-prod.magento-community.engineering
Admin access: https://d10338f5ad95d91c8ec6513f63f9a807.instances-prod.magento-community.engineering/admin_9075
Login: 730c44fe
Password: 582883b95606

[engcom-Dash]

Hi @salah11172 ,

verified the issue in 2.4-develop instance and the issue is not reproducible,Kindly refer the screenshots.

Steps to reproduce:
1.Place the order with 1 saleable quantity and complete the order

Product out of stock if saleable qty is zero.

Thanks!

[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://d10338f5ad95d91c8ec6513f63f9a807.instances-prod.magento-community.engineering
Admin access: https://d10338f5ad95d91c8ec6513f63f9a807.instances-prod.magento-community.engineering/admin_562c
Login: 6b25268f
Password: 1a68a553d4c2

[salah11172]

I mean stock status dropdwon in product page in admin
if quantity and salable quantity equal zero
the stock status is still in stock

Please be honest with us and with yourselves
This problem exists and has been encountered by many people
This is not the correct solution to pretend that there is no problem and try to hide it

[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://d10338f5ad95d91c8ec6513f63f9a807.instances-prod.magento-community.engineering
Admin access: https://d10338f5ad95d91c8ec6513f63f9a807.instances-prod.magento-community.engineering/admin_56ca
Login: 476a4d7e
Password: 4c3f887fe0ab

[salah11172]

okay
steps :
1-in this product (sku=24-MB03) make qty =1 and assign source (source= new)
2- from admin placed order (incerment_id=#4) [salable qty become zero]
2-then complete order steps to make it complete [qty become zero ]
in admin in product page Source Item Status still inStock

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-9291 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[github-jira-sync-bot]

❌ You don't have permission to export this issue.

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-9291

[engcom-Dash]

@salah11172 ,

As per internal discussion,Again we are working on this issue and we moved this issue as Needs update.

Thanks.

[engcom-Dash]

@salah11172 ,

Verified the issue in 2.4-develop instance and the issue is not reproducible.
As per DevDocs By default stock status should be In Stock only...We need to set the Source stock status in backend when products goes to out of stock.

Thanks.

[salah11172]

no hope

[engcom-Dash]

Hi @salah11172 ,

By default stock status should be In Stock only...We need to set the Source stock status in backend when products goes to out of stock.
Kindly refer the below screenshots:

Thanks.

[engcom-Dash]

Hi @salah11172 ,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

[serzhik]

This ticket duplicates magento/inventory#3062