Magento 2's Multi-Currency Pricing Glitch: Unpacking the Percentage Tier Price Fix

Magento 2's Multi-Currency Pricing Glitch: Unpacking the Percentage Tier Price Fix

As e-commerce migration experts at Shopping Mover, we constantly monitor the Magento ecosystem for critical updates and insights that impact store performance and data integrity. A recent GitHub issue (automatically generated from a pull request) highlights a significant bug in Magento 2's core pricing logic, specifically affecting multi-currency websites utilizing percentage-based tier prices. Understanding such nuances is crucial for any merchant, especially those considering or undergoing a Magento migration.

The Core Problem: Currency Conversion Misapplied to Percentages

The issue, #41728, describes a scenario where Magento 2's price indexer incorrectly applied currency conversion rates to percentage-based tier prices. This meant that on websites where the base currency differed from the global default, a percentage discount—which should remain a fixed percentage regardless of currency—was scaled by the exchange rate. For instance, if a USD to EUR rate was 2, a 10% tier price could be indexed as a 20% discount on the EUR website.

This bug specifically targeted the

percentage_value

within the tier pricing mechanism. Fixed-amount tier prices were not affected, as their conversion is expected and necessary. The root cause was identified within the

BaseFinalPrice::getTierPriceExpressionForTable()

method, a critical component used by the price indexer, which was inadvertently applying the

cwd.rate

(currency website rate) to these percentage values.

Impact on Merchants and Data Integrity

For Magento 2 merchants operating multi-website, multi-currency stores, this bug could lead to significant pricing discrepancies and potential revenue loss. Imagine offering a 10% discount, only for it to be doubled to 20% on certain store views due to an exchange rate. This not only impacts profitability but also creates an inconsistent customer experience, potentially eroding trust.

During a Magento migration, such underlying data inconsistencies can be particularly problematic. Ensuring that pricing logic is sound and accurately transferred is paramount. Issues like this underscore the importance of thorough post-migration testing, especially for complex pricing structures and multi-currency setups.

The Solution: A Targeted Code Fix

The proposed solution, originating from the pull request that generated this issue, involves a precise modification to the price indexer's logic:

• The

  BaseFinalPrice::getTierPriceExpressionForTable()

  method is updated to no longer apply

  cwd.rate

  to

  percentage_value

  . Fixed-amount tier prices will continue to be converted correctly.
• An unnecessary inner

  ROUND(..., 4)

  operation is removed for

  percentage_value

  , as this value is already stored as

  decimal(5,2)

  , making the rounding redundant.
• For consistency, the same expression in the deprecated

  DefaultPrice

  class is also fixed, although it's no longer used by the price indexer.

The manual testing scenario provided in the issue offers a clear path for developers and merchants to verify the fix or identify if their store is affected:

1. Set Catalog Price Scope to *Website*.
2. Create a second website with EUR as its Base Currency and set USD→EUR rate to 2.
3. Create a simple product priced 100, assigned to both websites.
4. Add a tier price: All Websites, ALL GROUPS, qty 1, Discount 10%.
5. Reindex:

   bin/magento indexer:reindex catalog_product_price

6. Check the price index. Before the fix, the EUR website would show 80 (20% discount), while after, both would correctly show 90 (10% discount).

Conclusion for Magento Users and Developers

This issue highlights Magento's ongoing commitment to refining its core functionalities. For developers, it's a reminder of the intricate details involved in currency conversion and pricing logic within a complex e-commerce platform. For merchants, it reinforces the need to stay updated with official patches and to meticulously test pricing on all store views, especially after any significant platform updates or migrations.

At Shopping Mover, we emphasize that understanding such core system behaviors is vital for a successful Magento migration and for maintaining a healthy, accurate e-commerce store. This fix ensures that percentage-based discounts behave as expected, providing consistent pricing across all your multi-currency storefronts.