Incorrect currency format
Change the store to EU currency
For the Euro currency, Shopify is currently displaying the price in the wrong format.
It’s showing €2.750,00 instead of the expected format €2,750.00.
However, on the cart page the correct format is displayed
Bug report
Shopify app dev here. Worth trying this before going any further:
1.From your Shopify admin, go to Settings.
2.Click General.
3.In the Store defaults section, click Horizontal menu, and then click Change currency formatting.
4.In each of the fields, replace {{amount}} with the currency format that you want to use from the options table.
5.Click Save.
| Money format | Rounded | Example |
|---|
{{ amount }} |
1,134.65 | |
|---|---|---|
{{ amount_no_decimals }} |
✓ | 1,135 |
{{ amount_with_comma_separator }} |
1.134,65 | |
{{ amount_no_decimals_with_comma_separator }} |
✓ | 1.135 |
{{ amount_with_apostrophe_separator }} |
1’134.65 | |
{{ amount_no_decimals_with_space_separator }} |
✓ | 1 135 |
{{ amount_with_space_separator }} |
1 134,65 | |
{{ amount_with_period_and_space_separator }} |
1 134.65 |
If it doesn’t work, I can suggest the next steps.
Hey @Van_Duong - @FundamentalApps is on point here. This likely expected.
EUR doesn’t have one universal separator format: €2.499,00 is common in many European regions, while €2,499.00 is common in English regional formats. For the store’s base currency, the theme uses the configured HTML money format, so {{ amount_with_comma_separator }} will produce 2.499,00.
I’d first follow the steps @FundamentalApps shared and check Settings > General > Store defaults > Change currency formatting. If you want 2,499.00, the amount placeholder should use {{ amount }} instead.
The screenshots also appear to compare the theme’s cart drawer with checkout, which can format amounts separately based on the buyer’s regional context. If changing the setting doesn’t help, could you share the active market/locale and confirm whether EUR is the store’s base currency? Let me know if I can clarify anything on our end here.
Hi @Alan_G and @FundamentalApps Thanks for the response. It was good to get confirmation that this was the intended behaviour.
No worries @Van_Duong - I’m going to mark this thread as solved for now with @FundamentalApps’s reply, but let me know if I can help out with anything else 
