Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Locations are the second main entity in the system. A location can be a resort, a geographical entity or a sublevel to create a hierarchy. Accommodations are grouped in a location. 

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:

  • subjects (which travel company categories can be booked)
  • commissions
  • cancellation extra's
  • add ons for accounting purposes

Business scenarios where the user needs a location:

  • 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


  • No labels