Grouped product stock status not changing to in stock when its child is added with qty and set as in stock through rest api

[rajeshScodilar123]

Preconditions and environment

• Magento version : 2.4.3 p1

Steps to reproduce

1. Create an grouped product with 1 child product, keep parent as well as child out of stock
2. Update the child stock using rest api the below endpoint and body
   endpoint : http://samplemagento243p1.com/rest/V1/products/{SKU}/stockItems/{item_id} (PUT)
   bearer token : use admin bearer token
   body : {"stockItem":{"qty":48, "is_in_stock": true}}

Expected result

1. child qty should be updated to 48 and stock status should be in stock
2. Parent grouped product stock status should be in stock

Actual result

1. child qty should be updated to 48 and stock status should be in stock
2. Parent grouped product stock status not changing to in stock

Additional information

It works fine when we update the qty and stock status of child from admin. Parent stock status automatically changed to in stock

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

[rajeshScodilar123]

@magento please provide the development instance

[rajeshScodilar123]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @rajeshScodilar123, here is your Magento Instance: https://ee1bd50574bdcc5a2b0033d2515b884e.instances-prod.magento-community.engineering
Admin access: https://ee1bd50574bdcc5a2b0033d2515b884e.instances-prod.magento-community.engineering/admin_da1c
Login: 10bef972
Password: 645aee32603a

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://ee1bd50574bdcc5a2b0033d2515b884e.instances-prod.magento-community.engineering
Admin access: https://ee1bd50574bdcc5a2b0033d2515b884e.instances-prod.magento-community.engineering/admin_eff8
Login: a2e6a2f8
Password: 444e89c1d840

[engcom-Bravo]

Hi @rajeshScodilar123,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Create an grouped product with 1 child product, keep parent as well as child out of stock
• Update the child stock using rest api the below endpoint and body

endpoint : http://samplemagento243p1.com/rest/V1/products/{SKU}/stockItems/{item_id} (PUT)
bearer token : use admin bearer token
body : {"stockItem":{"qty":48, "is_in_stock": true}}

Child Product qty is changed to 48 and it is IN Stock it is working fine.

Here Parent grouped product stock status not changing to in stock because we are updating for child products they both have different sku's and also we have tried from admin side to update the qty and stock status of child from admin. Parent stock status not changing automatically to in stock.

Could you please let us know if we are missing anything.

Thanks.