Introduction
For the web manager, bookings engine, my environment and webservices we don't use database listeners. For this, we have a separate flow in place, because we require additional information (such as pre-calculated prices) in the Elasticsearch index.
Index Modes
We have several index modes available which all have their requirements and benefits. Below you can find a matrix in which per index mode the requirements, benefits, and limitations are listed.
Matrix
Length of Stay using Pricecache | Length of Stay using Cashflowrules | Nightly Rates on Unit level | Nightly Rates on Type level | ||
---|---|---|---|---|---|
Performance | Processing time (faster = more real-time) | ||||
Index size (smaller = faster search) | |||||
Requirements | Nightly rate | ||||
Length of stay (LOS) rates | |||||
Every day departure | |||||
Departure on specific days | |||||
Functional | Inheritance of prices | ||||
Length of stay price calculation | |||||
Fixed rate offers (e.g., -20) | |||||
Relative (percentual) offers (e.g., -10%) | |||||
Override offers (override price for specific period) | |||||
X=Y offers (e.g., 7 days for price of 6) | |||||
Exact period only offers | |||||
Combination of offers (max. 2) | |||||
Implies fixed amount per stay | * | * | |||
Implies fixed amount per night | * | * | |||
Implies with relative prices | |||||
Implies on unit level | |||||
Search amenity on location level | |||||
Search amenity on type level | |||||
Search amenity on unit level | |||||
Gap configuration |
* support for these will be added through MXTS-26931 - Add support for internet additional costs in the night price index OPEN