Guest types can be used to differentiate pricing on activity products. Since guest types are part of the pricing structure, this simplifies the product setup.
Common use would be setting up guest types, for example Adult, Child, or Senior, and so have different pricing for each type.
Note: Guest types are not required and do not have to be used, if they are not needed for pricing purposes.
Also note that guest types are generally set up for all products. You can, however, specify on a product level if only a subset of the guest type is allowed or none at all.
| Field | Description |
|---|---|
| Code | The code used to reference the Guest Type. |
| Description | General description. |
| Internal Comment | Comment for internal purposes. |
The guest type usage is defined on the reservation type, that is if the guest type is shown and editable on the reservation.
Pricing activity products has an option to set pricing per guest type.
You can assign a default guest type to an activity product, and also specify if guest types should be selected during the POS booking process.
Note: When paying an activity which has guest type assigned, then the resulting sales invoice line/POS journal line populates the variant code as the assigned guest type. The variant code is created automatically on the related posting item (retail item) if it does not exist at payment time. This allows the user to see the sale of the posting item based on guest types (variants) if required in backoffice pages, reports or BI views.