Convert Multiple PNRs at Once: Batch & Group Booking Guide

Group bookings are where manual PNR conversion really falls apart. A family of six, a 20-person tour group, a corporate block booking — each passenger or sub-booking might come as its own PNR, and converting them one at a time, copy-paste by copy-paste, turns a five-minute job into a thirty-minute one.

Batch conversion fixes exactly this: paste multiple PNRs into the converter at once, and get back every itinerary, converted and ready, in a single pass.

How to Turn It On

Batch/Group Mode lives under Advanced Tools & Settings on the main converter, collapsed by default to keep the everyday single-PNR flow clean. Open it, flip on Batch / Group Mode, and the converter switches from expecting one PNR to expecting several.

1. Open Advanced Tools & SettingsClick the panel below the Convert button on the PNRGenius homepage.
2. Turn on Batch / Group ModeA single toggle switch — no separate page, no separate tool to learn.
3. Paste all your PNRs into the boxOne after another. Separate them with a line of dashes if you want explicit control over where each booking starts and ends.
4. Click ConvertEvery PNR in the batch is parsed and returned as its own itinerary card.

Two Ways to Separate Bookings

You have two options, and you can mix them across a session depending on what's easiest for the source text you're working with:

Explicit separators

Add a line of three or more dashes (---) between each PNR. This is the most reliable option — PNRGenius trusts your boundaries exactly and splits strictly on those lines.

1.SMITH/JOHN MR
2 BA 284 H 15JUL 2*LHRJFK HK1 1120A 215P 15JUL E
---
1.KHAN/AHMED MR
2 PK 301 Y 20DEC 1 KHILHE HK1 0900 1130 20DEC E

Auto-detect

If you don't add separators, PNRGenius watches for a new passenger-definition line (like 1.SMITH/JOHN MR) that shows up after the current block already has at least one real flight segment — a strong signal that a new PNR has started. This is deliberately conservative: it won't split a single PNR just because it has a blank line in the middle of it.

What You Get Back

Each PNR in the batch converts independently into its own itinerary — same passenger names, flight segments, layover detection, and PNR Health Check warnings you'd get converting it on its own. A summary shows how many succeeded and how many had errors, so a single malformed booking in a batch of twenty doesn't block the other nineteen.

Why Large Groups Come as Multiple PNRs in the First Place

Most GDS platforms cap the number of passenger names allowed in a single PNR — commonly around nine. Any group larger than that gets split by the GDS itself into multiple separate or linked PNRs, even though the booking is functionally one group traveling together. This isn't a choice an agent makes; it's how the reservation system is built, and it's exactly why batch conversion matters for tour groups and larger family bookings — the fragmentation exists upstream, before the itinerary ever reaches PNRGenius.

Mixed Itineraries Within the Same Group

Not every passenger in a group ends up on identical segments. Tour operators sometimes split a large party across two flights on the same route to work around seat availability, a couple adds an extra leg onto a honeymoon before rejoining the group, or one family member books business class while the rest fly economy. Batch conversion handles this cleanly because it treats every pasted PNR as fully independent — different fare classes, different segment counts, different connection points, all converted and checked on their own terms rather than forced to match a shared template.

Common Formatting Pitfalls

A few things tend to trip up a large paste more than a single PNR would:

• Leftover queue or record locator banner lines. Copying straight from a GDS window sometimes drags along header text above the actual PNR — usually harmless, but worth a glance since it can occasionally get parsed as part of a booking.
• Passenger lines split across two lines by a copy-paste wrap. Worth a quick visual check on a long batch before converting, especially when pasting from a narrow terminal window.
• Blank lines in the middle of a single PNR. Auto-detect is deliberately conservative about this so a blank line alone won't be misread as a separator — but on messy source text, adding explicit --- dividers removes the guesswork entirely.

When in doubt, explicit separators beat auto-detect every time — they cost one extra line of typing and remove any ambiguity about where one booking ends and the next begins.

Health Check Across a Whole Batch

Every PNR in a batch gets its own PNR Health Check pass, exactly as it would converting alone — the same missing-ticketing-deadline, tight-connection, and missing-loyalty-number flags apply per booking. For a tour group, that turns into a fast way to scan twenty sub-bookings at once for the one passenger with a connection six minutes under minimum, or the one PNR that's missing a ticketing deadline, without opening each record individually in the GDS to check by hand.

Groups Split Across Different GDS Platforms

A tour operator or agency consortium sometimes ends up with the same group booked across two different reservation systems — one block direct-issued through the agency's own Sabre terminal, another net-rate allotment ticketed through Amadeus on the tour operator's side. Manually converting a mixed batch like that usually means switching mental context between two different PNR formats mid-task.

Batch mode doesn't require every pasted PNR to come from the same GDS. Each block is auto-detected and parsed independently, so an Amadeus-format PNR and a Sabre-format PNR can sit in the same paste, separated the normal way, and each converts correctly on its own terms without needing to be sorted first.

Exporting and Sharing Batch Results

Once a batch converts, each itinerary keeps the same export options available on a single conversion — PDF download and translation into the same set of 25+ languages. For a group booking, that combination is where batch mode pays off twice: once at conversion time, saving the copy-paste-repeat work, and again when it's time to distribute results, since each passenger or family unit's itinerary is already a separate, cleanly formatted document ready to hand to a tour manager or send out individually rather than one long combined file that has to be split apart afterward.

Passenger Types Within a Group: Adults, Children, and Infants

Group PNRs rarely contain only adults. A family booking might carry two adults, a child fare, and an infant on lap all inside the same record, or a tour party might have a handful of child fares mixed in among the adults. Each passenger type can carry its own fare basis, its own baggage allowance, and — for an infant — its own separate element tied to the accompanying adult's segments, as covered in more detail in the guide to common PNR errors.

Batch mode doesn't need any special handling for this — each PNR converts with whatever passenger types it actually contains, adult, child, and infant fares included, exactly as it would sold and converted individually. The practical benefit shows up when scanning results: with several PNRs converted side by side, it's much easier to notice if one sub-booking is missing the infant element the others in the same family carry, since the itineraries are sitting right next to each other for comparison instead of being checked one at a time from memory.

The Limit, and Why It's There

Batches are capped at 25 PNRs. It's a practical ceiling, not an arbitrary one — it keeps conversion fast and keeps a single paste from accidentally becoming an unreadable wall of text. For anything larger, running two batches back-to-back takes a few extra seconds and is still dramatically faster than converting one at a time.