Definition and Scope

The pricecache is simply a table in the database which contains precalculated prices for specific distribution channels (mentioned in the pricecache criteria, see /wiki/spaces/OWC/pages/11403480).
The price calculator will calculate prices for the distribution channels mentioned in the pricecache criteria and does this only for accommodation types having:

• Release
• Rentability
• Cashflowrules

If Offers are applicable for the accommodation type it will also calculate prices for each applicable special separately, but no combinations of specials.
The price calculator will calculate prices up to a maximum number of durations, defined in the pricecache criteria.

Purpose

The precalculated prices are used by Elasticsearch to store in the availability index so that Bookings Engines, Webservices and the Third Party API can show a price in the search results.
The prices are also used by Resellers (such as Booking.com) which have a direct connection to pricecache to load length of stay prices in their system.

Options

Own pricecache

The distribution channel has its own prices in pricecache, which means it has its own prices and specials which can be used to display online.
Mostly used for internet and tour operator channels which has different prices than internet.

Inherited pricecache

Prices are not calculated for the distribution channel, but prices of another distribution channel are used, which can be used to display online. If the distribution channel has own specials (specific for that channel), then these will be calculated and stored in pricecache.
Often used for tour operator channels to inherit prices of the tour operator channel which has own prices, but use different specials.
To be able to inherit a pricecache it is required that the distribution channel is in the same representation (for all the accommodation types it can book) and has the same rate type as the distribution channel it inherits from.

No pricecache

When a distribution channel doesn't have any pricecache, we fall back to the distribution channel which is marked as Use as base price (There should always be exactly one distribution channel marked as use as base price).

Webservices and Third Party API

This is often used for tour operators, so any tour operator can get availability and prices based on the base distribution channel through the Webservices or Third Party API.
It is not required that the distribution channel is in the same representation and has the same rate type as the base distribution channel, but be aware that these tour operators might receive different availability and prices if the distribution channel is in a different representation and/or has a different rate type than the base distributionchannel. 

TO Portal

If a client makes use of the TO Portal, the tour operator can login and see their availability here. This requires that the tour operator distribution channels are in the same representation as the base distribution channel.

Checklist to decide which option is needed

1. Which representation will this dc have?
   
   1. Added to existing, Step 2.
   2. New representation, Own pricecache needed.
2. Do they want to offer unique specials on the dc?
   1. Yes, Step 3.
   2. No, Step 4.
3. Does one of the dcs in the representation already have an own pricecache?
   1. Yes, Step 4.
   2. No, Own pricecache needed.
4. Which rate type(s) does this dc have?
   1. New rate type, Own pricecache needed.
   2. Same rate type(s) as the dc in the representation which already has an own pricecache, No pricecache needed.
   3. Other rate type(s) as the dc in the representation which already has an own pricecache, Own pricecache.