Introduction

This Index mode uses precalculated price from pricecache

Performance

Faster processing time of changes since no pricecache is required to pre-calculate prices.

Requirements

• Pricecache for the distribution channels for which prices should be available online or through the API.

Functional

• X=Y offers are supported.
• Implies on unit level are not supported.

Flow

Elasticsearch index process

• Re-indexes are running twice a day: in the early morning and early evening (concern time zone). These completely refresh the availability index.
• Updates are running every hour or every half an hour(this differs per customer). These updates process changes in prices, rentability, representations, releases, and reservability.
• Depending on how many changes need to be processed, this process can take several seconds (no or few changes) to 50 minutes (many changes that need a complete refresh of the index).

• Changes that influence the prices are picked up in the update/re-index process after pricecache has processed them.

  		Price changes available
  	worst-case	best-case	average-case
  Pricecache calculation time	120 minutes	30 minutes	60 minutes
  Index frequency	60 minutes	30 minutes	45 minutes
  Indexing time	50 minutes	5 minutes	25 minutes
  total	230 minutes	65 minutes	130 minutes

• Rentability, representation, release, and reservability changes are picked up with every update/re-index process.

  		Changes available
  	worst-case	best-case	average-case
  Index frequency	60 minutes	30 minutes	45 minutes
  Indexing time	50 minutes	5 minute	25 minutes
  total	110 minutes	35 minutes	70 minutes

Pricecache

• Calculates prices for specific distribution channels only (usually internet and tour operators) and stores these in the pricecache (more info: Pricecache).
• The price calculation process constantly checks if changes are made affecting prices.
  These changes have to be at least 10 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
• 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 time will increase.
  Examples of these kinds of changes are:
  • Creating a special that is valid for all accommodations and/or all arrivals
  • Opening a new release
  • Adding a new resort
• Information on which pricecaches are active per client can be found here: Pricecaches.

Side notes

Fully-booked accommodation types

If an accommodation type gets fully booked for a certain period, the availability index will be updated immediately by removing that accommodation type for that period from the index.

Changes requiring a full re-index

The following changes require a complete re-index before they will be available online, therefore it can take up to 12 hours (time between two re-indexes before they will be available online).

• Changing an amenity
• Changing capacity
• Changing the number of bathrooms
• Changing the number of bedrooms
• Changing priority
• Updates in rating
• Adding new stayperiods