1 April 2026
When the booking engine and the desk disagree
Stop-sells, child policies, and packages often exist in three places. Guests see one version; the clerk reconstructs another.
A reservations manager in Selangor can spend an afternoon rebuilding bookings that ‘came in wrong’. The engine showed a family rate. The channel stripped the extra-bed. The PMS landed a rack rate with a note in Chinese that nobody on the evening shift can read.
We do not treat this as a training issue first. We print the guest-facing page, the channel extra, and the PMS reservation side by side. The mismatch is usually a mapping: child age bands, a package that exists only on brand.com, or a restriction that the channel manager cannot send.
Stop-sells fail in a particular way. The revenue manager closes a date at 16:00. The engine honours it. One OTA remains open until the next pull, which might be forty minutes. In that window a booking arrives, and the desk is told to ‘just take it’. The audit question is not whether the team is helpful. It is whether the property knows that window exists and who owns it.
Cancellation rules deserve the same treatment. If the engine says 48 hours and the channel says 24, the clerk will follow whichever screen is open. We ask them to show us both, then we write the operational rule the property actually uses — which is often neither.