Reservation operations on Galileo
Galileo reservation system for agencies that book and ticket on Galileo
Run every Galileo booking from one record: quote, hold, ticket, reissue and refund with approvals and an audit trail, while customers, agents and branches share the same self-hosted backend.
- One record per booking
- Holds, issue, reissue, refund
- Agents, branches and roles
- Fees, credit and invoices
How it runs
From Galileo search to ticket and after-sales in one workflow
A Galileo reservation system is more than a search box. Sales, operations, finance and agents work on the same booking record, so the PNR, the customer profile, the payment, the ticket and every change stay together. Staff stop switching between the terminal, inboxes and spreadsheets, and managers can see who did what and when.
- Map your booking flow, approval rules and agent structure
- Connect Galileo through your own Travelport agreement
- Set markups, service fees, credit limits and roles
- Train sales, ops and finance on the reservation desk
- Go live branch by branch, then open B2B and B2C channels
- Record locator
- 1G · K7Q2LM
- Customer profile
- Sara Malik · corporate account
- Branch and agent
- Dubai branch · Omar R.
- Ticketing action
- Issue ticket after payment
- Approval
- Finance sign-off required
Bookings and tickets
Every Galileo booking with its status, ticket and history
The reservation list shows where each booking stands, so teams pick up holds, payments and changes before deadlines pass.
- 1GDXB → LHR · 14 Nov · 2 adultsEconomy · corporate account–total
- GDSDXB → IST · 20 Nov · 1 adultEconomy · held for payment–total
- DXB → JFK · 3 Dec · 3 adultsPremium economy · date change–total
One booking record
PNR, traveller details, payments, tickets and messages tied to one reservation.
Ticketing workflows
Holds, issuance, reissue, exchange, refund and void with clear steps and logs.
Inventory and booking rules
Supplier rules, availability checks and booking constraints applied in one layer.
Customer profiles
Traveller documents, preferences, notes and booking history for repeat sales.
Approvals
Sign-off steps for refunds, exchanges, credit and fee overrides where you need them.
Operational reports
Bookings, tickets, changes, cancellations and team activity, ready to export.
Reservation lifecycle
Quote to ticket to invoice, under control
Each step is recorded against the booking, so approvals, changes and reconciliations stay traceable.
Quote
Search Galileo fares and send the customer a priced option.
Hold
Create the PNR and hold the seats until the fare time limit.
Pay
Take payment online, by invoice or from the agent's credit.
Ticket
Issue the ticket, then send the e-ticket and invoice.
Change
Reissue, exchange or refund with approvals and fee rules.
Reconcile
Match tickets, payments and refunds in finance reports.
Sources
Galileo next to your other suppliers
Combine Galileo availability with direct contracts and other suppliers without giving staff a second process.
Galileo on Travelport
Galileo content through your own Travelport agreement, PCC and credentials.
Other GDS and flight APIs
Amadeus, Sabre or flight APIs can feed the same search and booking record.
Direct contracts
Your own hotels, tours and negotiated fares sold alongside Galileo results.
Flight suppliers you can connect:
Seeru
Amadeus
Duffel
Google Flights
Kayak
Kiwi
Mystifly
PKfare
Sabre
TBO Holidays
Travelport
Back office
Agents, branches and finance in the same system
Who can see, book, ticket and refund is set by role, and money is tracked from the same booking.
Agents and sub-agents
Accounts for agents and sub-agents with their own limits and visibility.
Branches
Separate branches with their own staff, reports and booking queues.
Roles and permissions
Sales, ops and finance see and do only what their role allows.
Markups and service fees
By route, airline, agent or channel, as fixed amounts or percentages.
Credit limits and wallet
Agents book against a deposit or credit line you control.
Audit trail
Changes to bookings, tickets, payments and profiles logged with user and time.
Compare
Terminal, inbox and spreadsheets vs a reservation system
Many agencies run Galileo bookings across a terminal, email and spreadsheets. This is what changes.
| Task | Terminal and spreadsheets | PHPTRAVELS |
|---|---|---|
| Booking records | Terminal and spreadsheetsPNR in the GDS, payments and notes kept elsewhere | PHPTRAVELSPNR, customer, payment and ticket on one record |
| Holds and time limits | Terminal and spreadsheetsTracked by memory or in a spreadsheet | PHPTRAVELSHeld bookings listed with their time limits |
| Reissues and refunds | Terminal and spreadsheetsHandled by email, often without sign-off | PHPTRAVELSApproval steps and a logged history per change |
| Agent sales | Terminal and spreadsheetsAgents phone or email for every booking | PHPTRAVELSAgents book online with their own rates and credit |
| Fees and invoices | Terminal and spreadsheetsAdded by hand after ticketing | PHPTRAVELSService fees and invoices generated from the booking |
| Reporting | Terminal and spreadsheetsTotals rebuilt every month | PHPTRAVELSLive reports by branch, agent and status |
Use cases
Who runs Galileo reservations on PHPTRAVELS
Multi-branch agencies
One reservation process for every branch, with each team's work visible to managers.
Consolidators and host agencies
Sub-agents book Galileo fares in a B2B portal with markups and credit limits.
Corporate travel teams
Traveller profiles, approvals and reporting for company bookings.
Why PHPTRAVELS
A reservation system you own and can extend
Source code included
Self-hosted under a commercial licence, so your developers can adapt every workflow.
Your own Travelport agreement
Bookings run on your PCC and credentials, not a shared account.
B2B and B2C in one backend
Your website, agent portal and back office share the same bookings.
24 languages
Run reservations in your markets' languages and currencies, including right-to-left.
FAQ
Galileo reservation system questions
What agencies ask before moving Galileo bookings onto one reservation workflow.
Talk to salesGalileo is a global distribution system owned by Travelport, used by travel agencies to book and ticket flights; its host code is 1G. A Galileo reservation system is the software around it that agencies use to quote, hold, ticket and service those bookings, with customer records, payments and reporting in one place.
This page covers the day-to-day reservation operations: holds, ticketing, after-sales, agents, branches and finance. The Galileo software page covers the technical connection to Travelport, its environments and automation.
Yes. Galileo access, pricing and credentials come from your agreement with Travelport. PHPTRAVELS connects to it and runs the reservation workflow on top.
Yes. Ticketing actions follow clear steps, with approvals where you need them and a logged history, so responsibility stays traceable across the team.
Yes. Role-based access lets agents book in a B2B portal and customers book on your website, while the commercial rules stay under your control.
Your sourcing model, booking workflow steps, approval rules, agent and branch structure, financial handling and reporting needs. That lets us map a realistic scope and timeline.
Keep exploring