Skip to main content

July 8th, 2026 | TripBuilder Release Notes v376

Written by Product Management

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!

Customer Care

Post booking component editing for flights

Customer care users can now update certain flight component attributes (location, dates, time, PNR, carrier, flight number) on a booking through an editing screen access from the service and price table, without cancelling and rebooking.

These changes update the flight component itself but don't propagate to external systems, and are designed for 'cosmetic' corrections so customers can ensure their platform data and travel documentation is accurate (internal or external via Booking API). It is not a method of syncing the attributes of the component with the flight supplier.

A good example of using this feature would be an airline informing the travel opreator of a flight time change. This change has already being confirmed in the flight system but means the booking platform data is out of date. The new editing allows the time of the flight to be adjusted so travel documentation can be updated, without performing a full cancel and rebook.

This feature is a Beta release that we continue to work on. Please pass on any feedback via your support team whilst we work on the full release. The editing screen needs to be enabled by Nezasa so please contact your support team for this. A pencil icon will then appear on the service and price list for live supply flights and clicking this will open the editing modal.

Per-Leg Editing — Each flight leg can be individually updated:

  • Departure and arrival dates and times

  • Departure and arrival airports

  • Carrier and carrier (flight) number

  • Operated-by carrier

  • Travel class

Component-Level Editing:

  • PNR

  • Fare type

  • Supplier name

  • Supplier confirmation number

  • Ticketing deadline (Ticketing Until)

  • Net price (visible to tour operators only, does not impact sales price and will impact component markup)

View-Only Fields — Displayed for reference but not directly editable:

  • Sales price

  • Booking status

  • Booking system

  • Currency

  • Start and end locations (auto-update based on segment changes)

Audit Trail — All edits are recorded and visible in the itinerary history on the Overview tab.

Travel Document Sync — Updated flight details automatically regenerate travel documents.

Booking API — Changes pass through to the Booking API, keeping downstream integrations in sync.

Not Included in This Release:

  • Ad-hoc (offline) flight components

  • Sales price editing

  • Tax and fee fields

  • Baggage information

  • Internal ticketing

  • Adding or removing legs

  • Adjustments to related components - this has to be checked and handled manually.

Did this answer your question?