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 added image carousel functionality to hotel property cards in search results. Previously, users could only see a single static image per hotel and had to click through to the detail page to view additional photos. Since we already had three images available for each property, this required unnecessary navigation steps just to browse hotel photos.

Hotel cards now display left/right arrow navigation overlays that let users browse through three available images directly on the property card. This helps users make more informed decisions without leaving the search results page.

We've standardized destination descriptions across all destination cards to create a consistent, professional browsing experience. Previously, descriptions varied wildly from 20 to 65 words, causing layout issues with text truncation, inconsistent card heights, and poor visual balance across the destination grid making it difficult for users to quickly scan and compare options.

All destination descriptions now follow a consistent 20-25 word format focusing on geographic context and key defining characteristics. Each description provides specific, actionable information like exact locations (e.g., "Yucatan Peninsula, Mexico"), unique features (e.g., "desert landscapes meet Caribbean beaches"), and notable islands or regions within destinations. This eliminates truncation, creates uniform card heights, improves scannability, and delivers more valuable information to travelers comparing destinations.

Flight searches can automatically select the optimal airport when areas have multiple nearby airports. This reduces search failures with suppliers that don't support multi-airport queries (AerticketHub).

Key features:

Configuration:

Data Improvements:

Related articles: Area Management, Transport Search and Filtering

Fixed an issue where transit activities in the Planner map incorrectly displayed airplane icons instead of the actual transport type (bus, train, car). The map now shows the correct transport icons for each segment of the journey, matching what customers see in Discovery.

Additionally, the Planner map experience has been aligned to the one in Discovery:

The email notifications settings in distribution channel checkout configuration are now available to all customers.These settings allow you to control which email notifications are sent for booking confirmations, booking changes, cancellations, and PAX updates—and to whom (Customer/Agency, Tour Operator, Local Supplier, Inventory Owner).

For documentation, see: Email Notifications Help Article.

All timeout configurations are now configurable via environment settings. Most importantly, ConnectApi Transport integrations including AerticketHub now support up to 80 seconds for external integrations instead of the previous 60-second limit, reducing false timeout failures when suppliers need extra processing time. Existing behavior is preserved through a feature flag allowing supplier-specific adjustments.

We've fixed a booking error that occurred when a child's birthday falls during a trip. Previously, the system inconsistently calculated child ages - sometimes using the itinerary start date and sometimes using each accommodation's start date. When a child had a birthday between hotel stays, this mismatch caused the error "Unable to allocate child with age X or corrected age Y into room Z" and prevented successful bookings or retries.

The system now consistently handles age calculations when children have birthdays during their vacation. Whether a child turns 6 or 7 between accommodations, the booking process correctly allocates them to rooms without errors. This eliminates booking failures and the need for manual intervention when travellers celebrate birthdays during their trip.

We've fixed the "Remove All Flights" action in Customer Care Cockpit to work with multi-city flight configurations. Previously, this action was only available when at least one flight was classified as Inbound or Outbound, which meant itineraries with only multi-city flights couldn't use the removal feature. This created confusion because the action name suggested it should work for all flight types.

The action now correctly displays whenever at least one flight is not a placeholder, regardless of whether flights are Inbound, Outbound, or multi-city. This means you can now remove multi-city flight configurations just as easily as traditional round-trip flights, making the feature work as its name suggests.

We've changed how we bundle accommodation bookings to improve accuracy and reduce false failures. Previously, when booking multiple accommodations from the same supplier, the system would wait for all bookings to complete before returning a result. If any single booking took too long or failed, the entire bundle was marked as failed - even if some hotels had successfully booked. This created confusion, potential financial losses, and required manual intervention to correct the statuses.

Now we only bundle accommodations that belong to the same hotel. This means if you're booking seven different hotels from the same supplier and one times out, only that specific hotel shows as "Open" while the other six correctly display as "Booked". This change provides more accurate booking statuses, reduces unnecessary cancellations, and minimizes the need for manual corrections.

We've improved the hotel filter display in Content rules to help you configure rules more accurately. When selecting hotels in the Rule Hotel Filter, you'll now see the hotel name followed by the area name in brackets, and inventory properties will be clearly marked with an "- Inventory" label. This brings back functionality from the previous rule configuration that was temporarily missing.

This update makes it easier to identify the right hotels when setting up rules, especially for teams managing multiple properties across different areas.

Added configuration option to hide the default room allocation message about group inquiries and children's extra beds. Available only when Child Support is disabled, this allows customers who don't serve families to remove child-related messaging from their booking flow for improved clarity and brand consistency.

Rental car exclusions (such as one-way fees, young driver surcharges, and deposit requirements) are now displayed in the Traveler Registration document. Previously, these exclusions were only visible in the Travel Docs. This improvement ensures travelers have complete visibility of all rental car terms before confirming their booking.

Improved area search accuracy for AI-powered trip planning (Planner Copilot). When the AI suggests destinations with variant spellings or word splits (e.g., "Ko Pha Ngan" instead of "Ko Phangan"), the system now correctly identifies the intended location using fuzzy string matching. This applies to the from-prompt and from-scratch itinerary APIs.

Remark: Planner Copilot uses the same API endpoints and therefore, will profit from this improvement too.

We've enhanced the Booking API to explicitly identify products that are 100% non-refundable, particularly flights. Previously, while the API provided general tiered cancellation policies through purchaseCancellationFees, it didn't clearly indicate which specific products had no refund option. This made it impossible for integration partners to accurately communicate cancellation terms to customers, creating potential legal and financial risk.

The API now returns indicators for non-refundable products including productId, productType, description, cancellationFee, and feeType. This allows clients to understand exactly which items (like specific flight segments) cannot be refunded.

We've added structured product fields to the Booking API for generic ad-hoc, activity, accommodation, transfer, and base service components. Previously, information like titles and descriptions were concatenated into a single description field separated by commas (e.g., "Safari Adventure, Premium Package"). Since commas can appear within titles themselves, API consumers couldn't reliably parse this data back into separate fields, causing issues with invoice layouts and text formatting requirements.

The API now returns dedicated fields including productName, categoryName, title, description, shortDescription, categoryDescription, and additionalInfo depending on component type. For example, generic ad-hoc components now expose separate title and description fields instead of forcing consumers to parse concatenated text.

We've added structured location fields to transfer components in the Booking API. Previously, departure and destination information was combined into a single description field. Since arrows, hyphens, and other delimiters can appear within location names themselves, API consumers couldn't reliably split this data back into separate fields needed for proper transfer documentation.

Transfer components now return dedicated departureDescription and destinationDescription fields alongside the existing combined locationDescription field.

The checkout API now returns Terms and Conditions, Booking Terms 1 and 2, Entry and Health Regulations, EU-PRRL - Terms and Visa Regulation Links, and a Payment Explainer in the response. This enables clients to display essential regulatory and informational content in their user flow.

We've added support for per-passenger questions when booking activities through the Connect API. Activity providers can now configure questions to be answered individually for each traveler, rather than just once per booking. When an activity requires passenger-specific information, the system automatically creates separate questions for each traveler with their name clearly displayed.

This enhancement enables you to collect detailed information like dietary restrictions, accessibility needs, or equipment preferences for each person in your group.

We've added room allocation capabilities for multi-day tours sourced from live suppliers, enabling accurate pricing based on how travelers are distributed across rooms. Tour suppliers can now offer multiple room configuration options with specific pricing for each setup, such as single rooms, double rooms, or triple rooms.

The system clearly displays pricing per room type and warns you when changes affect the total cost, making it easier to help customers find the arrangement that best fits their needs and budget.

Hotel addresses in Japan and other non-Western countries now display correctly across all TripBuilder views (Travel Documentation, but also Planner). Previously, addresses in regions that don't use traditional street-based formats (like Japan's hierarchical address system) appeared incomplete or duplicated (e.g., showing "1-19 1-19" instead of the full address).

Remarks:

We've improved how TripBuilder handles flight searches with the Peakwork supplier by implementing connection limit validation. The system now automatically skips Peakwork API calls when searching for flights with more than 2 connections, since Peakwork doesn't support these complex itineraries. This change eliminates approximately 5,000 unnecessary API calls every 15 days that were previously generating validation errors.

This optimization reduces log noise and improves response times for flight searches without any impact on your ability to search for and book complex multi-connection flights. Alternative suppliers like AerTicket Hub continue to handle these itineraries seamlessly.

We've corrected the meal plan mappings for Hotelbeds accommodations to ensure accurate display of what's included with each booking. Previously, certain meal plan codes were either missing or incorrectly mapped, causing bookings that included meals like dinner to incorrectly display as "No Meals." The system now correctly recognizes and displays all meal plan types, including dinner-only options, breakfast and dinner combinations, and other board configurations.

Agency Dashboard - Hide GDPR Checkbox of “Send to Customer” Action

To hide the GDPR checkbox, simply remove all label texts at Settings → Distribution Channel → General → GDPR → GDPR Checkbox.

Seed Data - Airline Updates

Updated logo and/or data of the following airlines: CS, OM, NM, FH, BY, TS, N0.

Seed Data - Countries Kosovo and North Macedonia

Updated translations and labels for countries Kosovo (XK) and North Macedonia (MZ).

Generic Ad-Hoc Activities Title Length

​​The generic ad-hoc component title field now supports up to 100 characters (previously 40). This aligns it with other product types like accommodations and activities.

Help Widget - Unread Messages of Closed Tickets

The imported tickets were originally created as “unread” which made the little red dot of the help widget unreliable. On Dec 3, 2025 we ran a script to mark all tickets as read that were in status close to address this issue.

Travel Agency Logo Deletion

Improved Travel Agency logo deletion use case. Users can now delete logos successfully even if metadata is missing in the database.

Emails to Agencies - Language Handling Improvement

When travel agent users had no language preference configured, agency emails (booking change confirmations and cancellation confirmations) were being sent in the system default language (English) instead of the agency's preferred language. This improvement ensures that when an agent user has no language set, they inherit the language from their travel agency for email communications.

New labels to support German with Du

We’ve introduced a new German (Informal) language option to help you better connect with students and young travelers. By replacing the formal "Sie" with the friendly "Du" across all labels, buttons, and notifications, you can now deliver a more approachable and brand-aligned experience. This new setting (de-informal) is available now in the Cockpit and can be toggled directly within the user interface.