UPSTREAM FIX
magento2-41030: Edit Item page shows the original price instead of the applicable tier price
Community fix magento2-41030 merged into magento/magento2 on 2026-10-07, not in a release yet; applies cleanly to 2.4.9.
Edit Item page shows the original price instead of the applicable tier price edited
- Pull request title
- Applicable tier price is not applied on the Edit Item page on page load and it is not recalculated after quantity changes from the minicart.
- Pull request
- magento/magento2#41030
- Issues
- #41027 human
- Author
- @dhruvi-prajapat1
- Merged
- 2026-10-07
- Fixed in
- no release yet
- Reported on
- —
- Categories
- Price/Tax
- Components
- magento/module-catalog, magento/module-checkout
Labels
- Area
- Pricing
- Component
- Pricing
- Priority
- P2
- Severity
- —
- Reported on (labels)
- 2.4.x
Issue
Title and steps come from the upstream issue and pull request.
Description
- When opening the Edit Item page displays the original product price instead of the applicable tier price.
- When the quantity is updated from the minicart, the quantity is synchronized with the Edit Item page, but the displayed product price is not recalculated and continues to show the original price instead of the applicable tier price.
- When the quantity is updated from the minicart, the quantity is synchronized with the Edit Item page, but the displayed product price is not recalculated and continues to show the original price instead of the applicable tier price.
Steps to reproduce
1. Take 2.4-developer branch clone.
2. Create a product and configure tier pricing (for example, set a fixed price of 20 for a quantity of 2),as shown in Screenshot 2.
3. Open the product on the storefront and add 3 qty to the cart.
4. Open the Edit Item page from the minicart (Screenshot 1).
5. Observe that:
- The quantity is displayed as 3.
- The product price is displayed as 100 instead of the applicable tier price 20. (ScreenShot-3)
6. While remaining on the Edit Item page, open the minicart and update the quantity from 3 to 4 (Screenshot 4).
7. Observe that:
- The updated quantity is correctly reflected on the Edit Item page.
- The displayed product price remains 100 instead of being recalculated to the applicable tier price 20.
2. Create a product and configure tier pricing (for example, set a fixed price of 20 for a quantity of 2),as shown in Screenshot 2.
3. Open the product on the storefront and add 3 qty to the cart.
4. Open the Edit Item page from the minicart (Screenshot 1).
5. Observe that:
- The quantity is displayed as 3.
- The product price is displayed as 100 instead of the applicable tier price 20. (ScreenShot-3)
6. While remaining on the Edit Item page, open the minicart and update the quantity from 3 to 4 (Screenshot 4).
7. Observe that:
- The updated quantity is correctly reflected on the Edit Item page.
- The displayed product price remains 100 instead of being recalculated to the applicable tier price 20.
Expected result
- When opening the Edit Item page for a cart item with an applicable tier price, the page should display the tier price instead of the original product price.
- When the product quantity is updated from the minicart and the change is synchronized with the Edit Item page, the product price should be recalculated and display the applicable tier price.
- When the product quantity is updated from the minicart and the change is synchronized with the Edit Item page, the product price should be recalculated and display the applicable tier price.
Actual result
- When opening the Edit Item page displays the original product price instead of the applicable tier price.
- When the quantity is updated from the minicart, the quantity is synchronized with the Edit Item page, but the displayed product price is not recalculated and continues to show the original price instead of the applicable tier price.
- When the quantity is updated from the minicart, the quantity is synchronized with the Edit Item page, but the displayed product price is not recalculated and continues to show the original price instead of the applicable tier price.
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.
| Line | Code match per tag | Tests |
|---|---|---|
| 2.4.6 | 2.4.6 conflict 2.4.6-p1 conflict 2.4.6-p2 conflict 2.4.6-p3 conflict 2.4.6-p4 conflict 2.4.6-p5 conflict 2.4.6-p6 conflict 2.4.6-p7 conflict 2.4.6-p8 conflict 2.4.6-p9 conflict 2.4.6-p10 conflict 2.4.6-p11 conflict 2.4.6-p12 conflict 2.4.6-p13 conflict 2.4.6-p14 conflict 2.4.6-p15 conflict | 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 conflict 2.4.7-p1 conflict 2.4.7-p2 conflict 2.4.7-p3 conflict 2.4.7-p4 conflict 2.4.7-p5 conflict 2.4.7-p6 conflict 2.4.7-p7 conflict 2.4.7-p8 conflict 2.4.7-p9 conflict 2.4.7-p10 conflict | 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: no test data |
| 2.4.8 | 2.4.8 conflict 2.4.8-p1 conflict 2.4.8-p2 conflict 2.4.8-p3 conflict 2.4.8-p4 conflict 2.4.8-p5 conflict | 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: no test data |
| 2.4.9 | 2.4.9 clean | 2.4.9: no test data |
Triage
Model @cf/cloudflare/clef. Probability this is a bug fix: 97.8%. Probability it is security relevant: 0.6%.
Show the model's answers and probabilities
| Question | Answer | Probabilities | Confidence |
|---|---|---|---|
| Change kind | bugfix | bugfix 95.6%, refactor 1.5%, cleanup 1.0%, tests_only 0.8%, feature 0.5%, dependency 0.3%, docs_only 0.3% | 90.0% |
| Area | checkout | checkout 55.2%, frontend 36.2%, catalog 4.8% | 35.9% |
| Reported version | unspecified | unspecified 40.1%, 2.4.9 1.6%, 2.4.8 1.4% | 15.6% |
| Scope | 1.13 of 2 | 1 57.0%, 2 28.1%, 0 14.9% | 13.9% |
| Risk | 1.17 of 2 | 2 40.1%, 1 36.4%, 0 23.5% | 2.3% |
| Worth backporting | 1.43 of 2 | 2 56.9%, 1 29.1%, 0 14.0% | 14.3% |
Download
For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-41030/ 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.
Bundle README (what the ZIP ships)
# magento2-41030 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/41030 Issue: https://github.com/magento/magento2/issues/41027 Author: @dhruvi-prajapat1 Source commit: be1199b9c802a602b5a1cb22890aa0a027190c1e 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.
