Recover Refused OTA Bookings from the Log
Recover refused OTA bookings: a rejected push is saved in full and can be applied from the log once you fix the cause, with nothing lost.
Never lose a booking to a setup slip. Say an OTA sends four reservations one morning and your hotel rejects all of them because a key changed at one end only. Rejections happen in every system — the question is whether the details survive.
What is saved
Every incoming request, accepted or not: full payload, time and reason. Even an unreadable message is stored, so you can read it later rather than lose it.
How to recover it
- Fix the cause, such as a key or hotel mapping.
- Apply the refused booking from the log.
It runs the same path as a live booking — guest matching, room allocation, pricing. The guest appears on your chart carrying the reference the OTA issued, and the log records the delayed import together with the user who ran it.
Food orders too?
Yes. In F&B Point of Sale, an aggregator order containing an item you haven't mapped is held back with that item named, saved complete, and goes through as soon as you map it.