Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

As explained in the "Understanding the data model" chapter in the beginning of this documentation, the room availabilities in Hotel-Spider are managed on room type level and not per product. However, should the system of an online booking system manage availabilities on product level, then the Hotel-Spider system will transmit splitted availabilities.

 

Re-use of previous implementations

Aware that establishing and maintaining interfaces with multiple providers can be time-consuming, the Hotel-Spider system disposes of multiple methods to interface with on online booking system.

Should an OTA interface with a competitor and/or partner of Hotel-Spider already have been implemented, then it should be easy to re-use that code for interfacing with the Hotel-Spider system.

On the other hand, once an interface with the Hotel-Spider system has been developped, it can quite certainly be re-used to connect with our competitors and/or partners.

 

Precisely for the reason described above, the Hotel-Spider has two distinct methods to request/retrieve the room type and rate plan structure:

  • Transmitting room availabilities based on OTA_HotelInvCountNotifRQ / OTA_HotelInvCountNotifRS
  • Transmitting room availabilities based on OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS

 

  • No labels