This month, we are launching exciting product updates in Lemax. Learn about the details below (available from 28th November, 2024).

What’s new

Lemax now supports a “Per Day” billing type for Tour staff product types: Guides and Drivers, enabling precise daily billing calculations for reservation items.

This update is automatically available to you once the release is launched. Please note that the usage of this update could depend on system setups (which modules/products you use) and user roles.

Problem being solved

For products like Guides and Drivers, where billing is based on the number of service days, previous billing structures could not automatically calculate daily costs based on reservation duration. This required manual adjustments, increasing the chance of errors and reducing efficiency.

Benefit for the users

Users can now manage daily billing for specific services without manual calculations, enhancing accuracy and reducing administrative time for day-based billing needs.

How it works

Entering Tour staff

Per day billing type available when entering Tour staff

Booking Tour staff

When booked, the price is calculated Per day

What’s new

The background engine for quick search functionality has been reimplemented. The functionality of Quick search within Lemax is intact.

This update is automatically available to you once the release is launched. Please note that the usage of this update could depend on system setups (which modules/products you use) and user roles.

Problem being solved

  • system slowness
  • performance issues

Benefit for the users

  • higher stability of a system and reduced maintenance complexity
  • reduced number of incidents related to the search box
  • improved quality of the service
  • more robust quick search

How it works

Quick search

User can search:

  • reservations by entity id, name, period, customer, and customer’s email
  • passengers by name, email, city, and address
  • partners by name, email, city, and address

Note for users

Quick search doesn’t support search “like” functionality. For example, when searching “eorg” in a word “George”, no result is expected. However, “Geor” will return a result.

Quick search indexes other descriptive data about reservations, partners and passengers, but isn’t expected to always return consistent information, due to its nature of being updated via background operations, as well as the above stated fact.