How post-confirmation changes work — Window to itrvl flow

Written By Itrvl Team

Last updated 20 days ago

Once a booking is confirmed and deposit has been received, the JS owns both Window and itrvl. This article explains how changes flow between the two systems at the post-confirmation stage and what the JS is responsible for in itrvl.

Also known as: post-confirmation updates, changes after deposit, confirmed booking changes, Window to itrvl sync, post-confirmation flow

The golden rule

All booking changes at the post-confirmation stage are made in Window first. itrvl reflects what Window produces — never make booking changes directly in itrvl.

The post-confirmation flow

Every change at this stage follows the same sequence:

  1. Make the change in Window — accommodations, routing, flights, services, or any other booking update

  2. Refresh the booking in itrvl — this pulls through the latest Window changes including updated supplier costs, margin, and sell price

  3. Check version history — confirm the change came through correctly and review the pricing impact

  4. Re-invoice if the price has changed — if the sell price has increased, update invoices to reflect the new amount

  5. Share the updated itinerary with the agent — if accommodations have changed, regenerate the video itinerary before sharing

What updates automatically in itrvl

Once a booking is refreshed, the following update automatically:

  • Supplier costs and sell price

  • Line items and routing on the itinerary

  • The client portal — the agent's existing link will reflect all changes

What requires a manual action in itrvl

ActionWhen required

Refresh the booking

Every time a change is made in Window

Regenerate the video itinerary

Only when an accommodation is added or removed

Update invoices

When the sell price increases after a change

Generate a separate invoice

When a new item needs immediate payment

What the JS does not do in itrvl post-confirmation

The JS does not add activities, services, or transit directly in itrvl. All of these changes happen in Window. itrvl is used post-confirmation for:

  • Verifying changes have pulled through correctly

  • Managing invoices and payment links

  • Sharing updated itinerary and video links with the agent

  • Downloading and sending documents

Important: If the booking is confirmed in Window, it must be unlocked in Window before changes will sync through to itrvl. If you have made changes in Window and they are not pulling through after a refresh, check that the booking has been unlocked first.

Related articles:

  • Refreshing a booking after post-confirmation changes

  • Re-invoicing when a change affects the price

  • Regenerating the video itinerary

  • Generating a separate invoice for immediate payment

  • Sharing updated itinerary and video links with the agent

Should you notice any issues in this process, please reach out to itrvl support.