Zak - Products

You can offer physical rooms belonging to the same room category with different sales conditions (price/restrictions) depending on the occupancy.

For example, you can sell a quadruple room to 3 adults with a triple occupancy price, or maybe you want to offer a triple room with occupancy 2 at a lower price, but only if the stay lasts at least three nights, etc.


☞ Docs: ZaK - Physical rooms

☞ Docs: ZaK - Room Categories


Product


A product is a combination of room category and occupancy. You can specify four age groups for each product: Adults, Teenagers, Children, and Babies. In this way, you can better customize your prices.

Zak creates by default a product for each room category with the specific basic occupancy. Starting from these predefined products, you can add others with a different occupancy.


We remind you that when you create a new type of room, you can specify the further occupations with which you want to sell it, beyond the basic occupancy. In this way ZaK will automatically create the products for all the occupations (as mentioned in the documentation below):

☞ Docs: Zak - Room Categories


In the example below, we're selling the room DOP for 2 adults by default. And we're also selling it as DOP 2.1.0.0, which means with occupancy: 2 adults, 1 teenager, 0 children and 0 babies.
So from the same room category, you can create different products: in the example below, starting from the main product DOP for 2 people, we have created four different products with a different occupancy:







How to use products


Products are specifically designed for the sale on internet portals, so they are available in the channel configurations of the ZaK Channel Manager and the ZaK Booking Engine.
Online booking portals generally offer the same room category with different rates. For example, you can put the DBL room for sale with the "Standard Rate" and the "Non-refundable Rate."
Often these rates "represent" a specific occupancy: "Single-Use" Rate, Standard 2 Adults, Standard 3 Adults, etc.

☞ Docs: What is an OTA?

☞ Docs: What is a Booking Engine?


Your sale on the portals consists of combinations of "room category - rate," for example: (DBL - Standard), (DBL - Non-refundable), (TRP -  Standard), (TRP - Non-refundable), etc. Each combination has its price and restrictions, on each day.
For your products (and not for physical rooms or room categories!) you can set prices and restrictions using Tabla and Sytar.

☞ Docs: ZaK - Tabla

☞ Docs: ZaK - Sytar


On Zak, you can create prices and restrictions for each of your products. In the channels available on your Channel Manager, you can then map each ZaK's Product-Rate to each Portal's Room-Rate.

☞ Docs: ZaK - Rates


For example, suppose you have different rates for occupancy on the OTA portal (1PAX, 2PAX, etc.). In that case, you can associate the "room-rate" combination with the related Zak by-product without creating special rates.

If you want to sell a Double room with a "Standard 2 pax" rate and a "Single-use" rate, in Zak, you don't need to create the "Single-use" rate. You only need the by-product "Double single-use," and the channel mapping will be as follows:

(Double, Standard 2 pax) <---> (Double, Standard Rate)

(Double, Single Rate) <---> (Double Single-Use, Standard Rate)



Room setup


We have implemented the possibility of assigning predefined room setups (Double, Twin, Double with an extra bed, etc.) to each Product:





The creation of the Room Setups is connected with the new features we have developed for the ZAK Online Reception.

☞ Docs: Zak Booking Engine


Price Derivation and Restrictions


The price of one product may be derived from that of another product. For example, the double DBL single-use (1.0.0) has a price derivation of "- 20€" from the double DBL with occupancy 2 (2,0,0)

In these cases, it is very convenient to use automatic derivation. It is a "transformer" that, starting from the price of the product of reference, calculates the derived product price. This avoids having to define many prices that can be easily calculated by the system.


When creating a product, you can then choose whether to derive the price or not.
You must indicate the transformation "type" that can be sum or subtraction of a fixed value or a percentage.

Attention: This derivation does not affect the availability, but only the price. The two products, the one from which the price is taken and the one in which the price is derived, could represent different room categories.
For example the Suite double use, could always have a price equal to +15% more than Double standard.
Just as for prices, restrictions are also derivable. In this case you can just indicate which restriction (closure, minimum stay, etc.) should be inherited.













Did this solve your problem?