This month we’ve launched five exciting product updates in Lemax. Learn about the details below.

Enable Insert Ad-hoc items on existing reservation via Online booking API

What’s new

Lemax Online Booking API now supports adding ad-hoc items on existing reservations.

When using the Multiple business entities Add-on, it is now possible to set the business entity of the new ad-hoc item when adding the item with the Online Booking API.

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

When using Online Booking API, adding new items to the existing reservations was limited to products defined in the Product catalogue. That meant that booking new items on existing reservations for 3rd party suppliers which are not part of Lemax could not be inserted into the Lemax booking engine.

When using Multiple business entities Add-on, and adding new bookings with ad-hoc items or adding to existing ones, it was not possible to determine the business entity of the new ad-hoc item.

Benefit for the users

  • Users with custom implementations of Online booking API can now add new cases to their implementations. As mentioned above, items from 3rd party suppliers not integrated with Lemax can now be added as ad-hoc items to existing bookings.
  • Users with Multiple business entities Add-on can now determine the exact Business entity for the ad-hoc item and with custom integrations correctly set it in Lemax.

How it works

Enabling ad-hoc items on existing reservations

In the API method, InsertReservationItem added new field AdHocItems which enables adding ad-hoc items.

For more details, please look into our official documentation: https://support.lemax.net/developers-list/

Enabling setting business entity for ad-hoc items

In API methods InsertReservationItem and InsertReservation within ad-hoc items added new property BusinessEntityID. This property will determine to which business entity a new ad-hoc item will be added.

For more details, please look into our official documentation: https://support.lemax.net/developers-list/

New payment gateway provider: PaySmart

What’s new

With this release PaySmart payment provider integration is supported in Lemax system. This allows you to integrate your Lemax solution with PaySmart payment provider, if you use it.

Please contact customer.success@lemax.net for additional information regarding this new add-on feature. We would be happy to assist you and schedule a demo presentation.

Problem

Enhance the payment provider support in Lemax system to include PaySmart payment provider.

Benefit for the users

  • Users can now use PaySmart payment provider.

How it works

Payments can be made through PaySmart payment provider

Payment methods that support PaySmart need to be configured in the system. Once the configuration is done, payment methods supporting PaySmart can be used to pay for reservations, either via payment links, or via online booking form payment.

New payment gateway provider: PayGate

What’s new

With this release, PayGate payment provider integration is supported in Lemax system. This allows you to integrate your Lemax solution with PayGate payment provider, if you use it.

Please contact customer.success@lemax.net for additional information regarding this new add-on feature. We would be happy to assist you and schedule a demo presentation.

Problem

Enhance the payment provider support in Lemax system to include PayGate payment provider.

Benefit for the users

  • Users can now use PayGate payment provider.

How it works

Payments can be made through PayGate payment provider

Payment methods that support PayGate need to be configured in the system. Once the configuration is done, payment methods supporting PayGate can be used to pay for reservations, either via payment links, or via online booking form payment.

Note on usage

PayGate requires payer country to be sent to PayGate. You need to enable the country in Booking form data and mark it as required when PayGate is enabled.

When paying via payment link on existing reservation, for example via payment link available in documents, country will be taken from customer of the reservation. Even though country isn’t required field in Lemax, if it isn’t set on customer, it will result in the customer not being able to pay for the reservation.

Integration between Lemax and WETU (itinerary builder)

What’s new

Lemax is integrated with WETU!

WETU is one of the dominant itinerary builders for certain world regions, providing the users with beautiful, rich content and interactive itineraries.

Booking data created in Lemax is interfaced in real-time with just one click (or even automatically) to WETU, where you can continue with editing the itinerary with additional details.

Please contact customer.success@lemax.net for additional information regarding this new add-on feature. We would be happy to assist you and schedule a demo presentation.

Problem

When trying to promote business and increase your revenue, it is crucial to excel in certain business areas. One of the most important is providing the end customer with a unique experience and customization, where the strongest ally is Lemax and it’s variety of features.

Sometimes, pdf documents and itineraries are just not enough to succeed in the above mission. End customers wish for modern look-and-feel tools and technologies, with detailed information and interactiveness.

Benefit for the users

  • Easy to use integration
  • You can create interactive and beautiful itineraries that leverage sales, customer experience and satisfaction
  • You have the possibility to use rich WETU content (destinations, accommodations…)
  • You can edit itineraries in WETU throughout the whole process
  • Your partners using that have WETU license can work on the same itinerary and send it to the end customer
  • Create custom itineraries and themes (branding) in WETU, define own destination and supplier database in WETU
  • You can even organize mapping of products from Lemax to WETU (please contact customer.success@lemax.net for this feature)

How it works

Interface itinerary to WETU – manually or automatically

  • Interface to WETU is done through automatic action
  • Automatic action can be configured as per your needs:
    • Automatic or manual
    • Reacting to reservation events and/or reservation item events

Whenever you are finished with managing your booking in Lemax, you can just push the itinerary to WETU and have it visible there in just a few seconds!

How do I know a booking is interfaced to WETU?

When a booking is interfaced to WETU successfully, it is checked on the reservation custom field Reservation sent to WETU

Logging in Lemax

As if the above is not enough, whenever you need more information regarding the actual interface to WETU – if it failed or was successful, you can find the information in Other system logs.

Just filter by:

  • Other system → WETU
  • Log type → Information for successes, Warning/Errors for other log types

What data is interfaced to WETU?

Basically, all reservation items are interfaced to WETU, except cancelled and cancellation fee items.

However, not all products are interfaced with the same level of details.

In this iteration, Lemax interfaces:

  • Accommodation
  • Transfer
  • Flight
  • Activity

products with more extensive details. The rest of the products is interfaced with the basic* set of data.

General booking data interfaced:

  • Booking number
  • Booking description
  • Created by user
  • Booking status

*there are limitations on WETU API that prevent Lemax to interface all possible data from the Lemax bookings

How can I find my booking in WETU?

Well, first you need to have a WETU account.

After you login to WETU/connect page, you are able to see the list of all bookings interfaced from Lemax to WETU.

What is what?

  • Name → Lemax booking description, or booking number if nothing is written in booking description
  • Ref → Lemax booking number
  • Agent → Created by user in Lemax
  • Date → Interface date
  • Action → Connect/Update/New → if you are accessing the itinerary for the first time, only Connect will be available. Click on that to proceed with building or previewing the itinerary
  • Services → Map services between Lemax and WETU. This can be either done upfront during the implementation for the existing Lemax products, or done service per service each time a new one lands from Lemax to WETU. Once mapped, always mapped.
    Also, mapping can be removed or replaced with another if needed.

Ok, how finally does this itinerary looks like?

Lading page, click on ENTER to get the details:

Itinerary overview:

This is what your customer gets.

But, can I make changes on this itinerary?

Yes of course. You can always adjust your itinerary by adding, removing or editing existing services by using the itinerary builder (design tool).

Your partners, if they posses a WETU account, can also make changes on the itinerary before sending them to the end customer.

No communication from WETU

Only Lemax can push data to WETU. WETU does not support backwards communication, meaning that Lemax can’t store the itinerary link/code/other from WETU on the booking in Lemax.

Currently, Lemax does not support interfacing descriptions entered on products or destinations to WETU. WETU has a rich database that accommodates most clients’ needs.

Branch offices on documents and transactions

What’s new

Documents and transactions can follow the reservation branch office instead of the usual user’s default branch office.

Please contact support@lemax.net for additional information for advisory services on how this update could be set up for your instance or if you have any additional inquiries. 

Problem

Documents and transactions followed user’s default branch office which sometimes led to a discrepancy in profitability overview per branch office.

Benefit for the users

  • more accurate reports per branch office
  • less manual work
  • less mistakes

How it works

Creating a document on single reservation level

Preselected branch office depends on the iteration of the document (new document or there’s already an existing one) and it will be either the reservation branch office or the branch office of the existing document.

Creating a document via group action for multiple reservations (in All reservations grid)

Preselected branch office depends on the selected reservations’ branch offices and it will be either the reservation branch office or the user’s default branch office.

Creating a document via group action for multiple reservations (in Operations report) – supplier inquiry, supplier confirmation, supplier invoice

Preselected branch office depends on the selected reservations’ branch offices and it will be either the reservation branch office or the user’s default branch office.

Creating single transactions on reservation level

Preselected branch office is the reservation branch office, except for distribution of group payments.

Creating single transactions on document level

Preselected branch office is the document branch office.

Creating a transaction via group action for multiple reservations of the same customer (in All reservations grid)

Preselected branch office depends on the selected reservations’ branch offices and it will be either the reservation branch office or the user’s default branch office.

In all of the cases it’s possible to manually choose a different branch office from the dropdown.