Pricing and multiple currencies

I’ve been thinking a lot about pricing for my upcoming SaaS app lately and one of the issues I always come back to is currencies. I live in Europe and I’m targetting both European and US based customers.

Are there any best practices regarding which currencies to display on the pricing page? One option would be to pick one currency (for example USD) and use that for all pricing-related pages, and only convert to the users currency on checkout.
With this approach I’m a bit worried that the pricing would look “foreign” to people who use other currencies and this might affect their decision to buy.

Any thoughts?

We’ve been through this one. We’re in the UK and initially priced just in GBP - we used to show an indicative price in EUR and USD. We now have bank accounts and merchant IDs in all three so we chose to show the price in what we guess is the user’s currency and they can change it. We set the price for each currency as being a low value purchase we don’t lose or gain a huge amount to fluctuations.

If you are VAT registered it gets a bit tricky as you need to account for VAT in your registered currency (I’m assuming it is the same in other EU countries as in the UK) so we have to know the daily rate even though we don’t convert that day but pay into a dedicated account for that currency.

We have seen an upturn in American interest since we started to accept dollars, hard to ascertain if that is the only reason though.

We just use USD for everyone at the moment and it works great. Everyone in the world knows the dollar and they don’t have problems with it.

We accept both USD and EUR, both for our download edition as well as for SaaS subscriptions. We don’t really adjust the pricing based on the current exchange rate regularly though to keep it simple. If you are selling to a global audience and only want to accept a single currency, I would definitely pick USD and let customers / credit card company’s handle the exchange to their local currency.

For example, Europeans are really used to pay in USD for online services and it’s not an issue (even though we accept both USD and EUR and make this clear on our sign-up pages, our customers often pick USD even if they are from an eurozone country simply because most just don’t care).

Some customers might not be able to pay you if you don’t accept their local currency though (e.g. government agencies) so in a few cases we made exceptions and accepted GBP for larger orders.

That’s a broad sweeping statement. Also, not true.

2 Likes

Feel free to provide examples of how it’s not ture :slight_smile:
What i’m saying is that we’re selling world wide (from Chile to Japan) for years in USD only and haven’t had ONE single complaint about the currency.

Generally in reasoning, one has to prove that something IS true, not that something is NOT true. :slight_smile:

Our product is priced in EUR, USD, and GBP. Once every year or so I check the comparative values of the currency to make sure the prices are not too much out of alignment with each other.

We get told in those Marketing 101 books that we should price at, say $69, or $79, for some sort of psychological reason When the comparable price in EUR is €57.32, well, that doesn’t have quite the same effect.

But this is just my thought process. I’d love to see conclusions from someone who has tested a global USD price versus a few local currency prices, and has sufficient data to make a meaningful conclusion.

I don’t need to prove anything :slight_smile: i’m just sharing my experience and usually ignore one line trolling but if we really need to:


The only other currency that you might want to consider would be the Euro but outside of Europe avarage people don’t have a clue what it is.
Continents that know/use the USD regularly:
North America (ofcourse)
South America (alternate currency in a lot of countreis)
Australia (strong economic ties to the US)
Asia (might be problematic in a couple of areas, but you have larger problems selling to them then currency anyway. India, Japan, Russia - huge economies that ‘love’ the dollar).

The fact that the dollar is pretty much being raped by the FED at everyones expense is another discussion :slight_smile:
If you go down the route of selling in multiple currencies based on geo-location i think will generate more problems then benefits:

  • you’ll end up with selling cheaper to some if you use fixed rates for long periods of time, or you will have “dynamic” pricing - might look bad/strange to some customers (geo-location sometimes fails).
  • accounting issues
  • you’ll need to generate invoices in different currencies (might be a big problems in certain countries)

ps: i’m from Romania / Europe - no bias for the USD.

That is the approach I take. If someone can get it slightly cheaper by switching currency, they are happy because they got a discount and I’m happy becuase I got a sale. ;0)

2 Likes

You may not have intended it that way but the original chirp was a kinda one line troll, so I was just responding in kind! Anyways, thanks for breaking your thoughts out further… :smile:

I’ve worked at one stage for the worlds largest independent software company and I can tell you pricing in local currency made a massive difference to sales. Where we didn’t have local price lists (for example countries in the Eurozone not yet moved to Euro) we would frequently lose out to local competitors who did because their pricing was pegged to local inflation, not to global currency fluctuation.

This is especially problematic for SaaS because of the continuous nature of the payments. One a smaller scale and a more personal level I now live in South Africa and my company uses a bunch of USD priced and sold SaaS products (probably about $500 in total per month). Look at this chart:

I’m paying at least 20% more than we were 2 years ago and with some customer that becomes the difference between choosing a USD-based product and a local one. Conversely, if we were selling SaaS solutions in USD (we’re not yet) we’d be making 20% less.

1 Like

I’ve worked at one stage for the worlds largest independent software company and I can tell you pricing in local currency made a massive difference to sales.

Data! I like data when making business decisions. Thanks @imsickofmaps

In New Zealand (my home country, but not where I live) the currency is called the dollar and and the currency symbol is written as “$”. So when a website says a product is $79, we assume that this means 79 New Zealand dollars. And then you go to pay and find that the price has jumped at checkout to $94. 94 New Zealand dollars. D’oh! So you curse and go looking for an alternative.

These days we’re used to it, although not inured to it. It still leaves a sense of annoyance with the company.

Annnnnndddd, I’ve just realised that my own frickin’ product’s website is guilty of this.

@imsickofmaps Mike, that’s a valid argument. However you’re missing the context. I though we’re talking to/about boostrapped businesses/startups that don’t have a lot of resources. I fail to see how your example from a huge corporation applies to a business run by a couple of people with funding <500K usually.

@SteveMcLeod that’s an annyoing problem to have, maybe a text label on the pricing page that says it’s in USD? it also depends on where the majority of your customers are, it might be better to frustrate a couple of new zellanders than 100 of americans/french/indians/etc… (wait, the french will be pissed of because your site is not fully translated into french).

1 Like

it might be better to frustrate a couple of New Zealanders than 100 of
americans/french/indians/etc

Wikipedia tells me the following countries typically use the “$” sign in front of numbers in their local currency:

United States, Mexico, Australia, Argentina, New Zealand, Hong Kong, Pacific Island nations, and English-speaking Canada.

Even excluding the US, that’s a combined population of some 200 million or so, I guess. I think this fact is worth at least considering.

One’s conclusion might be, “ah heck, I’ll show it in USD anyway.” One’s conclusion might be, “Better put a ‘USD’ label there”. One’s conclusion might be, “Let’s auto-convert based on geo-location to what we think the user’s currency is”. One’s conclusion might be, “Let’s use geo-location to add a USD label if we think the user is in NZ, AU, AR, etc…” And depending on what you are selling and who you are selling it to, any of these conclusions are okay.

My current approach is to show “Buy now for $79” on the main product page. But once you click “Buy now”, I use FastSpring’s magic to auto-convert to the user’s probable currency, with dollar sign and currency TLA. eg. “$96.86 NZD”

I’m currently A/B testing a new product page that doesn’t show the price at all. To see the price the user will need to click on “Buy Now”.

I could go on all day on the topic of pricing in a global context…would love to see firm data from people who have tested this in various contexts. Where’s @patio11 when you need him, with his encyclopaedic knowledge of this stuff?

Showing the price after you click buy now is an interesting approach. In our app (Paymo) we issue invoices directly to each client for each transaction. How do you handle this with multiple currencies?

Our main product is desktop software that you pay for once (and then optionally for yearly upgrades). So the question is not really relevant, I think, if I understood correctly?

@SteveMcLeod In our case the system is automated and we generate a lot of invoices that go through cetain processes for our accounting firm and the state (for example EU/non-eu invoices need to be separated, EU invoices for companies in VIES don’t need to have VAT etc…). So what i’m saying is, do you have a system that handles this automatically for multiple curriencies? Do your customers get an invoice directly from you or from your payment processor?

Oh yes, we use FastSpring to handle everything in that area. A decision I made a few years ago, and a decision I’ve never regretted.

I put a little US flag next to the dollar price.