magento2-36878: Quote item price stored in the base currency on another currency store
Community fix magento2-36878 merged into magento/magento2 on 2025-07-02, released in 2.4.9; applies cleanly to 33 releases from 2.4.6 to 2.4.8-p5.
Fixes quote item price stored in the base currency on another currency store edited
- Pull request title
- Set price on quote item instead of base_price
- Pull request
- magento/magento2#36878
- Issues
- #38094 pr-derived
- Author
- @hostep
- Merged
- 2025-07-02
- Fixed in
- 2.4.9
- Reported on
- —
- Categories
- Shopping Cart
- Components
- magento/module-checkout, magento/module-tax
Labels
- Area
- Cart & Checkout
- Component
- DB, Frontend
- Priority
- P2
- Severity
- —
- Reported on (labels)
- 2.4.x
Issue
Title and steps come from the upstream issue and pull request.
Description
Which means that if you have multiple currencies in one website on the frontend, both price & base_price are stored in the database in the base currency. We would expect the price to be in the other currency and not the base currency.
Steps to reproduce
2. Configure "Stores > Configuration > General > Currency Setup" so that one of the 2 storeviews use different currency then the "default" values
3. Check in backoffice under "Stores > Currency > Currency Rates" that the 2 currencies aren't exactly the same rate, if they are the same, manually add some dummy exchange rate
4. Create a new product, give it a price of 100
5. Reindex, flush caches
6. In frontend, visit the product on the 2 different storeviews, you should see 2 different prices and currencies if all goes well.
7. On the storeview where the currency isn't the same as the "default" value, put the product in the cart
8. Now inspect the database, the table
quote_item, the columns price and base_price9. It's expected that the values aren't the same, the
base_price should contain 100, the price should contain the value from the other currency.Taken from the upstream pull request.
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 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: no test data |
| 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: no test data |
| 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: 96.9%. Probability it is security relevant: 0.7%.
Show the model's answers and probabilities
| Question | Answer | Probabilities | Confidence |
|---|---|---|---|
| Change kind | bugfix | bugfix 97.5%, refactor 1.0%, tests_only 0.4%, feature 0.4%, docs_only 0.4%, dependency 0.3% | 94.1% |
| Area | checkout | checkout 93.9%, frontend 1.6%, other 1.1% | 86.6% |
| Reported version | unspecified | unspecified 25.3%, 2.4.6 2.9%, 2.4.9 1.9% | 6.1% |
| Scope | 0.65 of 2 | 0 48.9%, 1 37.0%, 2 14.2% | 9.3% |
| Risk | 1.39 of 2 | 2 61.4%, 0 22.3%, 1 16.3% | 18.0% |
| Worth backporting | 1.35 of 2 | 2 47.6%, 1 40.3%, 0 12.1% | 10.5% |
Download
For cweagans/composer-patches, choose a version below and download the bundle. Copy its magento2-36878/ 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-36878 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/36878 Issue: https://github.com/magento/magento2/issues/38094 Author: @hostep Source commit: 203f2c21adce0e12d39170b18e066392a733c82d 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.
