Amadeus Integration

The Amadeus integration allows you to import airline ticket data from the Amadeus reservation system, manage tickets by PNR (Passenger Name Record), and link them to customer orders in Itsy.

Key concepts

PNR (Passenger Name Record)

A PNR is a 6-character code that uniquely identifies a booking in the airline system. Each PNR can contain multiple tickets for different passengers or services. In Itsy, PNRs serve as the primary grouping for imported tickets.

AIR files

AIR files are structured text files exported from Amadeus that contain ticket data. Each file includes passenger information, flight segments, fares, taxes, and payment details. A single file may contain tickets for multiple passengers.

Tickets

Each ticket represents an individual travel document within a PNR. Tickets contain flight segments, fare breakdowns, tax details, and passenger information.

Workflow

1. Upload an AIR file

Navigate to Inventory > Amadeus > Air Files and upload a file by providing:

• PNR code — The 6-character booking reference.
• File name — The original filename.
• File content — The raw text from Amadeus.

The file starts in Pending status after upload.

2. Parse the file

Click Parse on the uploaded file to preview its contents. The parser extracts tickets, segments, fares, and passenger data. It reports any errors or warnings found during parsing:

• Errors prevent import and must be resolved.
• Warnings are informational and do not block import.

3. Import tickets

After reviewing the parsed data, click Import to bring the tickets into Itsy. You can import all tickets in the file or select specific groupings. The file status changes to Completed on success or Failed if there are errors.

4. Browse PNRs

Navigate to Inventory > Amadeus to see all imported PNRs. Each PNR row shows:

• PNR code
• Link status — Green (all tickets linked), Orange (some linked), or Gray (none linked).
• Ticket count — Total tickets in the PNR.
• Linked count — How many tickets are linked to orders.
• Orders — Badges for each linked order (showing the order code and ticket count per order).
• Last updated — When the most recent change occurred.

Filtering PNRs

The PNR list uses filter chips above the list to narrow results. A date filter for Updated on is always visible and defaults to the last 6 weeks. You can add more filter chips using the + button:

Each chip shows a summary of its active value. Click a chip to edit its value, or click the x to remove the filter. Add and remove filters as needed -- only active chips affect the list.

Saved views

You can save your current combination of filters as a view for quick access later. Click the bookmark icon to save a new view, load an existing one, or set a default view that loads automatically when you open the page. Views can be shared with your team or kept private. If you modify filters after loading a view, the view shows a dirty indicator so you can save over it or discard the changes.

5. Link tickets to orders

Click on a PNR to view its tickets. Linking operates at the individual ticket number level — you select specific ticket numbers using checkboxes, rather than linking an entire PNR at once. Use Select All to select every available ticket at once. Void tickets and already-linked tickets are grayed out and cannot be selected.

Each ticket row displays the passenger name, ticket number type (Ticket, EMD, or MCO), route, date range, price, and -- if already linked -- a badge linking to the order. This lets you see partial link status at a glance (e.g., 3 of 5 tickets linked).

Once you have selected tickets, a linking panel appears with two options:

• Create new order — Select a client and segment, then click Create New Order. Itsy creates a new order with the selected tickets and automatically creates participants from the ticket passenger data.
• Link to existing order — Search for and select an existing order, then click Link to Order. The tickets are added to the order and participants are created or matched.

When linking, Itsy automatically:

• Creates a "Tickets" booking group in the order.
• Adds the PNR as an external reference on the order.
• Creates participants from ticket passenger data.
• Logs the linking action in the order's timeline.

Ticket details

Expanding a ticket shows full details:

Flight segments

Each segment includes:

• Flight number and airline
• Origin and destination airports
• Departure and arrival dates/times
• Class of service and fare basis
• Baggage allowance

Pricing

• Flight price (fare)
• Taxes (imported from the AIR file)
• Form of payment
• Commission rate and amount
• Endorsement restrictions (if any)

Manual taxes

You can add custom tax lines on top of the taxes imported from the AIR file. This is useful for recording additional charges or adjustments that are not captured in the original Amadeus data. Manual tax codes must start with AC (airline accounting charges) or SS (service segment charges). Each manual tax line has a tax code, currency, and amount. You can edit or delete manual tax lines at any time without affecting the imported taxes. Imported taxes cannot be edited or deleted.

When you add, edit, or delete a manual tax line, Itsy automatically recalculates the ticket number's total, the linked booking's price, and the order's totals to keep everything in sync.

Ticket number types

Each entry within a PNR has a type that indicates what kind of document it is:

Ticket information

• Ticket number (airline code + number)
• Passenger name
• Passenger contact information (phone or email when available)
• Issue date
• PNR creation date
• Office ID and IATA number
• Airline code
• Ticketing agent

EMD (Electronic Miscellaneous Document) details

Tickets may include associated EMDs for ancillary services such as baggage, seat upgrades, or other airline extras. Each EMD shows:

• EMD type and reason for issuance code
• Marketing and servicing carrier codes
• Route information (origin and destination)
• Validity period
• Pricing breakdown (base fare, taxes, equivalent amounts, net fare)
• Excess baggage details (where applicable)

AB Remarks

AB remarks are free-text comment lines from the Amadeus reservation. They typically contain contextual information such as company names, project codes, client identifiers, or special instructions. Remarks can be associated with specific passengers or segments.

When viewing a PNR's tickets, AB remarks appear as purple badges. During the linking process, all unique remarks from the selected tickets are displayed together, helping you identify who the tickets belong to.

Automatic Client Matching

When you select tickets for linking, Itsy checks the AB remarks against client profile codes. If a remark matches exactly one client's profile code, that client is automatically suggested in the linking panel. This speeds up the linking process for repeat customers — you set their profile code once, and future ticket imports automatically find the right client.

Unlinking tickets

If you need to reverse a ticket link, you can unlink a booking that was created from Amadeus tickets. Unlinking removes the connection between the ticket numbers and the order, then deletes the booking. The tickets return to "Available" status on the PNR detail page and can be linked to a different order.

You cannot unlink individual ticket numbers from a booking -- the entire booking is unlinked at once.

Default Amadeus supplier

Your workspace has a default Amadeus supplier setting (configured in workspace settings) that controls which supplier is assigned to bookings created from Amadeus tickets. When linking tickets to an order, this supplier is used automatically so you do not need to select one each time.

Automatic file detection

Itsy can automatically detect AIR files uploaded to your workspace's cloud storage bucket. The system polls the bucket at regular intervals, looking for files with a .AIR extension inside your workspace's folder. When a new file is found, Itsy:

1. Downloads the file content
2. Saves it as an AIR file record in the system
3. Deletes the source file from the bucket to avoid duplicate processing
4. Automatically parses and imports the tickets from the file

This means tickets from automatically detected files are parsed and imported immediately -- you do not need to manually trigger parsing and importing. The imported tickets appear on the PNR list, ready for you to review and link to orders.

How it connects

• Linked tickets appear as bookings in Orders, grouped under a "Tickets" booking group.
• PNRs are stored as external references on orders for traceability.
• Ticket passenger data creates participants within orders.
• The workspace's default Amadeus supplier (configured in workspace settings) is assigned to bookings created from tickets. You can also manage suppliers through Suppliers.
• AB remarks are matched against client profile codes for automatic client suggestion during linking.
• Saved views let you quickly recall frequently used filter combinations without re-entering them each time.
• Manual tax changes automatically cascade to the linked booking and order -- the booking price, participant prices, and order totals all recalculate when you add, edit, or delete a manual tax line.