Managing Consolidator Queues

A consolidator sells seats to a travel agency at a net fare, and the agency can control the mark-up of that fare.

Consolidators can access Universal Records/PNRs only on specified city code queues. On a specified queue, the consolidator can service and/or ticket the PNR without requiring a bridge branch relationship to the agency. This is available only for Galileo (1G).

Retrieving URs/PNRs for Queue Enter, Queue Next, Universal Record Modify

On Queue Enter, Queue Next, and Universal Record Modify, only URs that are accessible for the consolidator can be retrieved.

The consolidator can retrieve only one Universal Record (UR)/PNR while working on Queue. If more than one PNR from a single UR is in Queue, the additional PNR is not returned to the Consolidator, but Queue session information is updated.

Only Universal Records that contain one PNR are supported for consolidator queues.

Consolidators cannot retrieve PNRs in their queue if any of the PNR attributes are either hidden or masked from the provider.

Consolidator Queues for Aggregated Responses

For aggregated responses, which contain a Galileo (1G) response combined with response data from ACH, SDK, or RCS, the UR can be retrieved if the consolidator has permissions to retrieve both the Galileo booking and the additional aggregated provider's booking data. If the consolidator does not have permission to retrieve the additional provider information, permitted data is retrieved and an error is returned.

Supported Functionality for Consolidator Queues

Consolidators have access to the following functionality for Universal Records/PNRs for a consolidator queue.

Exceptions

Currently, Galileo (1G) is the only provider that supports this functionality.