| Table of Contents |
|---|
...
We have several index modes available which all have their requirements and benefits. Below you can find a matrix in which per index modes the requirements, benefits and limitations are listed.
Matrix
LOS prices using pricecache | LOS prices using cashflowrules | Nightly rates on unit Length of Stay using Pricecache | Length of Stay using Cashflowrules | Nightly Rates on Unit level | Nightly rates Rates on type 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 discounts offers (e.g., -20) | | | | | |||
| Relative (percentual) discounts offers (e.g., -10%) | | | | | |||
| Override discounts offers (override price for specific period) | |
| | | |||
| X=Y discounts 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
General Flow
Pricecache
- The Price calculation process runs every hour for all clients.
- Calculates prices for specific distribution channels only (usually internet and tour operators) and stores these in the pricecache.
- After a change has been made that needs (re)calculation or removal of prices it can take at most 1.5 hours before this gets picked up by the price calculator. The price calculator only picks up changes which are at least 30 minutes old. This has been done for efficiency reasons, because when multiple changes are made affecting the same accommodations these will be merged together, so it only has to calculate prices once.
- Changes that require price calculation are:
- Changes in cashflowrules
- Changes in rentability
- Changes in representations
- Changes in releases
- Changes/creation of specials
- In general, one run of the price calculator will calculate all the prices for changes made since the last time it ran, one run takes at most 50 minutes.
So, in worst-case, prices will be calculated after at most 2 hours and 20 minutes (1.5 hours + 50 minutes (maximum calculation time)).
In best-case the calculation just needs a couple of minutes, so just over 30 minutes (30 minutes + calculation time).
On average prices can be expected to be calculated in one hour. - However, it can occur that one run of the price calculator won’t be enough to calculate all the prices for a change. This is because the duration of the calculation depends on the impact of the change. If a change spans a large period and/or affects a large part of the accommodations, calculation times will increase.
Examples of this kind of changes are:- Creating a special that is valid for all accommodations and all arrivals will require many prices to be calculated and
- Opening a new release
- Closing a release
- Information on which pricecaches are active per client can be found here: /wiki/spaces/OWC/pages/11403480.
- Information on which client uses pricecache for prices in the Elasticsearch index and which uses the price calculation in the indexer application itself can be found here: /wiki/spaces/DEV/pages/5016084.
...