Multi-City vs Round-Trip PNR: How to Read the Difference

At a glance, a multi-city PNR and a round trip can look similar — both have multiple segments. The distinction matters for fare construction and for correctly explaining the itinerary to a client, so here's how to tell them apart quickly.

What Makes a Round Trip

A round trip is simple: the passenger flies from City A to City B, then back from City B to City A. The final destination equals the original origin.

1  BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P
2  BA 117 H 22JUL 2*JFKLHR HK1  600P 605A/23JUL

Segment 1 goes LHR → JFK. Segment 2 goes JFK → LHR. Same two cities, reversed — a straightforward round trip.

What Makes a Multi-City Itinerary

A multi-city (or "open jaw" in some cases) itinerary involves different city pairs across segments — the passenger doesn't simply retrace their outbound route.

1  BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P
2  AA 100 H 20JUL 1*JFKLAX HK1  800A 1105A
3  BA 269 H 25JUL 3*LAXLHR HK1  700P 105P/26JUL

Here, the passenger flies LHR → JFK, then JFK → LAX, then LAX → LHR. Three distinct city pairs, only returning to the original origin on the final segment — this is a multi-city trip, not a round trip.

Why the Distinction Matters

• Fare construction — multi-city itineraries often price very differently from a simple round trip, sometimes as separate one-way fares combined
• Client communication — describing a 3-city trip as a "round trip" to a client is confusing and can cause them to misunderstand their own routing
• Layover vs. stopover confusion — a multi-city segment gap is a deliberate destination, not a connection, and shouldn't be flagged as a "layover" the way a same-day connection would be

Circle Trips: When Multi-City Still Returns Home

The multi-city example above ends back in London, which raises a fair question: if it returns to the original origin, why isn't it a round trip? The answer is in the number of distinct city pairs, not just the start and end point. A round trip only ever involves two directions between the same two cities. The moment a third city enters the routing — LAX in that example — it stops being a simple there-and-back, even though the passenger eventually lands where they started. Agents sometimes call this specific shape a "circle trip": a multi-city itinerary that happens to close the loop.

The distinction isn't just academic. A circle trip is still typically priced as a set of combined one-way fares or a dedicated circle-trip fare construction, not as a standard round-trip fare — which means the total can look very different from what a client expects if they're picturing a simple "there and back" price.

Open-Jaw Itineraries: Different Departure or Return City

An open jaw sits between a round trip and a multi-city — the passenger flies into one city and, after time on the ground, departs for home from a different city, with no flight booked to connect the two. It's common on road-trip-style itineraries: fly into one city, drive around, fly home from somewhere else entirely.

1  BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P
2  AA 850 H 22JUL 1*BOSLHR HK1  600P 605A/23JUL

Here the passenger flies LHR → JFK, but flies home from Boston, not New York. The gap between JFK and BOS is deliberately not part of the ticket — the passenger is expected to make their own way between the two cities, most likely by car or a separate short domestic flight. Reading this correctly matters: telling a client "your return flight is from JFK" when it's actually from BOS is the kind of mistake that gets discovered at the worst possible moment, at the airport.

One-Way Bookings: A Third Shape Entirely

Not every PNR has a return leg at all. A one-way booking is exactly what it sounds like — one or more connecting segments in a single direction, with nothing coming back. These are increasingly common with one-way fares now priced competitively on many routes, rather than always being a last-resort option.

1  DL 45 H 10SEP 1*ATLLHR HK1  945P 1105A/11SEP

A converter (or an agent scanning by eye) needs to recognize that the absence of a return segment is a valid pattern, not a missing or incomplete booking — otherwise every legitimate one-way sale ends up flagged as though something got left out.

Reading Segment Gaps: Layover, Stopover, or New Destination

The time between two segments in a PNR can mean three very different things, and mixing them up leads to confusing client communication:

• Layover — a short gap at a connecting airport, typically under a few hours, where the passenger doesn't leave the airport.
• Stopover — a longer planned gap (often defined as 24+ hours on an international itinerary) at a city the passenger intends to actually visit before continuing on the same overall ticket.
• New destination (multi-city) — the gap isn't a connection at all; it's a distinct leg of the trip with its own dates, as in the LHR-JFK-LAX-LHR example above.

Getting this label right when explaining an itinerary to a client isn't cosmetic — a "layover" implies staying near the airport, while a "stopover" or a new destination city implies the client should actually plan for that time on the ground.

Booking Class Can Legitimately Differ Across a Multi-City

On a standard round trip, agents get used to seeing the same booking class on both directions, since the whole thing is usually priced as a single round-trip fare. Multi-city itineraries break that pattern in a way that's easy to misread as an inconsistency rather than the normal outcome of how the fare was actually built.

1  BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P
2  AA 100 K 20JUL 1*JFKLAX HK1  800A 1105A
3  BA 269 M 25JUL 3*LAXLHR HK1  700P 105P/26JUL

Three segments, three different booking classes — H, K, and M — on the same passenger, same overall trip. Because a multi-city itinerary is frequently priced as separate one-way fares stitched together rather than one unified fare, each leg can be sold in whatever class had availability at the time, independent of the others. That's normal, not a red flag — but it's worth confirming each segment's fare rules individually, since baggage allowance, change fees, and refundability can all vary leg to leg in a way they typically wouldn't on a single round-trip fare.

How a Converter Should Label the Trip Type

Determining trip type from raw segment lines means tracing the actual city sequence rather than just counting segments. A tool — or an agent working by hand — needs to compare each segment's origin and destination against every other segment: two segments forming a mirror pair (A→B, then B→A) is a round trip; a single segment with nothing following it is one-way; an outbound and return that don't share both endpoints is an open jaw; and three or more distinct city pairs is multi-city, whether or not the last segment happens to land back at the start.

Getting the label right up front changes how the rest of the itinerary should be read and explained — which is exactly why PNRGenius surfaces the trip type as part of the converted itinerary itself, rather than leaving an agent to work it out segment by segment on every booking.

Stopovers and Minimum-Stay Rules Vary by Fare Type

Even once a trip is correctly identified as multi-city or an open jaw, the fare rules governing how long a passenger can stay at an intermediate city before it counts as a separate ticketed stopover — rather than a same-day or short connection — differ by fare basis, by alliance, and sometimes by the specific city pair. Some published fares permit an unlimited number of stopovers on an international itinerary; others cap it at one or two, or price each additional stopover as an add-on.

This is one of the areas where reading the PNR alone doesn't tell the whole story — the segment lines show what's booked, not what the underlying fare rules actually allow. For a multi-city itinerary with a long gap between two segments, it's worth pulling the fare rules directly rather than assuming the routing itself confirms what's permitted, especially before promising a client that an extended stay at a connecting city won't affect their fare.