Different levels of data

As explained on the previous page, Hotel-Spider manages a broad variety of parameters, regrouped in dynamic data or static data. In addition to the multitude of parameters, a notion of levelling is also used. These levels are Hotel, room, rate plan and product. Whereas the static data parameters will only apply on the specific level on which they are applied, dynamic data parameters have a hierachy notion, reaching from the most global level: Hotel to the most specific level: product. Within this hierachy chain, the most constraining parameter will prevail.

Understanding which level is used

To understand which dynamic parameter applies on which level for which channel (CRS, WBE, Channel-Management, Meta, etc..), the Hotel-Spider extranet disposes of tooltips to inform which value will be taken into account for which channel.

1. Hotel level

When it comes to dynamic parameters, those defined on the hotel level, will apply to all the room types, all the rate plans and all the products configured for a property.

For example: closing on Hotel level means that all the rooms, all the rate plans and thus all the products will be closed.

2. Room level

Dynamic parameters defined on the room level will apply to a specific room type and all the products based on the same specific room type.

For example: Setting a Minimum Length of Stay will be applicable for the room type it has been set for as well as for the related products unless they have a more constraining minimum length of stay.

3. Rate plan level

Dynamic parameters defined on the rate plan level will apply to a specific rate plan and all the products based on the same specific rate plan.

For example setting a Minimum Length of Stay will be applicable for the rate plan it has been set for as well as the related products unless they have a more constraining minimum length of stay.

4. Product level

Dynamic parameters defined on this level will only apply to one specific product.

For example: setting a Minimum Length of Stay will apply only to one specific product.

Use case 1. Minimum Length Of Stay accros different levels

When a Minimum Length of Stay of 2 is set on Hotel level, a Minimum Length of Stay of 4 is set on rate plan level and a Minimum Length of Stay of 3 is set on product level then the most constraining value will be 4.

Use case 2. Open/Close accros different levels

When a Hotel is open on hotel level, open on room level, closed on rate plan level and open on product level then with the exception of the products based on the closed rate plan, all the other products will be sellable.

Use case 3. Closed to Arrival accros different levels

When closed to arrival is enforced on hotel level, not set on any other level then none of the products will be bookable with the closed arrival day.

Data levels accross Channel-Management connections

Not all the channels, we connect to, manage their data on all the levels the Hotel-Spider system does. Because of this, more restrictive settings might not be transfered to a channel, if the corresponding level nor an underlying level is not available. For example: should a Minimum Length of Stay should be configured on product level but a channel lowest level would be room level, then we cannot transfer the Minimum Length of Stay.

By now the third party software provider should be familiar with the data structure used by the Hotel-Spider system. The next step will be to dive into the interface specific documentation. Select the appropriate interface from the left menu.