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!

We've improved how markups are calculated for resellers using P2P. When determining which markup configuration to use we will now disregard the original source of the component.
​
This applies whether the P2P reseller or itinerary owner is in ‘reselling mode’ and directly contracting with a P2P seller or module owner. From the reseller's perspective, the relevant party is their direct commercial partner (the P2P seller) and the underlying source of the component is not relevant for markup calculations.

The supplier notification email for service categories has been updated to provide more accurate information. When a booking includes only one service category, the description will now include "(All Pax)" to clearly indicate that the service applies to all travellers.
​
When a booking includes multiple service categories, the email will now display passenger selection information if it is available for those categories. This provides a more precise breakdown of which passengers the different services apply to.
​
In cases where there are multiple service categories and no passenger selection information is available, the email will continue to display the service categories without the "(All Pax)" notation. This ensures that potentially incorrect assumptions about passenger allocation are not communicated to the supplier.

We've enhanced the local supplier notification emails for inventory transfer providers to include flight information to help with organising pick ups and drop offs.

The emails that will now include this flight information are for the local inventory transfer suppliers. Emails confirming a new booking (and booking requests) will be triggered and emails about booking changes/cancellations will be triggered if there has been a change/cancellation made to the transfer services.

Previously, these emails provided general information about transfer components. Now, if a transfer is related to a flight, the email will also include specific flight information:

This additional information provides local suppliers with more context regarding the transfer, improving communication and operational efficiency.

NOTE - operating carrier information is not sent to the supplier automatically on the email notifications - so for code-share flights where the marketing/booking carrier is different from the operating carrier it is important to continue to send this information manually.

Default activities that haven't been fully configured by the user will no longer appear in the Travel Summary document. Previously, these activities were listed, which could lead customers to believe they were already included in their itinerary and price, causing potential confusion. This update ensures that only fully adjusted and confirmed activities are displayed in the Travel Summary, providing a more accurate representation of the booked services.

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.