Zak - OTA Limit and Availability modifier

This article will talk about two very powerful and delicate restrictions that we have bravely introduced in our system: the rate level availability modifiers dedicated to online sales.
With the "Ota Limit" and "Availability Modifier," you can change the availability of a product day by day, rate by rate.
These advanced tools are not mandatory, so you can also choose not to use them.
However, we developed them by listening to your requests on the forum.
These advanced marketing tools could be a first step towards building a powerful Yield Manager!

You can find a description of all restrictions available in Zak in the Tabla article:

☞ Docs: ZaK - Tabla



With the Availability Modifier, you can increase or decrease your room categories' actual availability on a selected rate. This allows you to receive "programmed" overbooking or to limit your online availability in general, both on OTA and on your site, for a specific rate.
The value that you set in this field will then:

  • increase (if positive) the availability value
  • decrease (if negative) the availability value.

The value set as Availability Modifier does not change after receiving reservations: only the availability value changes.

The Ota Limit, instead, is used to limit your sales on OTA to optimize direct reservations or differentiate them per channel.
 
But do OTA channels support different availability on a rate basis??
The answer is no. At least in general, the availability is managed at room level.
You could put restrictions and closures: but closing some rates over others is not the same as differentiating availability.

So, how does it work? How does Zak send different availability values to your channel rates?

Let's make an example.

On our OTA X, we have two rates: OR1 and OR2. Let's say that these rates are mapped to Zak ZR1 and ZR2 rates. And let's suppose that for a selected day, the availability of a room is equal to 100.
 
On ZR1, we set Ota Limit = 4. While on ZR2, we set Ota Limit = 6.
In this case (and assuming no reservations have been received yet from OTAs), Zak will send availability = 4 to both rates (OR1 and OR2).

Let's see what happens when you receive the first OTA reservation...
 
The OTA availability has decreased: on OR1, we have 3 available rooms. And on OR2, we have 5 available rooms.
 
As in the previous case, Zak sends to the OTA the lowest value (= 3).
As you receive more reservations, the availability keeps on decreasing. Until the OTA Limit of the ZR1 rate is reached.
 
We now have 4 OTA reservations. The OR1 rate will be closed (OTA Limit = 4).
But at this point, Zak will send availability =2, keeping the rate OR2 open. Ready to receive two more reservations.
 


Did this solve your problem?