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 email: [email protected]
Via support portal: https://support.nezasa.com/
Via BucketList: Available in TripBuilder's Cockpit at the Resource Centre
.DISCOVERY
Fixed Multi-City Flight Search Segment Filtering
Resolved an issue in multi-city flight search where selecting multiple segments in the results filter caused no flights to be displayed and did not allow users to revert the filter. The filtering logic now correctly shows only flights containing the selected segment(s), and users can clear filters to return to the full results list.
.PLANNER
Aerticket’s flight results categorisation
We've simplified the flight search experience by consolidating all flight results into a single "Flights" tab. Previously, flights from the supplier Aerticket hub could appear under separate categories like "Multiple One-Way Flights" and "Return Flights," which created confusion. Now all flight options are displayed together in one unified view.
.COCKPIT
New Content Rules (BETA)
Content Rules - Supplier Exclusion Fix
We've resolved an issue where content exclusion rules for suppliers were not being applied correctly. Supplier exclusion rules now work as intended, ensuring that when you exclude a supplier, their content will no longer appear in your travel search results, even with combined with other rules (as Country/Area or Hotel Names). This gives you better control over which suppliers and content are displayed to your customers.
Enhanced UI for Country & Area selection
We've enhanced the user interface for creating content rules by improving the selection experience for areas, countries, and hotel filters. You can now select multiple options within the same rule definition, use search functionality to find specific locations or hotels, and view your selections displayed as easy-to-manage chips. This streamlined interface makes it simpler to create comprehensive content rules that target multiple geographical areas or specific accommodations in a single rule configuration.
Cancellation Policy Rule enhancement
We've enhanced the cancellation policy filtering options in content rules to provide more granular control over offer selection. You can now define rules to include or exclude offers based on their refund policies: Non-Refundable offers (those with 100% charges from the moment of booking) and Partially Refundable offers (those with cancellation charges that don't equal the full offer price). This enhancement gives you better control over which types of booking policies are presented to your customers.
New Agent Booking Change Completion Request System
We've introduced a new notification system that addresses communication gaps between agents and tour operators during booking changes, while respecting individual tour operator notification preferences.
This adds a new email type specifically for agent-initiated booking changes that require tour operator completion, separate from existing booking change confirmation emails that are sent after changes are finalised.
The system now provides two distinct experiences based on tour operator settings:
When notifications are enabled in settings (contact your support team for this): Agents see a 'Request Change' button at checkout that automatically sends a new "Agent Booking Change Completion Request" email to tour operator administrators, including the agent's name, itinerary link, and clear indication that a booking change requires completion. Agents receive confirmation that "An automated mail was sent to the TO, you'll be contacted shortly."
When notifications are disabled: The system recognizes that automated emails aren't wanted and instead displays a clear message directing agents to "Please contact your Tour Operator offline to complete the booking change," ensuring no unwanted emails are sent.
This enhancement adds a new communication channel between agents and tour operators while preserving all existing booking change email workflows, eliminating confusion about pending changes and enabling faster response times when automated notifications are desired.
Added "Open" Status Filter for Components Tab
We've enhanced the Components tab filtering functionality by adding a new "OPEN" status option to the sidebar filter section. Previously, users couldn't easily identify and isolate components that had associated issues or problems, making it difficult to efficiently resolve multiple related cases that required attention.
The Components tab now includes an "OPEN" filter option in the status section that displays only components with open status, allowing Customer Care users to quickly identify components requiring resolution. This filter is available for all Customer Care user roles.
This enhancement streamlines the component management workflow by enabling users to focus specifically on components that need attention, reducing time spent searching through all components to find those requiring action. Customer Care teams can now efficiently prioritise and address open issues across their component inventory.
View of discarded checkouts using Customer Care Order History
We have added the ability to view discarded checkouts and their orders in the Customer Care Order History page. By default, the discarded checkouts are not displayed: the user has to check the “Include Discarded” checkbox to see them. This allows users to view the complete history of a booking, including discarded booking changes, which may have included already booked and/or cancelled components.
Furthermore, we have removed the checkout numbering and replaced it with internal links for easier navigation from a checkout in the checkouts list to its details.
Commission Calculation on Negative Price Components
We've added the ability to calculate commissions on ad-hoc components with negative sales prices, such as price match discounts, addressing a gap where tour operators couldn't properly track commission impacts of discounts. Previously, TripBuilder only calculated commissions on components with positive sales prices, meaning discounts applied through negative-value ad-hoc components weren't factored into agent commission calculations.
A new feature flag "calculateCommissionsOnNegativePrice" allows administrators to enable commission calculation on generic ad-hoc components with negative sales prices. When enabled, the system applies the standard commission percentage to negative-price components, resulting in negative commission values that accurately reflect the discount's impact on agent payouts. The feature flag is configurable in Distribution Channel settings under the Commissions section and defaults to false to maintain existing behavior.
If the total commissions across all components is negative due to negative commissions on generic ad hoc components, then the negative commissions on those generic ad hoc components is adjusted such that the overall commissions become zero instead.
This enhancement provides tour operators with accurate commission tracking when applying price match discounts or other negative adjustments, ensuring commission calculations reflect the true impact of all itinerary components, both positive and negative, on agent compensation structures.
Fixed Amenity Count Display in Transfer Supplier Notifications
We've corrected the amenity count display in supplier notification emails for transfers where amenities were incorrectly shown as per-passenger instead of per-group. Previously, group-based amenities like rental cars on car ferries were being multiplied by the number of passengers, causing confusion for suppliers who would see "2 rental cars for 1 passenger" instead of the correct "1 rental car for the group."
The system now properly distinguishes between group-priced and per-passenger amenities in supplier emails. For group-priced amenities, the email displays "All pax" to indicate the amenity covers the entire group. For per-passenger amenities, the system uses the pricing multiplier to determine the correct passenger count - if the price matches one amenity unit, it shows "1x pax", if double the price, it shows "2x pax", and if it matches the total group price, it displays "All pax".
This fix ensures suppliers receive accurate information about amenity quantities and passenger coverage, preventing confusion about service requirements and enabling proper preparation for group bookings with shared amenities like vehicle transport on ferries.
.DOCUMENTATION
Knowledge Base - Double Booking Prevention Guide
Booking failures can occur from time to time and it is important that users understand something has gone wrong and how to react to the problem they face.
While we continue to work on reducing failure rates, both by supply and integration solutions and booking rescue tools, it is also really important our users know when to reach out for support to avoid financial loss due to double or missed bookings. This new article should make it clear where things have gone wrong, and we have more in depth articles available too for further support on rectifying booking issues. Please check the new article here.
.APIs
Timing Details in Cancellation Policy Rules
The Planner API now returns precise date and time information for when cancellation fees apply. We added new startDateTime and endDateTime fields to the cancellation policy rules, while keeping the existing date-only fields for backward compatibility.
Booking API Extensions
The booking API now includes the "isAdhoc" property for all product types, including hotels, enabling better management and differentiation of ad-hoc products.
We've enhanced the Booking API to support package differentiation by adding key data points that API consumers need to determine package types. Previously, API consumers couldn't easily identify whether bookings qualified for certain packages without manually parsing complex itinerary data.
The Booking API now includes the departure airport IATA code extraction and provides counts of unique services by service type (accommodation stays, activities, transfers, etc.) in the response. This enables API consumers to implement their business logic to determine a package type based on the combination and number of different service types included.
The Booking API is extended to support retrieval of card token/payment details from Datatrans payments when requested by the ‘include=payment-info’ parameter on booking fetch endpoints.
A new cardInfo object is included in PaymentTransaction, allowing downstream integration with partner integrations and accounting systems. No change is required to the payment flow or existing booking/payment logic.
