Part of Website and builder
One pricing currency, many display currencies
Most Nepal operators price in US dollars, because that is what agents abroad and repeat clients expect. A German couple still thinks in euros and an Australian group in Australian dollars, and some of them leave to do the sum elsewhere. TripNerve keeps your prices in the one currency you set in company settings ("Price trips in") and shows them on your website in the visitor's currency.
In the website's Currency panel you choose which currency prices show in before a visitor picks one, whether to match the visitor's currency, whether the header has a currency menu, and which currencies to offer. There are 33 to choose from, among them USD, EUR, GBP, AUD, CAD, NZD, CHF, INR, NPR, CNY, JPY, KRW, SGD, AED, SEK and ZAR. A new site offers USD, EUR, GBP, AUD, CAD and INR.
- Matching uses the visitor's browser time zone and language
- Your own currency, and any currency a trip has its own price in, are always offered
- Rates are refreshed every day; converted prices drop the cents
Your own price where a conversion is wrong
A straight conversion isn't always the price you want. Indian travellers are a large market for Nepal treks and often expect a rupee price set for them, and some operators keep a separate euro price for European agents. On a trip's price you can add a price in another currency, with a compare-at price if you show a discount. A departure can carry its own currency prices too, for a single date that sells differently.
A price you set by hand is used as it is, never converted. If the trip has group prices in your own currency, a hand-set currency price scales by the same share for a group of that size.
What travellers book in
Exchange rates move, and a price quoted from a rate is an estimate. So a booking request is made in a currency only when you set the price in that currency. When the visitor is looking at a converted price, the booking form tells them: it was converted at today's rate, and they book in your currency, with the amount shown. Nobody is surprised by a different number in your confirmation email.
TripNerve doesn't take or record payments. You confirm the booking and take payment the way you already do, such as by bank transfer, in the currency the booking was made in.
Worked example
One Everest trip, four kinds of visitor
Mero Himal Treks prices its 14-day Everest Base Camp Trek at USD 1,450 a person, or USD 1,300 each for 4 or more. It sets INR 115,000 by hand for Indian travellers. On the day below the rates are 0.86 EUR, 0.76 GBP and 1.54 AUD to the dollar.
| Visitor | Sees | Books in |
|---|---|---|
| Couple in Munich | EUR 1,247 (converted) | USD 1,450 each, told on the form |
| Walker in Leeds | GBP 1,102 (converted) | USD 1,450, told on the form |
| Group of 4 from Pune | INR 103,103 each (your price, group share) | INR |
| Agent in Kathmandu | USD 1,450, switched with the menu | USD |
The Munich couple's browser is set to the Europe/Berlin time zone, so the site opens in euros: 1,450 × 0.86 is 1,247. When they send a booking request, the form says the price was converted at today's rate and that they book in USD: USD 2,900 for two.
The group from Pune sees rupees because INR is offered and their time zone is Asia/Kolkata. The rupee price was set by hand, so it stays INR 115,000 for one traveller. For four, the group price is USD 1,300, which is 89.7% of USD 1,450, so each pays INR 115,000 × 1,300 ÷ 1,450, or INR 103,103, and the booking is made in rupees.
Common mistakes
Offering every currency
A menu of 33 currencies is hard to scan. Offer the 5 or 6 your travellers actually come from.
Quoting a converted price as final
Converted prices move with the rate. Confirm in the currency the booking was made in, as the booking form tells the traveller.
Forgetting hand-set prices after a price change
A rupee price you set doesn't follow a later USD increase. Review your currency prices when you change the main price.

