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
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.
☞ Docs: Zak - Room Categories
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.
For your products (and not for physical rooms or room categories!) you can set prices and restrictions using Tabla and Sytar.
☞ Docs: ZaK - 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)
☞ 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.
For example the Suite double use, could always have a price equal to +15% more than Double standard.