Hotel Website Pricing: What Happens When the Rate Grows on the Way to Payment

Picture a guest landing on your homepage and seeing "Rooms from ₹4,999." In hotel website pricing, that first number does a lot of work. Before the guest has read a word about the property, it tells them roughly what kind of stay this is and whether it belongs on their shortlist.

Then they enter their dates. The ₹4,999 room is not available on a Saturday, so the cheapest option is now ₹6,200. They want breakfast, which takes it to ₹6,800. Two nights makes it ₹13,600. GST is added on the next screen. At payment, a small "convenience fee" appears. None of these steps is dishonest on its own, and every line can be explained. But the guest who arrived holding ₹4,999 in their head is now looking at a number nearly three times larger, and they reached it one surprise at a time.

This is the part of hotel website pricing that rarely comes up in a redesign. Owners discuss how rates look: font size, a "Best rate guaranteed" badge, where the "Book Now" button sits. Fewer ask a simpler question: how many times does the number change between the first screen and the payment screen, and what does the guest do each time it changes? On a hotel's own website, the answer matters more than most owners assume.

How a hotel rate grows on the way to payment

It helps to separate the two ways a price can rise during a booking.

The first is the guest's own choices. A weekend, a bigger room, a meal plan or a second night raises the price, and the guest knows why. Someone who chooses breakfast expects to pay for it.

The second is charges the guest did not choose and could not see coming: taxes added after the room is selected, a payment-gateway surcharge, a compulsory supplement on peak dates, an extra-adult charge that appears only once occupancy is entered. These feel like the price moving, rather than the stay changing.

Hotel booking engines tend to mix both, which makes the problem hard to see from the inside. Each increment has a reason the hotel understands. The guest only sees the total going up.

Regulators have a name for the second category. India's Central Consumer Protection Authority, in its Guidelines for Prevention and Regulation of Dark Patterns, 2023, defines drip pricing as a practice where "elements of prices are not revealed upfront or are revealed surreptitiously within the user experience," among other forms. The guidelines apply to platforms systematically offering goods or services in India, as well as to advertisers and sellers.

I am not suggesting that every hotel adding GST at checkout is breaking the law; that depends on how and when charges are disclosed, and it is a question for your legal adviser. The useful point is that the regulator treats the pattern itself as a problem, separate from whether the final price was technically accurate.

What the research says about surprise costs

The most widely cited data comes from e-commerce rather than hotels, so read it with that limitation in mind. Baymard Institute's checkout research asks US online shoppers why they abandoned a purchase. After setting aside people who were "just browsing," the most common reason was "extra costs too high (shipping, tax, fees)," cited by 40% of respondents. A separate 12% said they abandoned because they "couldn't see / calculate total order cost up-front."

The first answer is about the size of the extra costs; the second is about not being able to see the total at all. A booking engine that shows a per-night, pre-tax rate for one room can produce both at once.

There is a more uncomfortable piece of evidence, and it deserves an honest hearing because it cuts the other way.

In 2015, the ticket marketplace StubHub ran a large randomised experiment. Half of its users saw prices with fees included from the first screen. The other half saw fees only at checkout. Economists Thomas Blake, Sarah Moshary, Kane Sweeney and Steven Tadelis analysed the results in a paper later published in Marketing Science, "Price Salience and Product Choice". Users who saw fees late spent about 21% more. They were more likely to buy, and they bought more expensive tickets.

So hiding the fees "worked" for StubHub, at least over the experiment period. A hotelier could fairly ask why they should show the full price early when a well-designed study suggests the opposite earns more.

Why your hotel booking engine is in a weaker position than StubHub

The same paper helps explain why that result is unlikely to carry over to your own site. The researchers' clickstream data showed how the users who saw fees late behaved. They were more likely to leave at checkout, the moment the fee first appeared. They went back to look at other listings more often, and when they did, they looked at cheaper tickets. The authors describe hidden fees as making price comparison difficult, which raises the cost of shopping around.

The important detail is where those users went back to: other listings on StubHub. The platform kept the customer even when the customer reconsidered. A hotel website does not have that safety net. When a guest is surprised by your total and decides to "check again," there is no second listing on your site for them to compare. The comparison happens in another tab, and that tab is often an OTA or Google. As our earlier piece on why guests book through OTAs explained, many guests already arrive on a hotel's website after seeing the property on an OTA. The surprise at your checkout sends them back to a familiar platform that already displays your property.

This is my interpretation rather than a tested finding. As far as I know, nobody has run the StubHub experiment on an independent hotel's booking engine. But the mechanism the paper documents, a price shock followed by re-comparison, is exactly the behaviour a hotel should least want to trigger on its own site.

One more detail from the paper: the effect was smaller among StubHub's most experienced users, and the authors suggest, cautiously, that price salience may matter most where people buy infrequently. Most guests book a given hotel once, or once a year at best. They have no memory of how your booking engine builds a price.

Google is already checking the number

There is also a practical reason to care, tied directly to direct bookings. If your hotel appears in Google's hotel results with your own website as a booking option (through Hotel Ads or free booking links, usually via your booking-engine or channel partner), Google checks whether the price on your site matches what it showed the guest. Its Price Accuracy Policy requires that the total price on the booking page is prominently displayed and matches the total shown on Google for the guest's dates and occupancy.

The accompanying Taxes and Fees Policy says the price must include all mandatory taxes and fees collected by the partner or the hotel, "regardless of when they're due," and explicitly prohibits lowering the base rate while raising taxes or fees to make the rate look cheaper. Outside the US and Canada, Google says it shows the total price, including taxes and fees, more prominently.

Google spells out the consequences of low accuracy: worse placement for ads and free booking links, and suspension for hotels whose prices are repeatedly wrong. A price that drifts between landing page and payment can cost you visibility, not only individual bookings.

The US has moved the same way through regulation. The Federal Trade Commission's Rule on Unfair or Deceptive Fees, effective May 12, 2025, covers hotels and requires the total price, including mandatory fees, to be shown more prominently than other pricing information. Government taxes may be left out of that figure but must be disclosed before the guest pays. Whether it applies to an Indian property selling to American guests is a legal question, but the direction is clear: the first price a guest sees should be close to the real one.

How the GST on hotel rooms makes pre-tax prices misleading

For Indian properties, one detail makes pre-tax display riskier than it looks. Since 22 September 2025, hotel accommodation with a value of supply up to ₹7,500 per unit per day attracts 5% GST without input tax credit, as the GST Council's FAQ and Finance Ministry clarifications reported by Business Standard confirm. Above ₹7,500, the rate is 18% with input tax credit, as this 2026 analysis of hospitality GST sets out.

Look at what that does to two rooms that appear almost identical when rates are shown before tax:

• ₹7,500 per night before GST: 5% GST, so ₹7,875 per night in total
• ₹7,600 per night before GST: 18% GST, so ₹8,968 per night in total

On a pre-tax rate card, these rooms look ₹100 apart. The real difference is about ₹1,093 per night. A guest who picks the ₹7,600 room as a small step up meets a much larger jump at the tax line, exactly the kind of late surprise the research links to abandonment.

The same analysis points out a second trap. Because the threshold is based on the value of supply for the unit, extra charges such as an extra bed count towards it. On its example, a ₹7,000 room with a ₹1,500 extra bed crosses ₹7,500 and attracts 18% on the whole amount. A family adding a third guest late in the flow can trigger a far larger tax line than the extra-bed charge suggested. Your CA should confirm how this applies to your rates, but the display lesson holds either way.

A tax-inclusive display, or at least a stay total on the room-selection screen that updates with occupancy, removes this trap. It also prompts a useful revenue conversation: whether a rate positioned just above the threshold is worth what it costs the guest.

What honest, stable pricing looks like on a hotel website

The goal is to keep the number stable once the guest has given you enough information to calculate it. That comes down to a handful of decisions.

Make "from" prices honest about what they include. If the homepage must show a starting price before dates are entered, label what it covers: which room, which meal plan, per night or per stay, and whether taxes are included. "From ₹4,999 per night, room only, incl. taxes" sets a very different expectation from a bare "₹4,999."

Pick one tax convention and keep it everywhere. Tax-inclusive or tax-exclusive, the homepage, room pages, booking engine, confirmation email and offers page should use the same convention. Switching conventions halfway through the journey does more damage than either convention on its own.

Show the stay total as soon as you can calculate it. Once the guest has entered dates and occupancy, the room-selection screen can show the total for the stay, with taxes, alongside the nightly rate. Waiting until the payment page wastes the moment when the guest is still comparing rooms and can adjust their choice.

Bring unavoidable charges forward. Extra-adult charges, compulsory dinners on festive dates, mandatory transfers and similar supplements belong on the room-selection screen when they apply to the guest's dates. If a payment-gateway fee cannot be avoided, consider absorbing it into the rate. A separately named surcharge at the last step is the most visible version of the problem.

Itemise, then total. A short breakdown of room rate, taxes and named fees, followed by one prominent total, is easier to trust than a number that changed without explanation.

Compare your breakdown with what appears elsewhere. Search your own property on Google and the OTAs you use, with the same dates and occupancy, and note how each displays the price. If your website looks more expensive at first glance only because it includes taxes others leave out, a simple "incl. all taxes" label does more than a discount.

One trade-off deserves an honest mention. A tax-inclusive price will sometimes look higher than a competitor's pre-tax rate at the top of the funnel, and some guests may leave before they understand why. That is a real cost. The guests who continue, though, are working from a number that will not change on them, at the step where they have invested the most effort. Which effect is larger for your property is something only your own data can tell you.

Price display is one of the things we check when we audit a site for Plading’s hotel website upgrade service, if you want an outside view of yours.

A ten-minute "price walk" you can run today

Before changing anything, record what is happening now. On your phone, start at your homepage and book a realistic stay: a weekend, two adults, a mid-range room, with breakfast. At every screen, write down the number shown and what it represents.

• Homepage or ad landing page: the first price shown, and its label
• Room page: the rate shown, whether it is per night or per stay, and whether it includes tax
• Booking engine, after entering dates: the rate for your dates, and whether a stay total appears
• After choosing room and meal plan: the new figure, and any supplements that appear
• Guest details: any new line items
• Payment: the final amount, and every line that was not on the previous screen

Then count the times the number rose for a reason you did not choose. If that count is zero or one, and the final amount appears before you are asked for card details, your pricing display is probably not the problem. If it is three or four, you have found a specific, fixable leak.

If your analytics allow it, check where guests drop off. A sharp fall between room selection and payment is consistent with late price surprises, though it can also reflect payment problems or a confusing form, so treat it as a lead, not proof.

The number is part of the promise

A hotel website makes several promises before a guest arrives: the room looks like the photographs, the location is as described. The price is the only one the guest can check before travelling, within minutes, on the same screen.

When that number holds steady from room page to payment, it says something about how the hotel operates, and the guest can finish the booking without opening another tab to check. When it keeps growing, even for good reasons, it gives them a reason to look somewhere else.

If you would like us to run this price walk on your site, along with the rest of the booking journey, you can request a free hotel website audit from Plading.

Sources

1. Central Consumer Protection Authority (India). Guidelines for Prevention and Regulation of Dark Patterns, 2023, notified November 30, 2023. Text of definitions as reported by Verdictum: verdictum.in
2. Baymard Institute. 50 Cart Abandonment Rate Statistics 2026 (reasons for abandonment survey), last updated September 22, 2025: baymard.com
3. Blake, T., Moshary, S., Sweeney, K., and Tadelis, S. Price Salience and Product Choice. NBER Working Paper 25186; published in Marketing Science (2021): nber.org
4. Google. Price Accuracy Policy, Hotel Center Help: support.google.com
5. Google. Taxes and Fees Policy, Hotel Center Help: support.google.com
6. US Federal Trade Commission. Rule on Unfair or Deceptive Fees, 16 CFR Part 464, effective May 12, 2025: ecfr.gov
7. Muchale, S. "GST on Hospitality Industry: Hotel Accommodation, Restaurant GST Rates, ITC & Rule 42 Reversal," TaxGuru, May 16, 2026: taxguru.in
8. Business Standard. "No ITC for hotel rooms up to Rs 7,500 under 5% GST, says FinMin," September 16, 2025: business-standard.com
9. GST Council. FAQs on GST rate changes effective 22 September 2025: gstcouncil.gov.in