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?