What PCC means
When a travel agency connects to a GDS, it does not log in as a company in general but as a specific office. The pseudo city code is that office's identity. Sabre's developer glossary describes the PCC as an alphanumeric identifier issued to a travel agency that designates access to Sabre Red Workspace and Sabre APIs.
The name comes from the idea of a city code: just as a three-letter code identifies a city, a pseudo city code identifies an agency inside the system. Sabre and Travelport PCCs are short codes, while Amadeus uses a longer Office ID, typically nine characters, that begins with a city code (for example the illustrative DXBXX1234).
A great deal hangs off the PCC. PNRs are owned by the PCC that created them. Each PCC has its own set of numbered queues, as Travelport's documentation explains. Ticketing authority, BSP or ARC settlement identity, private and negotiated fares, and airline agreements are all loaded against specific PCCs.
Agencies with several branches or markets often hold multiple PCCs. One office can be given permission to work in another's PCC, a practice known as emulation or branch access, so that a central ticketing team can service bookings created elsewhere.
How PCC works
A PCC is set up when an agency signs with a GDS and then becomes the anchor for that office's activity.
- Agency contracts with a GDSThe GDS provider creates a PCC or Office ID for the agency location, linked to its settlement identity such as an IATA or ARC number.
- Users and access are assignedAgent sign-ins and API credentials are attached to the PCC, which defines what they can see and do.
- Content is loadedAirlines and fare providers load negotiated fares, commissions and agreements against the PCC.
- Bookings are ownedEvery PNR created records its owning PCC, and airline messages for that booking come back to that PCC's queues.
- Cross-PCC workingWhere agreements allow, one PCC can emulate or share records with another, for example for central ticketing or out-of-hours support.
PCC in practice
Illustrative set-up for a multi-market agency (codes are made up):
| Office | GDS | Identifier | Purpose |
|---|---|---|---|
| Dubai head office | Amadeus | Office ID DXBXX1234 | Retail bookings and ticketing |
| Dubai head office | Sabre | PCC A1B2 | Corporate accounts with negotiated fares |
| Dhaka branch | Travelport | PCC 9XY7 | Local bookings, ticketed by head office |
A booking platform connected to all three must know which PCC or Office ID to use for each search, since fares and ticketing rights can differ. In this set-up, a corporate traveller's booking should be searched on the Sabre PCC where the negotiated fares are loaded. The Dhaka branch's bookings stay owned by its own PCC, so schedule change messages reach the branch queues, while the head office emulates that PCC to issue the tickets.
Who uses it
Advantages and limitations
Advantages
- Gives each agency location a clear identity for access, ownership and audit.
- Allows negotiated fares and commissions to be targeted at exactly the right office.
- Supports multi-branch operations through controlled cross-PCC access.
- Routes airline messages, such as schedule changes, back to the office that owns the booking.
Limitations
- Terminology and formats differ between GDSs, which complicates multi-GDS integrations.
- Fares loaded on one PCC are not automatically visible from another.
- Managing many PCCs adds cost and administrative work for agencies.
- Incorrect PCC selection in an API call can produce wrong prices or ticketing failures.
Frequently asked questions about PCC
Is an Amadeus Office ID the same as a PCC?
They do the same job. Both identify a specific travel agency office inside a GDS and own its bookings, queues and fare access. Sabre and Travelport call it a pseudo city code, while Amadeus calls it an Office ID, which is typically longer and begins with a city code.
Why does a travel agency need more than one PCC?
Separate PCCs let an agency keep branches, countries or business units apart. Each can have its own settlement identity, negotiated fares, users and queues. Agencies selling in several markets often need a PCC in each, because fares, taxes and ticketing authority depend on the point of sale.
What is PCC emulation?
Emulation lets an agent signed in to one PCC work as if they were in another, provided the GDS has set up the permission. It is commonly used for central ticketing, where a head office tickets bookings made by branches, or for consolidators servicing sub-agents' bookings without moving the PNR.
Where can I find my agency's PCC?
Your GDS account manager or help desk can confirm it, and it appears in your terminal sign-in and in PNR history lines that show the creating office. Booking platforms connected through an API will also hold it in their GDS connection settings. Treat it as account information and share it only with trusted partners.
Run your agency on one booking platform
ReservationHub's Subscription Cloud Edition gives agencies GDS, NDC and low-cost content, B2B and B2C sales, and back office in one hosted platform.
See the SaaS platform