Release Note 20.8

Improved product typing

A better automatic typing of imported products has been implemented in order to avoid that tours, self-tours, combos, cruises, or campsites are typed as stays.

Improvement of the management of age groups

The evolution of the sales of activities and services makes it important to be able to sell the activities requiring a fine management of the age groups.

This means being able to import them into the database, send them to the reservation process, display them and be able to select and reserve them. Once the reservation is made, it is necessary to be able to consult in the back office the reservation with the age groups in question. It is therefore an important work that has been done and that has impacts at many levels and in many modules of the platform, from import to back office.

Import

In the price grid, prices can be entered by age group by duplicating as many groups as possible with their prices.

In this import, it is possible to specify the low and high limit of ALL the brackets (minimum and maximum age of the bracket).

The management of quantity constraints by band also follows this new operation.

Catalog services

The information of the slices and the prices per slice are connected via the catalog services. This is so that a website can use them.

Reservation process

On the booking process, it is now proposed a selection menu by age group and not a selection by passenger one by one according to the booking form.

Here is the appearance of the selection of a service with the following age groups:

  • Senior [65-99]
  • Adult [16-64]
  • Teenager [11-15]
  • Children [2-10]
  • Infants [0-1]

Depending on the participants requested in the catalog, some choices will not be displayed.

The senior age group is always proposed if it exists because adults can be concerned (in fact, all the groups can concern an adult whose age is not known).

The automatic assignment between the reservation process and the connection takes into account these brackets.

Integration of the Viator source

The Viator activity source has been connected and is now available for distribution via the platform and according to all processes (Package and Prepackage, Dynamic Package, Activities and Services)

Displaying the availability of “Promos” prices

In line with the Omnibus directive, which will reduce the volume of “brochure” prices, “Promos” prices will be highlighted in red in the reservation module for Professionals (B2B)

The following are affected: in the results lists, the call prices of the product cartridges, and the availability prices of the product sheet calendar.

Example of a promotional price list in the result list.

`

Type of payment “On account

It is now possible to define in the backoffice “On account” payment types in order to indicate the payment method linked to the entered payments.

New API for the SPI system

SPI is a system used by seasonal rental agencies (mainly in the mountains today).

Their API is evolving for more security and more content and performance. We have integrated this new API.

  • It supports advanced options (new feature).
  • It adds more editorial information (new fields).
  • It handles the services with more accuracy (sending the date range on each request).
  • The commission is handled on this integration (for stay and commissinable services).

Adding editorial content in languages other than those imported

It is now possible to manually enter editorial content on external (imported) products in a language other than the imported languages.

Use case:

  • Activation of a language, all internal and external products have the edito of this language activated (empty/grey by default).
  • Completion of an EN editorial manually on an external product, each zone can be desynchronized or synchronized in anticipation of a future import.
  • Import of contents for this product (external TO), with an EN editorial only
  • The FR edito visible is the one of the import. It can be overwritten manually by desynchronizing fields.
  • The EN editorial entered manually (in progress) is not impacted.
  • I import contents for this product (external TO), with an editorial FR and EN.
  • The manually entered EN editorial is not impacted, but an imported version appears (desynchronized by default, at least on the zones that have been desynchronized manually in the previous steps)