...
Typical resort structure (example):
Toplevel:---
- resort A
...
- resort B
→ a sublevel is advised, in case there are general data for a group of locations, for example, country → specific costs related to that country
Typical ' serviced apartments' structure (example)
Toplevel:---
- Amsterdam
...
- Rotterdam
Configurations which are common to do on a top-level and can be used for all sub-levels:
...
- as a filter for check-in
- as a filter for housekeeping planning and maintenance
- in case of using the tax module and different tax rates
The location structure is fundamental configuration which cannot be considered dynamic, meaning, it is not possible for the user to add or remove additional sublevels or move locations from 1 parent to another. The location tree structure should be considered a fixed framework which is setup at first when MXTS is configured. Over time, new bookable locations can be added in the existing structure (below existing sublevels), or new sublevels are added to the structure when circumstances make sense (new location in a new country).