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 overhauled our booking component status system to give Customer Care users more accurate information about booking outcomes and align the email notifications generated for booking failures with Customer Care component statuses.

The previously generic "Open" status has been replaced with three specific statuses: "Failed" for confirmed booking failures, "Unknown" for timeout or unclear outcomes, and "Open" solely for cases where a booking attempt has not yet occurred.

These new statuses are now filterable in the Customer Care component list, making it easier for agents to quickly find and address bookings that need attention.

We added module visualisation to the Customer Care services & prices tab. You can now view all module components and their pricing details directly within the services and prices list, alongside margin by product category.

We fixed an issue where transport booking failures through our sourcing service only stored a generic error message in the booking audit. The audit now captures the detailed error returned by the supplier, including specific failure codes and descriptions.

This makes it significantly easier for support and operations teams to diagnose and understand transport booking failures.

We introduced a new "confirm the cancellation manually" action for itineraries in Customer Care. When a cancellation fails due to an API or supplier issue and the booking is cancelled offline, users can now update both itinerary and component statuses directly in the platform to reflect the actual cancelled state.

This removes the discrepancy between the platform status and the true booking status that previously occurred after failed cancellations resolved offline. The action does not trigger any supplier API calls and has no impact on cancellation calculations.

We fixed an issue where booking change failure notification emails were not sent when a component failed to cancel during a booking change with the cancellation failure flag enabled. The system now correctly sends failure emails to tour operators and marketplace operators regardless of feature flag state.

Previously, only the component-level cancellation failure email was sent, leaving customer care teams without the booking-change-level context. Both emails are now sent consistently, ensuring operational teams have full visibility to follow up on failed booking changes.

We enhanced the global recommended hotels feature with multi distribution channel capabilities, giving you fine-grained control over hotel recommendations across different distribution channels. You can now create separate recommended hotel lists for each distribution channel, allowing you to tailor hotel strategies based on your audience and business model.

Combined with an improved management interface, this capability transforms basic hotel recommendations into a sophisticated, channel-aware recommendation engine that maximizes conversions while respecting your business preferences.

This feature is not available by default. To enable it, please contact our Customer Support team

This release aligns the public API with the backend by adding four new booking statuses (ToBeVerified, Option, Failed, Unknown). The inline availability-status enum has been refactored to reference the shared BookingStatus schema, reducing duplication. A new consistency test will catch enum mismatches in CI.

Note: As this API is in BETA, these non-backward-compatible changes are acceptable and require client updates to handle the new statuses.

We improved the accuracy of transfer bookings by sending exact hotel geocoordinates to transfer suppliers instead of generic area-level coordinates. When you book transfers with hotel pickup or dropoff locations, the system now transmits the specific hotel's geocoordinates to suppliers, ensuring drivers receive precise location information for accurate service delivery.

This enhancement eliminates location ambiguity that previously caused operational issues with transfer fulfillment. Transfer suppliers now receive the exact coordinates for each hotel, enabling more reliable pickups and dropoffs while maintaining the existing functionality for airport transfers using IATA codes. The improvement works seamlessly across all transfer booking scenarios, including hotel-to-airport, airport-to-hotel, and hotel-to-hotel transfers.

We added support for quantity-limited inclusions on rental car equipment, allowing suppliers to offer packages where a specific number of items are included free and additional units are charged. This enables accurate pricing for packages like Alamo's Gold Static, which includes one free child seat and one free ski rack, with additional units available at an extra cost.

Previously, the system only supported two modes for equipment pricing: all units free or all units paid. This enhancement introduces a third mode that handles the common supplier pattern of including a limited number of units in the base package. The system now correctly calculates pricing by charging only for units beyond the included quantity, displays the included quantity in package details, and provides clear pricing breakdowns showing which units are free versus paid.