Build a Branded Client Itinerary From Scratch — No PNR Required

Not every booking fits neatly into one PNR. An Umrah package might combine a flight booked in one system, a hotel booked directly with a property in Makkah, ground transport arranged separately, and a Ziyarat tour thrown in. A holiday package might bundle flights with a hotel voucher from a completely different supplier. There's no single "paste this and convert" source text for any of that — which is exactly the gap the Itinerary Builder fills.

What It's For

Where the main PNR converter takes raw GDS text and turns it into an itinerary, the Itinerary Builder starts from a blank canvas — or from a PNR as a starting point — and lets you assemble the rest by hand: hotels, transport, tour segments, and pricing, alongside the flight details.

1. Start with a PNR, or start blankPaste a PNR to auto-fill the flight segments, or skip straight to building the package manually if there isn't one.
2. Add the non-flight partsHotels, transport, tours, or any other component of the package, each with its own dates and details.
3. Add pricingShow the client a clear breakdown, or a single package total — whichever fits how your agency prices trips.
4. Apply your brandingYour agency name, logo, and contact information, so the finished document reads as yours.
5. Export a polished PDFA single, professional document that covers the entire package, not just the flight portion.

Where This Shows Up Most

Umrah and religious travel packages

These almost never come as a single clean PNR — flights, Makkah and Madinah hotels, and ground transport are frequently booked through different channels. The Itinerary Builder brings all of it into one client-facing document instead of sending a client three separate confirmations to piece together themselves.

Holiday and flights-plus-hotel packages

Same idea: flights from the GDS, a hotel voucher from a separate supplier, maybe transfers booked locally. One branded itinerary beats three disconnected emails.

Flights-only bookings that still need to look sharp

Even a simple flight booking benefits from your own branding on the final document — the difference between a document that looks like it came from a generic tool and one that clearly represents your agency.

A Step-by-Step Walkthrough: Building an Umrah Package

1. Start with the flight PNRPaste the GDS PNR for the outbound and return flights — say, a Karachi–Jeddah–Karachi routing — and let the Itinerary Builder auto-fill the flight segments: airline, flight numbers, dates, times, and connection details.
2. Add the Makkah hotelEnter the property name, check-in and check-out dates, room type, and number of nights. These fields are typed in manually since they don't come from a GDS PNR.
3. Add the Madinah hotelSame process, with its own check-in/check-out dates — make sure the transfer date between the two cities lines up with both hotel windows.
4. Add ground transport and any Ziyarat tourAirport transfers, inter-city transport between Makkah and Madinah, and any guided tour segments each get their own line with dates and a short description.
5. Add pricingEither a full breakdown by component (flights, hotels, transport, tour) or a single package total, depending on how transparent you want the pricing to be with this particular client.
6. Apply your agency brandingLogo, agency name, and contact details, so the exported document is unmistakably yours.
7. Export and review the PDFOpen the exported file once before sending — catching a typo in a PDF a client has already received is a much worse conversation than catching it thirty seconds earlier.

What to Double-Check Before You Send the PDF

The flight segments in an itinerary built from a pasted PNR are pulled directly from GDS text, so they're about as reliable as the booking itself. Everything else in the document — hotels, transport, tours, pricing — was typed in by hand, which means it carries the same risk of typos or mismatches as any manually entered data. A few things are worth a specific look before export:

• Date continuity. Does the Makkah hotel checkout date match the day you travel to Madinah? Does the final hotel checkout line up with the return flight date, not the day before or after it?
• Passenger count consistency. If the flight PNR covers four passengers, do the hotel room counts and pricing actually reflect four people, or were they copied from an earlier, different-sized booking?
• Currency and totals. If you've broken pricing into line items, do they actually add up to the total you quoted the client verbally or in an earlier email?
• Spelling consistency. Hotel and city names typed by hand are where inconsistent spelling — "Madina" in one field, "Madinah" in another — tends to creep in. It reads as sloppy even when nothing is functionally wrong.

Common Mistakes When Relying on Automation

None of these are dramatic, but they're the kind of small errors that are easy to make when a tool does most of the work and the temptation is to skim rather than review:

• Reusing a previous client's branding template without updating the trip-specific details. A saved layout is a time-saver, but only if every date, name, and price inside it gets updated for the new client, not just the cover page.
• Leaving a placeholder or draft note in a hotel or transport field. A quick internal note like "confirm with supplier" is easy to forget to delete once the supplier confirms.
• Assuming local check-in times without checking them. Hotel check-in and checkout times are local to the property, not to the passenger's home time zone — worth a second look on international packages.
• Sending before applying branding. A generic-looking PDF still functions, but it misses the point of the tool — always confirm the branding step was actually completed before export, not just planned.

Pricing Display: Itemized or Package Total

Neither approach is more "correct" than the other — it's a judgment call based on what a given client expects and how your agency typically prices. The Itinerary Builder supports both, so the decision is about the client in front of you, not a limitation of the tool.

Pairing the Builder With Other PNRGenius Tools

The Itinerary Builder rarely operates in isolation. If a flight segment carries a Basic Economy fare flag, that's worth a line in the itinerary itself so the client isn't caught off guard by a missing checked bag. If a client asks about change or refund terms on a flights-only portion of the package, running the fare rule text through the Fare Rule Decoder before you finalize the itinerary's terms section means you're writing an accurate summary rather than a guess.

Itinerary Builder vs. the Main PNR Converter: Which One to Use

The two tools solve related but different problems, and it's worth being clear about which one a given booking calls for. The main PNR converter is built for speed on a straightforward flight booking — paste raw GDS text, get a readable itinerary back, nothing else to configure. The Itinerary Builder is built for anything that needs to become more than that: a package with hotels or transport, pricing to present, or your agency's branding applied before it reaches the client.

In practice, the two overlap constantly: the fastest path into a full branded package is still pasting the PNR first, since the Itinerary Builder auto-fills the flight portion from the exact same GDS text the main converter reads. Neither tool requires choosing one over the other permanently — the right one just depends on what the booking in front of you actually needs.