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!

By ticket: https://support.nezasa.com/hc/en-gb/requests/new

By email: [email protected]

Via support portal: https://support.nezasa.com/

Via BucketList: Available in TripBuilder's Cockpit at the Resource Centre

We have introduced live destinations for Dynamic Packaging. Operators can now configure destinations that are not pre-cached, making them available for visitors to select and book through the Smart Planner. This removes the previous ceiling on the number of destinations an operator can offer without increasing caching costs.

Both cached and live destinations appear in the same destination dropdown. Cached destinations show the "Popular" badge and the familiar priced calendar and hotel cards. When a visitor selects a live destination, a simplified date picker is shown instead. After selecting travel dates, the visitor is taken directly into our Smart Planner with a pre-built itinerary and the ability to add flights, hotels, activities, transfers and proceed to checkout.

Feature flag controlled - contact support to enable ‘liveDestinations’ for your organisation.

Two new distribution-channel-level settings have been added to Smart Planner:

**Flight price display** - Customers can now choose how flight prices are shown to travelers. Four display modes are available: absolute per person, absolute total, relative per person (difference from cheapest), and relative total. Previously, prices were always shown as absolute per person.

**Flight removal policy** - A new setting allows customers to prevent travelers from removing flights from an itinerary. When disabled, both "Remove Flight" and "Remove All Flights" options are hidden. The "Change Flight" button remains unaffected.

These are NZ-only settings. Customers should contact their Nezasa representative to activate or change them.

A new distribution-channel-level setting allows customers to globally disable the add/remove stops feature in Smart Planner. Previously, this could only be controlled per template. When disabled at the channel level, no itinerary — whether template-based or not — will allow adding or removing stops. The per-template setting continues to work independently; both must be enabled for the feature to be available.

This is an NZ-only setting. Customers should contact their Nezasa representative to activate or change it.

The rental car selection drawer in Smart Planner now clearly displays cancellation policies for every offer. Previously, cancellation information was not visible when browsing rental car options, requiring users to select an offer before seeing its policy.

This is an NZ-only setting. Customers should contact their Nezasa representative to activate or change it.

Fixed a critical issue where removing all optional activities one by one would block the checkout flow with a "check your activities" message. Since there were no activities left to check, users were stuck in a loop with no way to proceed. The validation now correctly handles the case where all optional activities have been removed.

Unadjusted Musement activities now display a warning message in travel proposals and summaries when tickets have not yet been selected in the planner. The warning appears beneath the activity title and reads: "This activity is not included in the price until tickets have been added via the planner."

Previously, these activities appeared in travel documentation as though they were part of the itinerary, but their costs were not included in the total price. This caused confusion for customers who assumed the activities were confirmed and priced. The warning is automatically removed once tickets are properly configured.

Payment partners can now reflect an intermediate processing state in TripBuilder while asynchronous payment logic completes - for example, when coordinating between a frontend and a PSP before final closure. PATCH endpoint now accepts InProgress as a valid status transition, removing the previous 400 validation error.

Supported transitions: Open → InProgress, InProgress → Closed, and Open → Closed

All other statuses remain system-managed - no change to existing lifecycle behaviour. This gives payment integrators the flexibility to reflect real processing states without working around the API, and aligns TripBuilder's transaction lifecycle with external payment logic.