A wrong price went live on a booking site: stop, correct and answer the guests who booked

A wrong hotel price on booking site channels is usually a distribution problem: the channel manager, the tool that pushes rates and availability to every sales channel, sent a number nobody approved. Close sales first, correct the rate at source, recheck each channel, list the bookings made at the wrong price, then decide each case and write to the guest.

For example: a revenue manager opens a booking site on a Tuesday morning and sees a sea-view double at a tenth of its price. The first reservations at that rate arrive before anyone has finished reading the screen. This article is the sequence for that morning: stop the sale, correct the rate, count the bookings, decide about each one, write to the guests, and then put controls in place so the next error stops earlier.

What should you do in the first ten minutes after spotting a wrong price?#

Stop the sale first and diagnose second. Every minute the wrong rate stays open adds bookings you will have to handle one by one.

Before acting, name the fault precisely: which rate plan, which date range, and whether it appears on one channel or on all of them. A single-channel error and a system-wide error need different first moves. If the wrong price is everywhere, the source is probably your own system or the channel manager; if it is on one channel only, the mapping or the channel's own copy is the likelier suspect.

Close the affected rate plan rather than the room type. Closing the room type also blocks the correct rates for the same dates, which turns one problem into two. Do not delete the rate plan or the room type to hide the price: deletion can break the mapping between your system and the channel, and a broken mapping can take the room off sale for the correct rates too.

Send one message to the front desk and the reservations desk: which rate is closed, for which dates, and that any quote for those dates must be checked by hand until further notice. Write down the time you spotted the error and the time sales were closed. That pair of timestamps is the spine of every later conversation with the channel and with the guest. If the error exists only on your own website, the order is the same: close the rate, then fix it. To understand why the wrong number reached the channel at all, read how a channel manager connection works: messages, delays and errors.

How do you correct the rate and prove every channel took it?#

Correct the rate where it is defined, push it out, and then look at each channel the way a guest would, on a future date.

Fix the rate in your own system, not in each channel's extranet. An extranet edit is a copy, and the next push from your system can overwrite it with the old number again. Push a full refresh of the affected dates and rate plans rather than a single edit, and expect a propagation delay: a channel can keep showing the old price for a while after the push.

Search as a guest would: a private browser window, two adults, a test date at least a month out, and the exact room and board combination that was wrong. Check each channel type separately, because they fail separately: your own booking engine, the booking sites, travel agency portals, and any metasearch feed that copies your rates. Recheck after an hour and again the next morning, since cached pages and third-party copies can reappear after a correction that looked complete. Keep a screenshot with the date and time of every check: it is the only proof you will have that the correction actually reached the channel.

The mapping between rate plans, room types and channels is where most of these errors start, so it is worth reading channel manager mapping: room types, rate plans and testing before your next bulk update.

Which bookings were made at the wrong price?#

Pull every reservation created between the moment the wrong rate went live and the moment sales closed, and filter by rate plan code rather than from memory.

Build the list from two places: each channel's own reservation report and your own system. The two lists rarely match exactly, and the gap is where disputes come from. Filter by rate plan code and by the time the booking was created, not by arrival date: a booking made in the bad window can be for next spring.

Record per booking: channel, booking reference, guest name, arrival and departure, room and board, amount paid or payable, and the cancellation terms the guest was shown at the time of booking. Include bookings that were later modified or cancelled, because a cancelled booking at the wrong rate can still produce a complaint or a payment dispute. Work out the money at stake per booking, not as a single total, since each booking will be decided on its own facts.

Should you honor, adjust or cancel a booking made at the wrong price?#

There is no single right answer, and the choice is not only commercial: it depends on what the guest was shown, what the booking terms say and where the guest is.

Three practical options exist: honor the booking at the wrong price; honor it with a goodwill addition such as an upgrade or an extra; or ask the guest to accept a corrected price before arrival. Cancelling is a fourth option, but it is not a free move. The legal position depends on the specific terms shown to the guest, the channel's rules, and Turkish consumer protection regulations. Because the outcome varies by case, consult a legal adviser before cancelling a confirmed reservation.

Decide by rule, not by mood. Set a threshold in advance, for example a difference below which you honor without discussion, and apply it to every booking on the list the same way. Name the person or small group who decides, and put that name in the record, so the answer does not change from guest to guest. Read the cancellation terms the guest actually saw at the time of booking: those are the terms you will be measured against, not the ones in your current contract. Count the cost of the argument, not only the cost of the room: a public complaint, a payment dispute and a lost repeat guest are all costs, and they arrive later than the room cost.

For bookings made online, the starting point is the distance contract framework: see right of withdrawal and hotel bookings in Türkiye: what the distance contract rules say.

How do you write to a guest who booked at the wrong price?#

Write early, in plain words, say what happened and what you are offering, and never blame the guest or the software.

Send one message per booking, through the channel the guest used where the channel allows it, and by email as a record. Structure it in five lines: what happened, what it means for their booking, what you are offering, what happens next and by when, and who to reply to. Do not stop at "a system error": say which price was shown, which price applies, and whether the guest's amount will change. Vagueness reads as a negotiation tactic.

If you are honoring the booking, say so in the first line and confirm the price will not change. That single sentence removes most complaints before they start. If you are asking the guest to accept a change, give a real choice and a clear deadline, and say what happens if they do not reply. Log the message, its time and the guest's reply inside the booking, so the next person does not restart the conversation from the beginning. Write in the guest's language where you can: a translated apology reads as a procedure, while a short message in the guest's own language reads as a person.

What do you send to the booking site's support team?#

Send facts, not blame: the rate plan, the dates, the timestamps and the booking references, in one message per channel.

Open one ticket per channel rather than one per booking, and list the affected bookings inside it with their references. Include the property identifier, the rate plan code, the wrong price, the correct price, when the wrong price was first seen, when sales were closed and when the correction was pushed. Ask a specific question: whether the channel can waive cancellation charges on the affected bookings, and what evidence it needs from you to do so.

Do not settle for a verbal answer on the phone. Ask for the outcome to be written into the ticket, and keep the ticket number next to your booking list. Ask what the channel saw on its side: sometimes the wrong price came from the channel's own mapping or a promotion, not from your push, and the fix belongs to them. Treat every channel's rules as its own and subject to change, so nothing in your message should assume a policy; ask, and keep the written answer.

How do you prevent the next wrong price from going live?#

Two controls catch most rate errors: a limit on how far a rate can move without a second approval, and a second pair of eyes before any bulk change.

Set change limits so that a mistyped zero or a shifted decimal stops at the limit instead of reaching a channel. The limit is a number you choose, and it should be low enough to catch a factor of ten. Require two people for bulk work such as seasonal loads, currency changes and mass date updates: one person enters, the other checks the preview before anything is pushed. Preview the rate grid for the affected dates and room types before sending, and read the preview rather than clicking through it.

Keep a short list of future test dates and search them on every channel after any rate change. The same five dates every time make the check fast enough to actually happen. Run a weekly comparison of your own website and each channel for a handful of dates: small drift is normal, and catching it on a Tuesday is cheap. A fuller version of that routine is in rate parity check: a weekly routine for direct and OTA prices. Log every rate change with who made it, when, and from which screen, and check currency and decimals explicitly on every change: a wrong currency and a wrong decimal are the two errors that travel furthest before anyone notices.

What to do next#

Write the first-ten-minutes checklist before you need it. Name the person who closes sales, the person who decides about each affected booking, and the person who writes to the guest, and keep all three on one page. The article is one sequence: stop, correct, list, decide, write, learn. The last step is the one that decides how the next error feels.