Behavior based on backoffice product configuration

Behavior based on backoffice product configuration

Based on how the product is configured in the backoffice, the widgets will behave differently.

Bilberry Backoffice Terminology

Product: A product is a single item that contains information about the product, such as name, description, price, and availability.

Project: A project is products combined with date and time series, and individual project items are the actual bookable entities in Bilberry. Availabilities and capacities are set on the project level.

Tour series: Same as project.

Tour: A single project item in a project at a specific date and time.

Ticket option: A ticket option is a specific type of ticket that can be booked on a tour. For example, a child ticket, an adult ticket, or a family ticket. The product also has the default ticket options, so we are able to display and select them before selecting a date and time.

Project collection: A project collection is a collection of projects that are combined into a single entity. This is used to group different projects together, such as a project with adult tickets and a project for child tickets. The purpose of this is to allow the booking forms to display these projects as a single entity, while still tracking resources separately for each individual tour. This is useful when you have different ticket options that require different resources, such as life vests of different sizes.

Extra: An extra is a product that can be added to a booking, such as a meal or a t-shirt. Extras are effectively tours added to tours.

Cutoff Time

You can set a cutoff time for products in the backoffice. If the current time is past the start date minus the cutoff time, booking that product at that time will not be possible.

Translations

In the backoffice, the names, descriptions and a range of other text fields can be translated into multiple languages. The widgets will display the text in the language the widgets are configured to use.

If the language or text of your widgets is not as expected, please review the translations in the backoffice, as well as the language configuration of the widgets.

Bilberry settings

The widgets read a few settings from the backoffice, which can affect the behavior of the widgets. These settings are:

• Currency: The currency used in the widgets.
• Timezone: The timezone used in the widgets.

Quantity Validation in widgets based on backoffice configuration

In the backoffice, you can configure specific minimum and maximum quantity requirements for products, individual ticket options, and combinations of these. The booking widget uses these configurations to validate the quantities entered by users, ensuring that they adhere to the defined rules.

For example, if you offer child and adult tickets that require different resources (such as life vests of different sizes), this feature allows you to track resource consumption accordingly.

Using Project Collections, you can also enforce specific combinations of ticket options during the booking process. For instance, you can require users to select both an adult and a child ticket before proceeding with their booking. This is achieved by configuring the product in the Bilberry backoffice to enforce minimum and maximum quantity requirements across all ticket options.

Quantity Validation Rules in Different Scenarios

The following backoffice configurations influence how the booking widget validates quantities:

Maximum Quantity Validation

1. If using a Project Collection and a max entrant limit is specified:

   • The maximum quantity is determined by the lesser of:
     • The tour’s total capacity, and
     • The project collection’s max entrants per booking.
   • The quantity of other ticket options within the same project collection is subtracted from this total.

2. If using a Project Collection and no max entrant limit is specified:

   • The maximum quantity is simply the tour’s total capacity, without considering other ticket options within the project collection.

3. If not using a Project Collection:

   • The maximum quantity is the tour’s total capacity, minus the quantity of other ticket options for the same tour.

Minimum Quantity Validation

1. If using a Project Collection and a min entrant limit is specified:

   • The minimum quantity is the greater of:
     • The ticket option’s min entrants, and
     • The project collection’s min entrants, taking into account other ticket options in the same project collection.

2. If using a Project Collection and no min entrant limit is specified:

   • The minimum quantity is determined by:
     • The ticket option’s min entrants, or
     • The tour’s overall min entrants.

3. If not using a Project Collection:

   • The minimum quantity is based on:
     • The ticket option’s min entrants, or
     • The tour’s overall min entrants.

Display of Extras based on backoffice configuration

In the backoffice, you can configure how the extras are displayed in the checkout process.

Show extra as minimal: If this option is enabled, the extras will be displayed in a minimalistic format in the checkout process. This means no image, description or icons will be displayed. Only the title, price and quantity selector will be shown.

Show extras as list: If this option is enabled, the extras will be displayed in a list format in the checkout process. By default, the landscape version of the product cards will be displayed. If the minimalistic format is enabled, there will still be a portrait version of the product cards.

Show time: If this option is enabled, the date / time of the extra will be displayed in the checkout process.

Custom icons

In the backoffice, you can upload and configure custom icons for both Products and Projects (and by extension extras). If this is done, the widgets will display these icons instead of the default icons.

If you wish to display no icons, configuring custom icons, but not uploading any, will achieve this.