-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect cataloginventory_stock_status.stock_status after stock item update by REST #39578
Comments
Hi @zakdma. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Delta. Thank you for working on this issue.
|
Hi @zakdma , Thanks for your reporting and collaboration. We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the screenshot. Steps to reproduce
Can you please re-verify in latest 2.4 develop instance. Thanks. |
Preconditions and environment
Steps to reproduce
test-stock
test-stock
product pagetest-stock
product pagecurl -X PUT "https://domain.com/rest/V1/products/test-stock/stockItems/<stock_item_id>" -H "Authorization: Bearer " -H "Content-Type:application/json" --globoff -k --data-binary @- << EOF
{"stock_item": {"qty": 1.0, "is_in_stock": true}}
EOF
test-stock
product pageExpected result
Product should still be displayed as Out of Stock and can't be added to cart
Actual result
See product is displayed as In Stock and Add to Cart button is enabled
If you click Add to Cart button it cannot add it and error message displayed
Additional information
The problem is that after updating the stock item by REST API request field cataloginventory_stock_status.stock_status became 1 but it should remain 0 because the salable quantity is 0.
Manual reindexing of cataloginventory_stock indexer doesn't fix this bug. cataloginventory_stock_status.stock_status remain 1 after reindex.
It force us to resave product to correctly update salable status
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: