Importing Air from Your GDS

If you book air in a GDS, you don't have to retype any of it. Copy the booking out of your terminal, paste it into JourneyFuse, and the flights land fully built — in a proposal your client can accept, or on a trip where they're tracked with live flight status.

Works today with: Sabre (the *R, *IA, or *I itinerary display). Booking confirmations emailed by airlines and consolidators also import through the same flow.

Importing into a Proposal

This is the flow for "my client is choosing flights":

1. Open the trip → Proposal → AI Import
2. Pick the Paste tab
3. In Sabre, display the PNR (*R) and copy the whole readout — segments, name field, everything
4. Paste it in and click Extract
5. Review what came through, then Import

You get a Flight option with:

• Every leg as its own row — airline, flight number, airports, dates, and times, including overnight arrivals on the right day
• The passenger name from the PNR's name field, added to the trip's travelers
• The fare — if the PNR has been ticketed (an ACCOUNTING DATA line), the base fare and taxes pre-fill the option's pricing
• The record locator saved as the confirmation number

Paste two or three alternative PNRs and each becomes its own option — your client compares complete itineraries side by side and picks one, the same way they'd pick a hotel.

What the client sees

Flight options render like a booking site, not a data dump:

• An Outbound and Return summary — SLC 3:35 PM → LIM 5:00 AM +1, with connections collapsed into "2 stops (ATL 1h 46m, LIM 4h 30m)" including the ground time at each stop
• The airline names up top ("Delta Air Lines + LATAM Airlines")
• A route map as the option's cover image — the actual flight path drawn on a map — unless you add your own photos
• Full per-leg detail (plus a larger route map) behind View details

Importing into Trip Bookings

Prefer to track the air without putting it in a proposal? Same paste, different door: trip → Bookings tab → AI Import Booking. The booking is created with its flight segments, and JourneyFuse tracks live flight status and delay alerts from there.

What to Paste (and What Not To)

Paste the full PNR readout. The more of the display you include, the more we can extract — the name field, the segments, the ticketing and accounting lines all carry data.

A bare record locator won't work. A six-character code like ABCDEF is just a pointer to the reservation — it contains no flight data, so there's nothing to extract. Always paste the itinerary display itself.

Cancelled segments are skipped. Segments with status HX, UN, or UC are recognized and left out, so a PNR with schedule-change debris imports clean.

Tips

• Dates auto-fill. A flight option's start and end dates derive from the first departure and last arrival — you can override them anytime.
• Editing legs: every leg is editable after import. Type a flight number and click Auto-fill to look up airports and times for manually added legs.
• Pricing: raw PNRs that haven't ticketed usually carry no fare — just type the quote into Base Price. Remember fares aren't guaranteed until ticketed.
• Open-jaw itineraries (fly into one city, home from another) import fine; the in-between ground travel is yours to add as itinerary days.

Other GDSs

Amadeus and Travelport imports follow the same paste-and-extract approach and are on the roadmap — if your agency books on either, tell us at support and we'll prioritize it. In the meantime, the email confirmations those systems generate usually import well through the same AI Import flow.