We are happy to announce our latest TripBuilder release. Please see these release notes for the most significant changes. Let us know if you have any questions, feedback, or ideas for features or improvements!

The "Flight Search with Carrier Criteria" feature, previously made available in Planner, is now accessible in Discovery when creating your own tour, starting with a flight selection. This enhancement allows users to refine their search results by selecting specific airline carriers. The chosen carriers will directly influence the flight results page, providing a more tailored and efficient search experience.

Find more information here.

Accommodation picture handling received a considerable enhancement, significantly reducing broken pictures in the hotel details image carrousel on Planner.

We have improved the ticket selection process for Musement activities to ensure a smoother booking experience. When booking tickets that require a minimum number of passengers, TripBuilder will now automatically select the minimum required number. For instance, if a ticket is available for 2-4 adults, the default selection will automatically set the number of travellers to 2.
​

Based on feedback from Musement, approximately 30% of their inventory will benefit from this enhancement, with plans to increase this coverage to nearly 80% by mid-2025.

We have introduced greater flexibility in the checkout process by relaxing the "Passenger 1 is the main contact" requirement. Previously, this setting had to be selected to proceed with itinerary booking, and the information in the "Contact Details" section needed to match the "Traveller 1" section. Now, it is possible to proceed with the booking even if this setting is not enabled, and different details are provided in the "Contact Details" and "Traveller 1" sections.

Find more information here.

We have introduced a new configuration setting that allows you to define the default country code for the Mobile Phone field associated with the main contact of the itinerary. This setting is available per distribution channel in the Checkout tab. Responding to popular demand via Bucketlist, this improvement replaces the previous default UK country code with a customisable option. It is especially beneficial for distribution channels linked to specific markets, helping to reduce errors when collecting mobile phone numbers. Please note that this new setting is only available if the Mobile Phone field is configured as "Required" or "Optional".

We have updated the Product Referencing Logic to provide a more comprehensive view of where products are linked, irrespective of template or module publication status. Previously, TripBuilder relied solely on "published" views, but now TripBuilder checks both "latest" and "published" versions. This change prevents unexpected failures when deleting products and enhances transparency for Tour Operators. It also lays the groundwork for future improvements in product deletion logic.

We have enhanced the management of travel agencies to better handle those marked as inactive, such as agencies that are closed, bankrupt, or have overdue payments:

Find more information here.

We have enhanced our email notifications to improve the efficiency of customer service operations by including country codes in booking-related emails. Previously, the absence of country codes made it challenging for customer operations and local supplier teams to quickly identify and coordinate with the correct destination teams, potentially causing delays and errors in post-booking management.
​

With this update, our core booking-related emails - covering new bookings, changes, and cancellations - now include ISO country codes. This applies to all recipients, including tour operators, inventory owners, and local suppliers. The country codes are displayed in the email body, following the order they are defined or visited in the itinerary template, consistent with the Booking API response.

For example, for an itinerary covering Spain and Portugal, the email body will include:
​

Country Code(s): ES, PT

This improvement ensures that our email templates support multi-destination bookings by displaying all relevant country codes, allowing teams to expedite booking triage and significantly reducing manual effort.

Find more information here.

The Itinerary API was enhanced by extending the "From-Scratch" endpoint, which now supports including activities within stops. Technical users can now incorporate activities from sources such as Inventory, Musement, and Hotelbeds by referencing product IDs or names. Multiple activities can be added in a single API call and assigned to specific dates or days within a stop. This update also includes parallel searching and mapping of activities to improve the overall API endpoint performance.

Find more information here.

We have introduced a new functionality that enhances the integration capabilities of our Booking API, particularly benefiting customers who use back-office systems for reconciliation.
​

Previously, itinerary searches within TripBuilder were limited to using the TripBuilder itinerary reference, restricting customers from utilising their own external booking IDs. With this update, you can now populate and search using an external reference ID.
​

When a booking is confirmed, the external reference ID field can be populated via API with your desired back-office booking ID. This allows you to store and retrieve this ID within TripBuilder, enabling customer care agents to search for itineraries using the external reference ID. This enhancement streamlines the reconciliation process and improves operational efficiency.

Find more information here.

We are happy to share further enhancements to TripBuilder Analytics:

Find more information here.

Nezasa follows the “Now, Next, Later” framework to outline the development trajectory of TripBuilder, enhancing transparency around our progress. We share these insights with our customers in each new release in the TripBuilder - Now, Next, Later article.