# Multi Currency pricing

**URL:** <https://community.hubspot.com/t/multi-currency-pricing/132611>\
**Category:** Tips, Tricks & Best Practices\
**Tags:** best-practices\
**Created:** [May 13, 2025, 11:39am UTC](https://community.hubspot.com/t/multi-currency-pricing/132611 "2025-05-13T11:39:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![galvanA81](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@galvanA81](https://community.hubspot.com/u/galvanA81)\
**Post date:** [May 13, 2025, 11:39am UTC](https://community.hubspot.com/t/multi-currency-pricing/132611/1 "2025-05-13T11:39:36Z")

</div>

Hello all,

We have the following situation in our company:

- We use 1 HubSpot portal for all our branches (different countries and continents)
- We sell our products in several currencies
- Even if the same currency is used in two countries there can be price differences

Because how Hubspot works, you can have different prices in different currencies, however for 1 product you can’t have Price in Euros for Italy and Price in Euros Spain. Because of this we have created Product Properties like “Price EUR Spain” and so on.

I would like to know what are some disadvantages of doing this, since I am aware that the Product Properties for Prices are set automatically by HubSpot for every “Currency” you add in your Account Settings, so I dont know if these properties have some backend use that we are not aware of

---

<div class="post-metadata">

**Author:** ![RubenBurdin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rubenburdin/32/75212_2.png) [@RubenBurdin](https://community.hubspot.com/u/RubenBurdin)\
**Post date:** [May 13, 2025, 4:24pm UTC](https://community.hubspot.com/t/multi-currency-pricing/132611/2 "2025-05-13T16:24:31Z")

</div>

## Hello @galvanA81

This answer of the community might help: [https://community.hubspot.com/t5/CRM/Different-currencies-for-the-same-product/m-p/181468](https://community.hubspot.com/t5/CRM/Different-currencies-for-the-same-product/m-p/181468)?

Hope it helps.

---

<div class="post-metadata">

**Author:** ![galvanA81](https://avatars.discourse-cdn.com/v4/letter/g/e9a140/32.png) [@galvanA81](https://community.hubspot.com/u/galvanA81)\
**Post date:** [May 13, 2025, 4:36pm UTC](https://community.hubspot.com/t/multi-currency-pricing/132611/3 "2025-05-13T16:36:27Z")

</div>

Not really 😞

That post talks about multi-currencies which is something already provided by HubSpot, the problem is that it only generates one “Price” property per Currency added into your Account. We need to have multiple “Price” properties for the same Currency.

---

<div class="post-metadata">

**Author:** ![SanjayKumar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sanjaykumar/32/16943_2.png) [@SanjayKumar](https://community.hubspot.com/u/SanjayKumar)\
**Post date:** [May 14, 2025, 5:47am UTC](https://community.hubspot.com/t/multi-currency-pricing/132611/4 "2025-05-14T05:47:51Z")

</div>

Hello @galvanA81

You’re correct HubSpot automatically creates price fields for each currency added in Account Settings. Using custom product properties like “Price EUR Spain” bypasses this system, meaning HubSpot’s backend logic (such as currency conversion, quoting, and revenue reporting) won’t apply to those fields.  
This can complicate reporting, workflows, and integrations as your setup scales.

Thanks!

---

<div class="post-metadata">

**Author:** ![victoriajohn4](https://avatars.discourse-cdn.com/v4/letter/v/2bfe46/32.png) [@victoriajohn4](https://community.hubspot.com/u/victoriajohn4)\
**Post date:** [May 14, 2025, 8:05pm UTC](https://community.hubspot.com/t/multi-currency-pricing/132611/5 "2025-05-14T20:05:05Z")

</div>

Using custom product properties like “Price EUR Spain” can work short term, but it does limit scalability and makes reporting or syncing with other tools more complex. We ran into similar friction with workflows and quotes not recognizing those custom fields 주소월드 .