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!

In this release, we have improved the hotel mapping recommendations of Planner Copilot, ensuring it now fully respects the configured accommodation suppliers. Previously, the copilot could suggest hotels from Nezasa’s global property list that were not available through the suppliers connected by the tour operator. This update ensures that only accommodations with proper supplier mappings are considered, enhancing the relevance and accuracy of hotel suggestions.

We've improved the user interface for displaying "Guaranteed Departures." Initially, we explored making the "Guaranteed" checkbox directly editable from the table but reverted this change to maintain a simpler and more reliable workflow where all edits are handled through the modal.

To improve clarity, the disabled checkbox in the "Guaranteed" column has been replaced with a specific icon. This icon now clearly indicates whether a departure is guaranteed, making the table easier to read at a glance without changing the underlying editing process.

We have expanded the range of supported currencies in our frontend application. Users can now view prices and conduct transactions in the Guyanese Dollar (GYD), Eastern Caribbean Dollar (XCD), Jamaican Dollar (JMD), and Barbadian Dollar (BBD).These new currencies have been added to the currency selector component. This update includes correct currency conversion, accurate price formatting, and updated documentation to reflect the new additions, improving the local user experience.

The Booking API response now includes a dedicated down payment attribute within the payment object. This new attribute will clearly display the non-refundable prepayment amount, resolving previous confusion caused by implicitly indicating deposits via the first payment transaction.

The down payment attribute will be populated using the same logic as the Midoco Connector, and it will be set to null or None if the down payment is not an absolute monetary value or is missing.

This enhancement improves clarity and reliability for down payment/deposit retrieval. The new field has also been documented in the API documentation.

The information is also available to Customer Care users via the Cockpit Copilot if they ask the chatbot ‘what is the downpayment for this itinerary?’

This new boolean field indicates whether a flight was imported via PNR (true) or selected through flight search (false). The attribute enables different supplier handling based on how the flight was added to the booking.

We've enhanced the Booking API response for rental car components to include a new pickupCode attribute. This attribute, found within RentalCarComponentAttributes, will now be populated with a short string representation of the pickup location's coordinates.

This change ensures that the Booking JSON provides information equivalent to what the Midoco Connector sends, allowing Midoco to correctly populate both the car-service/pickup-code and car-service/return-code fields, improving efficiency for car service bookings.

We’ve successfully integrated the BusyRooms API into our platform. BusyRooms offers first-class technology that expands distribution reach by connecting to over 500 global sales channels.

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.