UPSTREAM FIX

magento2-40431: Admin product alerts grid showing the wrong website

Community fix magento2-40431 merged into magento/magento2 on 2026-03-05, released in 2.4.9; applies cleanly to 33 releases from 2.4.6 to 2.4.8-p5.

Fixes the admin product alerts grid showing the wrong website edited

Pull request title
Product stock alert's website and stock mismatch issue for multi website
Pull request
magento/magento2#40431
Issues
#40027 human
Author
@KrasnoshchokBohdan
Merged
2026-03-05
Fixed in
2.4.9
Reported on
2.4.8-p1
Categories
Catalog/Product
Components
magento/module-product-alert

Labels

Area
Catalog
Component
ProductAlert
Priority
P2
Severity
—
Reported on (labels)
2.4.8-p1

Issue

Title and steps come from the upstream issue and pull request.

Description

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

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.

![Image](https://github.com/user-attachments/assets/fd6b9730-18bf-45a7-8a1f-ac3e724da538)

Actual result

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

![Image](https://github.com/user-attachments/assets/e63960f2-7216-4b49-9a6f-9e8480d57ed2)

Taken from the upstream issue.

Code match per tag

Each tag was checked with git apply --check against that tag's files. A clean match means the change applies; it is not a test result. Tags that already contain the fix are marked.

LineCode match per tagTests
2.4.6
2.4.6 clean 2.4.6-p1 clean 2.4.6-p2 clean 2.4.6-p3 clean 2.4.6-p4 clean 2.4.6-p5 clean 2.4.6-p6 clean 2.4.6-p7 clean 2.4.6-p8 clean 2.4.6-p9 clean 2.4.6-p10 clean 2.4.6-p11 clean 2.4.6-p12 clean 2.4.6-p13 clean 2.4.6-p14 clean 2.4.6-p15 clean
2.4.6: no test data 2.4.6-p1: no test data 2.4.6-p2: no test data 2.4.6-p3: no test data 2.4.6-p4: no test data 2.4.6-p5: no test data 2.4.6-p6: no test data 2.4.6-p7: no test data 2.4.6-p8: no test data 2.4.6-p9: no test data 2.4.6-p10: no test data 2.4.6-p11: no test data 2.4.6-p12: no test data 2.4.6-p13: no test data 2.4.6-p14: no test data 2.4.6-p15: no test data
2.4.7
2.4.7 clean 2.4.7-p1 clean 2.4.7-p2 clean 2.4.7-p3 clean 2.4.7-p4 clean 2.4.7-p5 clean 2.4.7-p6 clean 2.4.7-p7 clean 2.4.7-p8 clean 2.4.7-p9 clean 2.4.7-p10 clean
2.4.7: no test data 2.4.7-p1: no test data 2.4.7-p2: no test data 2.4.7-p3: no test data 2.4.7-p4: no test data 2.4.7-p5: no test data 2.4.7-p6: no test data 2.4.7-p7: no test data 2.4.7-p8: no test data 2.4.7-p9: no test data 2.4.7-p10: passes before and after (test does not cover the fix)integration: passes before and after
2.4.8
2.4.8 clean 2.4.8-p1 clean 2.4.8-p2 clean 2.4.8-p3 clean 2.4.8-p4 clean 2.4.8-p5 clean
2.4.8: no test data 2.4.8-p1: no test data 2.4.8-p2: no test data 2.4.8-p3: no test data 2.4.8-p4: no test data 2.4.8-p5: passes before and after (test does not cover the fix)integration: passes before and after
2.4.9
2.4.9 conflictcontains the fix
2.4.9: no test data

Triage

Model @cf/cloudflare/clef. Probability this is a bug fix: 97.7%. Probability it is security relevant: 0.6%.

Show the model's answers and probabilities
QuestionAnswerProbabilitiesConfidence
Change kindbugfixbugfix 96.4%, refactor 1.1%, tests_only 1.0%, feature 0.7%, dependency 0.4%, docs_only 0.4%91.5%
Areacatalogcatalog 47.9%, admin 41.9%, other 3.3%32.3%
Reported version2.4.8-p12.4.8-p1 61.1%, 2.4.8 3.2%, 2.4.8-p2 2.6%36.9%
Scope0.62 of 20 49.1%, 1 39.7%, 2 11.1%11.8%
Risk0.18 of 20 85.1%, 1 11.8%, 2 3.1%60.8%
Worth backporting1.57 of 22 66.5%, 1 24.0%, 0 9.5%26.4%

Download

For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-40431/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Test files are always removed; paths are relative to each package root, using the default -p1 level.

Packages (1): magento/module-product-alert
Bundle README (what the ZIP ships)
# magento2-40431

Community fix merged upstream into magento/magento2, adapted by magento.watch.
This is not a patch published by Adobe.

Pull request: https://github.com/magento/magento2/pull/40431
Issue: https://github.com/magento/magento2/issues/40027
Author: @KrasnoshchokBohdan
Source commit: 17dbf7a20845bca25fa351108a4b10ccc9425f91
Modifications: test files and documentation removed, paths rewritten relative to each Composer package.
Licence: OSL-3.0 / AFL-3.0, as the original Magento Open Source code.
Maintainer: Łukasz Bajsarowicz (@lbajsarowicz)

Licence: Magento Open Source code under OSL-3.0 and AFL-3.0. The bundle carries the original author, source commit and the list of modifications.

Sources

Łukasz Bajsarowicz
Built by

Łukasz Bajsarowicz, e-commerce architect

Magento and Adobe Commerce architecture, upgrades, performance and audits for merchants and agencies since 2015; magento.watch is the tooling I use on those projects.

Open source, maintained on weekends.