Typical use case

One typical use case is flights booked via the AERTiCKET Cockpit. Using the AERTiCKET Cockpit tool, the agent needs to import the booked flight into the Travice system for Nezasa to access the PNR. This is because there are two different systems in play here: the one used by the AERTiCKET Cockpit tool and the one used by Nezasa's TripBuilder.

Later, in TripBuilder, the entire itinerary is put together, and that separate flight is imported to sell the whole package to the consumer.

Steps to Import PNRs with file key for ad-hoc flights

You can do this in 2 ways:

A) 

1. Click on TO-Tools / TA-Tools.

2. Click on Ad-Hoc Components.

3. Click on + Add Transport Ad-Hoc Components.

4. A pop-up window opens, so you can enter the details and make your selections.

5. Click on the button Import PNR from GDS.

B)

1. Click on TO-tools / TA-Tools.

2. Click on Ad-Hoc Components.

3. Click on + Import PNR from GDS.

4. A new window opens so that you can enter the following PNR details:

• • PNR Locator (File Key) 

  • Reservation System (choose from dropdown)

  • AER Agency Number

5. After entering this information, the modal expands presenting the PAX Selection section.

6. Click on Load PAX Data. This loads the PAX names from the PNR that, on the next step, you will need to match the passengers in the itinerary. This is particularly relevant when having both adults and children in the same itinerary, where an exact mapping between adults and children is required between the information present in the itinerary and in the PNR.

7. Once PAX have been defined the modal expands presenting the Booking Details section. Here you can enter the following details:

• • Supplier 

  • Net Price (Total, all PAX) (including currency)

  • Sales Price (Total, all PAX) (currency based on itinerary currency)

  • Taxes (if you have this option selected on your settings in the Cockpit)

    

8. Click on Save.

The PNR details are imported into the itinerary, and the transport details are displayed in the overview list.

Go back to the Planner:

• If the imported PNR doesn't fit the dates or length of the itinerary, for example, a message is displayed to the user.
• Adapt changes to the dates, route or number of nights to make the imported flights fit the itinerary, and the message disappears.

FAQ

Q: Why can't I find all my PNRs? 

A: Whether a PNR can be found or not depends on whether the GDS and, thus, PNR is accessible via the pullPnr endpoint of the AERTiCKET / SoftConEx API.

Q: Why is the sales price equal to the net price? 

A: TripBuilder imports what can be found in the PNR. Typically, that's only the net price (your purchase price). Therefore, you should always review the prices and adjust them accordingly.

Q: Is the PNR edited in any way when I change the imported flight? 

A: No, it is a one-way import that is performed. The GDS remains the master. No changes done to the imported flights in TripBuilder have an impact on the actual flight booking in the GDS and with the airlines.

Q: Can a PNR be updated?

A: A PNR can be refreshed. Find more details about it here.