Image Added

Introduction

For the web managerAPI, 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.

We use Elasticsearch to store availability and prices. Elasticsearch is a search engine that provides fast searches and grouping of data (so-called aggregations).
The availability index consists of documents and each document represents a possible stay; it contains (among other fields) a resourceId, arrival date, duration, distribution channel, units, price, and possibly an offer code.
Only accommodation types meeting the following criteria will be indexed:

• Are released
• Have rentability
• Have prices

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.

An overview of which customer uses which index mode can be found here: Index Modes.

Matrix

Nightly

		Length of Stay using Pricecache

Length of Stay using Cashflowrules

Night Rates on Unit level

Nightly

Night Rates on Type level
Performance	Processing time (faster = more real-time)

	Index size (smaller = faster search)

Requirements

Nightly rate

Rate Option - Night rates

	Rate Option - Length of stay

(LOS)

rates

	Every day departure

	Departure on specific days
	Difference in units of one accommodation type  (e.g., amenities)
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

*
	Offer that overrides accommodation price ("New price" offer)

**	**
	X=Y offers (e.g., 7 days for price of 6)
	Subject-based offers
	Exact period only offers

	Combination of offers (max. 2)

**

***
	Implies fixed amount per stay

****

	Implies fixed amount per night
	Implies subject-based

**

	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
	Reallocation
	Include unavailable units

* Inheritance: only if the distribution channels are in the same representation, have the same rate types, and don't have unique specialsonly if configured with nightly or consumption rates.

** Support for these will be added through  Image RemovedMXTS-26931 - Add support for internet additional costs in the night price index OPENonly when the offer is "exact period only", support for partially valid offers will be build in: 

*** only in optimised mode

Troubleshooting

To check why some availability is missing, see Checklist availability online.