Currency Arbitrage: Why Booking the Same Hotel in Another Language Saves 8–12%

A little-known quirk of major OTAs: the rate displayed is not purely a function of the hotel. It is a function of the hotel, the currency, the display country, the detected locale, and the OTA's own regional markup model. Change any one of these variables and the price can move 8–12%.

Why this happens

OTAs run regional pricing engines. A user detected from New York pays a different markup than a user detected from Berlin — even on the same EUR-denominated hotel. The underlying net rate from the hotel is identical. The "display rate" is adjusted based on: willingness-to-pay data in the region, competing OTA prices shown on Google Hotels in that country, and FX conversion spread.

The typical pattern

• US-detected users pay the highest markup on European hotels (~5–9% over EU-detected users)
• UK-detected users pay mid-range on Mediterranean destinations
• In-country language often shows the cleanest rate (searching an Italian hotel in Italian, from Italy)
• USD-forced-display on European hotels typically carries a 1.5–3% FX spread over EUR-native booking

How to test it yourself

1. Search the hotel on Booking.com with your normal browser settings
2. Open a private/incognito window with locale set to the hotel's country (e.g. it-IT for an Italian hotel)
3. Set currency to the hotel's native currency
4. Compare. The delta is often €30–€80 on a 3-night stay

Where this breaks down

This arbitrage is effective on OTAs. It is not effective on the hotel's own site (which shows one rate globally) and it is not effective against bedbank/wholesale rates (which are set in a single B2B currency). The wholesale rate is almost always still lower than even the best currency-arbitraged OTA rate.

Vacayos automatically compares across currency and locale permutations, so you see the lowest version of the public rate before it compares against the wholesale floor.