Refreshing a booking after post-confirmation changes

Written By Itrvl Team

Last updated 20 days ago

When changes are made to a confirmed booking in Window, itrvl needs to be manually refreshed to pull those changes through. This article covers how to do that and what to check once the refresh is complete.

Also known as: pulling through changes, syncing the booking, updating itrvl, refresh quote, post-confirmation update

When to refresh

Refresh the booking in itrvl any time a change has been made in Window at the post-confirmation stage. This includes:

  • Accommodation changes

  • Routing or transit updates

  • Services or activities added or removed

  • Night changes

  • Regional flights added

Always refresh before checking pricing, sharing the itinerary with the agent, or updating invoices.

How to refresh

  1. Open the booking in itrvl.

  2. Click the three dots (⋯) at the top of the booking.

  3. Select Refresh Quote.

[SCREENSHOT: Show the three dot menu with Refresh Quote highlighted]

  1. Wait for the refresh to complete — you will see a loading animation while itrvl pulls through the latest changes from Window.

What to check after refreshing

Once the refresh is complete, go to the History tab to confirm your changes have pulled through correctly and review the pricing impact.

[SCREENSHOT: Show the History tab with a post-confirmation change entry]

Check the following:

  • The change you made in Window appears in version history

  • Supplier cost and sell price have updated correctly

  • The % invoiced indicator in the cost summary reflects the new sell price — if it has dropped below 100% you will need to update invoices

See: Re-invoicing when a change affects the price

Important: If your changes are not appearing after refreshing, check that the booking has been unlocked in Window first. Confirmed bookings must be unlocked before changes will sync through to itrvl.

Note: Numbers will sometimes look different between Window and itrvl due to Window's single currency invoicing applying a time-based FX buffer. This is expected and not an error.

Related articles:

  • Re-invoicing when a change affects the price

  • Reading version history and supplier cost lines

  • How post-confirmation changes work — Window to itrvl flow

  • Generating a separate invoice for immediate payment

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