What is a fallback message?
We send fallback messages any time your system fails to pick up a new reservation, modification or cancellation message. In each case, your system has a maximum of 30 minutes to pick up the new messages, and if it doesn’t, we’ll send you a fallback message via email.
So sometimes, instead of receiving an XML message as normal, you might get a fallback message.
Please note that we don’t push reservations to your interface or let you know when reservations come in. Instead, in order to avoid fallbacks, overbookings and pricing mismatches, we recommend that you configure your system to pull messages every minute – or more frequently if your system can manage it.
If you have any questions about why we don’t push reservation messages, we recommend that you get in touch with your Partner Business Manager.
What other factors can cause a reservation not to be received via XML?
Fallbacks aren’t the only reason you may not receive your reservations through XML. Here are some others:
- Non-XML rates: it’s possible to configure rates as non-XML, on request. We recommend you check if the rate in question has been configured as a non-XML rate.
- Mapping error: we recommend you check that the rooms and rates were correctly mapped before the reservation was made.
- Connection not confirmed: errors can also arise when properties aren’t correctly connected to your system. We recommend you check if the connection was enabled before the reservation was made.
- Enqueuing not enabled for modifications/cancellations: if the message you’re looking for is related to a modification or cancellation, we recommend you check if modifications and cancellations were enqueued.