A hotel booking is a promise made in several systems at once. The property management system holds the room and the guest record, the channel manager holds availability, the booking engine takes direct reservations, the payment provider holds the authorisation, and the front desk holds the practical reality of who is arriving tonight. When one of those systems disagrees, the guest experiences it at the worst possible moment.
Many booking failures are not mysterious. They are state mismatches: one system changed, another did not, or a message arrived twice. This troubleshooting guide works from the symptom a manager can observe, through the likely cause, to a fix and a prevention control. Use it after an incident, and use the weekly routine to stop the same incident returning.
Symptom 1: the hotel is overbooked after an online sale
Likely cause: availability was sold on a channel before the channel manager pushed the reduction to the other channels, or the property uses pooled inventory that does not map to individual room types. A manual block placed at the front desk may never reach the online channels.
Fix: stop selling the affected room type, contact the guest with a clear relocation or upgrade option, and record the cost and cause. Reconcile the reservation timestamps across the PMS, channel manager and channel extranet.
Prevention: keep a small protected buffer for the room types most exposed to late sales, confirm near-real-time synchronisation in the contract, and run a daily availability comparison between the PMS and each active channel.
Symptom 2: the rate on one channel does not match the others
Likely cause: a rate plan is mapped to the wrong code, taxes and service charges are included in one channel and excluded in another, or currency rounding produces a different displayed price.
Fix: pause the affected rate plan, correct the mapping, and document the correct treatment of taxes, fees and inclusions. Check a test booking end to end, not only the rate screen.
Prevention: maintain a rate-plan matrix with one owner, test every new plan on every channel before activation, and review parity at a fixed time each week.
Symptom 3: the booking is confirmed but the payment is missing
Likely cause: the authorisation expired before capture, the payment callback was lost, the guest abandoned a redirect, or the booking was created from a channel that settles later.
Fix: locate the payment reference, check the provider dashboard and the callback log, and decide within the property's stated hold period whether to capture, request new payment or release the room. Do not mark the booking as paid on the basis of a guest screenshot alone.
Prevention: reconcile booking status against payment status at least daily, use idempotent callbacks so a repeated notification cannot double-charge, and define a written policy for expired authorisations and no-shows.
Symptom 4: the guest arrives and the reservation cannot be found
Likely cause: the guest booked under a different name, the channel reference was stored in a free-text field, the arrival date shifted because of a time-zone difference, or a duplicate profile was merged incorrectly.
Fix: search by channel reference, email, phone, arrival date and surname before creating a new booking. Check whether the reservation sits in a cancelled or no-show state. Record the root cause in the guest profile.
Prevention: store a canonical booking identifier and the channel reference as separate indexed fields, standardise date handling at property local time, and prevent duplicate profile creation at the front desk.
Symptom 5: confirmation or arrival messages are missing
Likely cause: the message template failed, the trigger did not fire because a status was set manually, or the guest's number was stored in an invalid format.
Fix: resend the confirmation from the PMS, check the message log for the booking, and verify the guest contact details. For international guests, confirm the country code before resending.
Prevention: monitor failed messages as an operational queue, use a fallback email when a mobile number fails, and test templates whenever a booking status or channel changes.
Symptom 6: the night audit does not reconcile
Likely cause: manual room moves, late refunds, no-show charges, tax or service charges handled outside the PMS, or a payment captured in one period and posted in another.
Fix: list every adjustment made after the close started, match each to an approval and a receipt, and post corrections with a reason code. Do not force the balance by editing the opening figure.
Prevention: lock the business date during the audit, require a reason code for manual postings, and review the exception report before the manager signs the close.
Diagnostic sequence for any booking incident
- Preserve the evidence. Copy the reservation record, channel notification, payment reference and message log before anyone edits them.
- Establish the timeline. Use one time zone and record when each system received and changed the booking.
- Identify the system of record. Decide whether the PMS, the channel or the payment provider is authoritative for the fact in dispute.
- Check for duplicates. Look for repeated callbacks, repeated reservations and duplicate guest profiles.
- Replay the failing step in a test booking. Never test with a live guest record.
- Fix the immediate guest problem first. The root-cause review can wait until the guest has a room and a clear answer.
- Record the cause and the control. Add the case to the weekly reconciliation checklist.
The weekly control routine
- Daily: compare availability by room type, review unapplied payments, clear failed messages and check arrivals with special requests.
- Weekly: test rate parity across active channels, review overbookings and relocations, inspect manual postings, and confirm that the channel manager is syncing.
- Monthly: reconcile refunds and no-show charges, review user access for front desk and reservations, test a restore of the booking database, and update the incident log.
What to fix first
Rank each issue by guest impact and frequency. An overbooking that happens once a month but displaces a family at midnight deserves attention before a cosmetic rate display issue. A payment mismatch that affects many bookings but is caught before arrival is still important because it consumes staff time and creates refund risk. Fix the highest-impact, highest-frequency combination first, then the low-frequency but severe failures such as lost reservations or double charges.
When the software itself is the constraint
Some failures cannot be fixed by training. If the PMS cannot expose a stable booking identifier, if the channel manager has no retry or alerting, or if the payment integration cannot handle a repeated callback safely, the property is relying on manual vigilance to cover a design gap. Document the workaround, quantify the staff time it consumes, and include the integration requirement in the next software decision.
Booking and operations software work sits inside Custom Software & Integrations, including PMS, channel and payment integrations. The pricing page explains how an integration project is scoped. For the inventory side of the same problem, read what inventory synchronisation costs in Bangladesh.
Sources
- OpenTravel Alliance, hospitality data and messaging specifications, accessed 17 November 2026.
- Hospitality Technology Next Generation (HTNG), accessed 17 November 2026.
- PCI Security Standards Council, accessed 17 November 2026.
- RFC 9110, HTTP Semantics, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.