Product stock alert's website and stock mismatch issue for multi website

[hiren-gujarati]

Preconditions and environment

• Magento version: 2.4.8-p1
• Multi website setup with MSI
• Global config value for Share Customer Accounts
• Enable Stock alert

Steps to reproduce

1. Create customer account on website A.
2. Subscribe to "Notify me when this product is in stock" alert from OOS product's PDP.
3. Logout and Login to website B with same customer.
4. Subscribe stock notify me on same product.
5. Open admin product edit page where it's showing only website A and there stock in stock alert.

Expected result

It should be show the correct website and stock instead of website from customer account is created.

Actual result

For all the website's stock alerts, it is showing same website and stock where customer account is created.

Additional information

• product_alert_stock table have correct website and store data and it is sending emails from correct store but product edit page shows wrong data.

• Collection which used to show data on product edit page is using website_id from customer_entity table instead of product_alert_stock.

• https://github.com/magento/magento2/blob/2.4.8-p1/app/code/Magento/ProductAlert/Model/ResourceModel/Stock/Customer/Collection.php

• https://github.com/magento/inventory/blob/develop/InventoryProductAlert/Block/Adminhtml/Product/Edit/Tab/Alerts/Stock.php#L70

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 @hiren-gujarati. 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.

• 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

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

[engcom-Bravo]

Hi @hiren-gujarati,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.Kindly refer the screenshots.

For all the website's stock alerts, it is showing same website and stock where customer account is created.

Hence Confirming the issue.

Thanks.