Transmission of the prices
As explained in the "Room-based pricing vs Occupancy-based pricing" chapter in the beginning of this documentation, the prices in Hotel-Spider can either be managed per room or per occupancy per room. Depending on the pricing structure the online booking system uses, the Hotel-Spider system will transmit the appropriate structure.
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.
No OTA logic corruption
Depending on the pricing structure management by the online booking system, the Hotel-Spider system has 3 distinct methods to transmit the prices:
- Transmission of the prices based on OTA_HotelRateAmountNotifRQ / OTA_HotelRateAmountNotifRS (Can be used for room-based pricing or occupancy-based pricing)
- Transmission of the prices based on OTA_HotelRatePlanNotifRQ / OTA_HotelRatePlanNotifRS (Can be used for room-based pricing occupancy-based pricing)
- Transmission of the prices based on OTA_HotelAvailNotifRQ / OTA_HotelAvailNotifRS (Can be used exclusively for room based pricing)