Nitesoft has direct integration with Google Travel platform. Nitesoft sends availabilities, rates and restrictions to Google Travel. Guest can find this information in Google Search or on Google Maps. Google Travel navigates guests to Nitesoft WBE to make a reservation. Reservations that are comming from Google Travel will have "Google Travel" channel.
Google constantly monitor accuracy of rates sent to the platform. If the rates sent don't match the rates offered on WBE the hotel score will be decreased and WBE will be moved down in the list of offerings. Google Travel currently doesn't support all the features available in Nitesoft. Therefore when integration is enabled it's important to uderstand what restrictions are exist for rate management.
At this point mapping have to be configured manually and Nitesoft does not validates accuracy of the mappings and does not generates alerts on actions that may lead to break of rate synchronization.
It's important to remember that rate mapping is done for guest combinations. Therefore when hotel changes the way it handles rates for different guest numbers the mapping configuration need to be updated as well. For instance, in case a hotel didn't use different rates for different guest numbers and would like to start using the corresponding rate mappings need to be added before making changes in Nitesoft.
When you add or remove rate chains please also remove the corresponding mapping. Google doesn't support different discounts for different unit categories. Therefore in order to make rate chain compatible with Google Travel all the unit categories must have the same dicount either percent or per night reduction. There is a limited workaround to have multiple rate chains for different groups of unit categories. For instance, a rate chain for single, double and twin, and another rate chain for junior suite and suite. Rate chain discount can be only positive (it's not possible to increase rate). The following fields are supported when Nitesoft rate chains are sent to Google:
- Booking dates - period when reservation can be made
- Stay dates - period when guest can live in the hotel
- Min/Max PickUp - time period when booking can be made relative to arrival date
- Min/Max StayLength - number of nights a guest stays in the room
- Adult count - number of adult guests in the room
- Up to 3 levels of stacking - it's possible to define the order for promotions to apply. For instance, early bird -5% and then long stay -10%, so tatal discount will be -14.5%. This is controlled by Level property in Nitesoft. Only 3 levels are supported: 1, 2, 3.
- Percent discount and discount per night are supported (direct rate is not supported)
There are 3 types of mappings: unit category mapping, rate plan mapping and rate mapping.
On the unit category maping page you define which room categories you would like to make available for the Google guests. Reference can be any alphanumeric value.
On the rate plan mapping page you configure rate plan mappings. The BAR rate mapping is the default one and it is required in this case. Rate chain mappings need to be marked as Solitary indicating that there are no specific rate mappings in these rate plans. Promotions (the entity to which rate chain is mapped) in Google works on all unit categories, so you can't specify different discounts for single and double. Marking rate chain as Solitary you tell Nitesoft to send this discount to Google as a Promition.
On the rate mappings page you configure the values to send for particular combination of unit category and rate plan. Google Travel supports unit availability only on unit category level. E.g. it's not possible to limit the number of units for particular rate plan. In Nitesoft this is achieved with the special (unspecified) rate plan. This record need to export Availability values. Stay length, restrictions and pick up lengths can be exported once per rate plan for default guest combination. Then please specify all the rates for different number of adults. Google travel supports only adult based rates, so no need to add mapping for child rates.
