Understanding the data model

Disregarding which way (SpiderXML, SpiderCRS/SpiderWBE or SpiderConnect) a third party software provider wishes to integrate with the Hotel-Spider system, understanding how we structured the inventory, rates and stay restrictions should allow a faster integration and most of all a faster debugging.

Dynamic data vs static data

As with other systems, the Hotel-Spider system distinguishes between dynamic data (Data which change on a daily basis) and static data (Data which does not change on a daily basis). Are considered as dynamic data, the following parameters:

Inventory
Open/Close
Minimum length of stay arrival date based
Minimum length of stay stay through
Maximum length of stay arrival date based
Maximum length of stay stay through
Closed to arrival
Closed to departure
Prices
- Occupancy based pricing
- room based pricing

If some of these terms are not clear for you, please refer to the glossary

On the other hand, are considered as static data, the following parameters

Pictures
Textual descriptions
Amenities
Cancellation policies
Payment policies

No static data for Channel-Management

Please keep in mind that managing the static data does not make any sense, should a hotel only use the channel-management functionality of Hotel-Spider. This because we cannot transfer the static data to the different portals connected.

Now that the two different data types that the Hotel-Spider System manages have been explained, it is time to add a bit more complexity and introduce the different levels used in the Hotel-Spider system. When ready, click here to move to the next chapter "Different levels of data"