Fulfillment may consist of the one or more of the following processes:
- Queuing: Queuing involves manipulating traveler itineraries and records to appropriately process travel requests. While queuing occurs on the Apollo® or Galileo® CRS, the function of working with queues is closely related to ticketing and the management of other fulfillment processes.
- Ticketing: The process of providing the actual electronic or hard copy ticket. Also referred to as Document Production, or Doc Prod.
- Payment and Refunds: Processing and reconciling payment or refunds.
- Reporting: Reporting business processes and data to regulatory agencies.
Note: Ticketing, payments and refunds, and reporting are the fulfillment processes that are most subject to industry standards, regulations, and requirements.
Basic ticketing for a booking contains one passenger and one stored fare, but any number of tickets can be issued from one stored fare quote when a booking has multiple passengers. The actual ticket issue request is the same for all options, and the basic steps are:
- Retrieve the PNR
- Set the printer linkage
- Issue the ticket
Before ticketing, the customer should first display the Host booking to check for changes to the ticketing data. If there have been changes, the ticketing process is stopped, and the customer receives a message that the Universal Record (UR) and the Host booking are out of sync. See Synching with the Universal Record for details. The UR is synched at this time, and the customer must check following elements/attributes against the Host:
- Passenger Names
- Air segments - any changes
- Fare quote amounts
- Fare quote ticketing status
Ticketing without a stored fare is not allowed.
Next Steps
Review specific Air Ticketing transactions:
- Requesting Air Tickets
- Displaying Ticket Information
- Refunding Air Bookings
