Why the right hotel at the wrong market rate costs an agency so much time
Hotels price by the market a guest comes from. When inventory does not carry that, a client is booked at the wrong rate and you spend days proving it. A real Mauritius case, and how to avoid it.
In this article
A hotel rate belongs to a market, not just a room. If your inventory does not say which market a rate is for, you can book the right hotel at the wrong price, and fixing it can take far longer than the booking did.
I saw this at one of India's largest online travel companies. The booking was for Mauritius. The API inventory we worked with carried no market-specific rates. A Japanese client who was working in Gurgaon was booked at Indian-market rates. Convincing the hotelier to put that right took an enormous amount of time and effort.
Nothing in the booking looked wrong. The hotel was right, the dates were right, the room was right. The rate was the only thing that was wrong, and nothing in the data said so.
What is a market-specific hotel rate?
Hotels often price the same room differently depending on the market the guest comes from. A rate meant for one market is not automatically valid for a guest from another.
That means the question "what is the rate?" is incomplete. The full question is "what is the rate, for which market, from which source?"
Why does this go wrong in agencies?
Because most systems only ask for the room, the dates and the price. The market is an unwritten assumption, and the assumption is usually the agency's own country.
In the case I dealt with, the client's nationality and where they were working did not match the market the rates were for. The inventory could not tell us, so the mistake was invisible until a person had to argue it with the hotel.
What does a mistake like this actually cost?
It costs time first. Days of back and forth with the hotelier, with a client waiting. Then it costs money: the price gap if you absorb it, or the goodwill if you pass it on. Neither shows up on the quote you sent.
This is the same point I keep coming back to. A number you cannot trace to a source is a number you will end up defending by hand.
How can a travel agency avoid it?
- Record which market every hotel rate is for, next to the rate.
- When a guest's nationality or country of residence differs from your agency's usual market, ask the supplier before you confirm, not after.
- Keep the evidence: the rate sheet or the supplier's written reply. If you ever need to argue with a hotelier, that is what you will use.
- Treat a rate with no stated market as unverified, however clean the booking looks.
This is why NAMA keeps rates tied to the sheets and sources they came from. The aim is that a quote can show where each number came from, so a question like "which market is this?" has an answer on the screen instead of in someone's memory.
Frequently asked questions
- What are market-specific hotel rates?
- Rates a hotel sets for guests from a particular market. The same room can be priced differently by market, so a rate is only valid for the market it was meant for.
- Why would a hotel API not show the market of a rate?
- Some inventory carries only room, date and price. In the case I handled, the API inventory carried no market-specific rates, so the mismatch was not visible in the data.
- What should I ask a hotel supplier when the guest's market differs from mine?
- Ask which rate applies to that guest's nationality or country of residence, and get the answer in writing before you confirm.
- How do I protect margin when a rate was booked for the wrong market?
- Keep the supplier's written rate terms with the booking. Without them, correcting the rate depends on persuasion, which takes time.
- Does NAMA store the market of a rate?
- NAMA is built so that quotes trace back to the rate sheets and sources they came from, which is where a rate's market should be recorded.
