October 13th, 2026 | TripBuilder Release Notes v383

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!

When an inventory component is booked on request, TripBuilder now tracks whether the supplier confirmed it or could not fulfil it, instead of leaving it showing as "On Request" indefinitely. A component the supplier can't confirm shows clearly as ‘Failed’.

For local suppliers we email directly upon booking, the on request email can now include ‘Confirm’ and ‘Reject’ actions for each component, with no login needed. A supplier who confirms can add the confirmation number. A supplier who rejects can add a note with what is available instead, such as alternative dates, room categories or prices. As soon as a component is confirmed or rejected the status of the component is updated in TripBuilder.

When a new setting is enabled, The tour operator is emailed automatically, one email per component, to inform them of the component being confirmed or rejected by the local supplier. If the component was confirmed the status is set to ‘Booked’ in TripBuilder. If it was rejected the status will be set to ‘Failed’ and the tour operator would then follow any guidelines given via email by the supplier to attempt to rebook an alternative service. For example, trying alternate dates or a different room category via a booking change.

We've added a new setting that adds the Confirm and Reject actions to the on request email sent to your local suppliers, and the tour operator notifications are switched on in the same checkout email notification settings (DC Settings - Checkout). If you enable it, disable the existing on request email without actions so suppliers don't receive duplicate requests. The same on request emails are now also sent when an on request accommodation is added through a booking change.

Editing a flight in Customer Care no longer shifts the departure by an hour or changes the arrival unexpectedly, because times now use the airport's own timezone. Transport edits also show the correct arrival date and no longer trigger a false "Departure after Arrival" error.

Editing the net rate of a multi-segment activity no longer fails with "activity cannot be updated". The save previously failed whenever the product's segment list had changed since booking, so the new price was never stored.

You can edit the net price of a hotel component in Customer Care to align costs with what you are charged after booking, without changing the sales price. Until now this feature did not include hotel components with priced extras such as breakfast (amenities) because the edit overwrote the original price and cleared the extras.

We've redesigned how these edits are stored. A net price change is now kept as a correction on top of the supplier price, so the original cost and the extras stay intact and the pricing calculation stays accurate.

Net price editing also extends from inventory to live supply hotel components. We also record net price changes over the life of a booking, including the net price at confirmation and the markup before and after each change. Please ask your Nezasa support to enable the feature as required.

The default duration setting now correctly applies to the package search bar.

When TravelgateX returns a gateway timeout, we no longer treat the hotel as "not available". The outcome is now unknown, so a booking that did go through at the supplier is not left invisible and uncancellable.

Previously the component failed, the payment authorisation was cancelled and the supplier reference was lost, which led to a no-show charge from the supplier.

We fixed booking changes for HolidayTaxis transfers that were found through the area-based search fallback. These offers carried hotel references that did not match what HolidayTaxis expected, so the change failed and left the transfer stuck in "Open".

Musement activities with pickup or drop-off options now return availability faster. TripBuilder confirms that at least one pickup or drop-off point is available instead of loading every option, so searches complete without timing out and your team can offer and book these activities without delay.

NTP-70549

A Restel booking made through TravelGateX was placed at a different hotel in another country from the one sold and shown on the voucher. TravelGateX was still using an outdated copy of our Restel hotel mappings, because the up-to-date mappings were no longer reaching the location TravelGateX reads them from.

Up-to-date hotel mappings are now exported to TravelGateX again, so Restel bookings go to the hotel the traveller chose.

NTP-70082

When the connection to TBO dropped after a booking request had been sent, we marked the hotel as Failed even though TBO had confirmed it. This left a booking at the supplier that TripBuilder didn't show, with a risk of booking the same hotel twice.

In this case we now set the hotel's status to unknown and flag it for checking, instead of marking it as Failed. This applies to all hotel suppliers connected through the Connect API.

NTP-70102

Some rental car pictures from Sunny Cars showed broken images in the rental car list, mainly for cars whose picture file name contains spaces, such as "Toyota Yaris 4dr". All vehicle pictures now load.

NTP-70240