Overview

TripBuilder instances with high volume usage typically result in the creation of many itineraries daily. Some of them will be booked, others will not, and might pollute your instance (e.g., be listed in Customer Care). 

As time passes, the number of accumulated itineraries in planning would become substantial, impacting the daily operations of those involved in a valid or active planning process.

This article explains the existing automation in TripBuilder to avoid such itinerary accumulation.

Automatism for Itinerary Retention

The itinerary retention policy defines the retention phase for itineraries in the state In Planning.

Only itineraries are archived that are in status “In Planning” and have not been modified in any way for the number of days defined as “retention period”:

• The maximum retention period for itineraries is now set at 90 days.
• The default retention period for a new itinerary is 30 days.

An archived itinerary will no longer be accessible and will not appear in customer care search results.

Especially for B2C distribution channels, the number of created itineraries can be very high. Thus, as a rule of thumb, a B2C-oriented distribution channel should have a lower retention period (a few days), and a B2B-oriented distribution channel might go for a longer period of 30-90 days, depending on your users’ behaviours.

Support Statistics

Additional insights, considering data from all Nezasa customers for the period between January 1, 2023 and April 30th, 2025. The average time to book (creation to booking):

• Overall: 4 days (standard deviation: 17 days)
• B2C: 2 days (standard deviation: 11 days)
• B2B: 6 days (standard deviation: 19 days)

Setting up the Itinerary Retention Policy

TripBuilder administrator users can define the value for the Itinerary Retention Policy. The setting is available at the Distribution Channel level, in the Planner tab.