Live demo

Sabre for agencies

Sabre software for travel agents that run the whole agency desk

Give your agents one browser desk for Sabre quotes, holds, ticketing, changes and refunds, with the customer record, branch roles, markups, invoices and end-of-day reports built around your approved Sabre access.

  • Shared booking queue
  • Changes, voids and refunds
  • Branch and agent roles
  • Invoices and reports

The agent's screen

What Sabre software for travel agents looks like on a working day

Sabre gives your agency the content: availability, fares, fare rules and the booking record. What your team still needs is the desk around it, where every quote, hold, payment and service request has an owner, a status and a due time, and nothing lives in a notebook or a spreadsheet.

PHPTRAVELS is that desk. Agents work in the browser, each booking sits on the customer record with its invoice and notes, and managers see the whole branch queue at once. The inventory and functions available depend on your Sabre agreement and enabled services.

Looking for the technical connector, endpoints and certification steps instead? Sabre API integration

Agent deskBranch: head office
  • KQ7M2DDXB → LHR2 adults, returnQuote sent
  • T4ZP9AKHI → JEDGroup of 12, one wayOn hold
  • BW3H8LJFK → CDG1 adult, returnAwaiting payment
  • NR6C1XLHE → ISTCorporate travellerTicketed
  • PJ2V5QBOM → SINFamily of 4, date changeChange request
  • HX8E4KCAI → DXB1 adult, cancelled tripRefund pending

Sample data for illustration

One shift, two systems

A day at a Sabre-connected desk, hour by hour

Sabre keeps the booking record and the ticket. The platform keeps everything your business needs around it. This is how the work splits during a normal shift.

  1. 08:30

    Open the queue

    Handled in SabreBooking records, schedule changes and ticketing time limits

    Handled in PHPTRAVELSOne list per branch with owner, status and due time

  2. 10:00

    Quote a family trip

    Handled in SabreAvailability, fares, baggage and fare rules

    Handled in PHPTRAVELSMarkup applied, quote sent from the customer record

  3. 12:30

    Take payment and ticket

    Handled in SabreBooking record created and ticket issued

    Handled in PHPTRAVELSCard or wallet payment, invoice and e-ticket email

  4. 14:00

    Change a travel date

    Handled in SabreNew itinerary and fare difference

    Handled in PHPTRAVELSChange fee, updated invoice and a note on the booking

  5. 16:00

    Process a refund

    Handled in SabreVoid or refund on the ticket

    Handled in PHPTRAVELSCredit note, refund status and approval trail

  6. 18:00

    Close the day

    Handled in SabreThe day's tickets, voids and refunds

    Handled in PHPTRAVELSSales, refund and agent reports with a finance export

Which Sabre functions your desk can use depends on your agreement and the services enabled for your agency.

Who can do what

Branch roles that match how your agency already works

Head office, branches, agents, B2B sub-agents and corporate bookers each see their own slice of the Sabre desk. Below is an example setup; every permission is set per role.

ActionAdminBranch managerAgentB2B sub-agentCorporate booker
Search and quoteAllowedAllowedAllowedAllowedAllowed
Hold a bookingAllowedAllowedAllowedAllowedWith approval
Issue a ticketAllowedAllowedAllowedAllowedWith approval
Change the markup on a quoteAllowedAllowedWith approvalNot allowedNot allowed
Void or refundAllowedAllowedWith approvalWith approvalNot allowed
Set markups and commissionsAllowedNot allowedNot allowedNot allowedNot allowed
Set credit limitsAllowedWith approvalNot allowedNot allowedNot allowed
See reportsAllBranchOwnOwnCompany

See alsoB2B travel portalCorporate travelTravel CRM software

Pricing and paperwork

One Sabre fare, three channels, the right document every time

The same net fare can be sold on your website, to sub-agents and to corporate accounts, each with its own markup and fee. Every sale then produces the paperwork your accounts team needs.

Fare build-upDXB → LHR, 1 adult
Sabre fare (net)
$480.00
Agency markup 6%
+28.80
Service fee
+15.00
Sell price
$523.80
Paid by card at checkoutYour margin $43.80
Sabre fare (net)
$480.00
Agency markup 3%
+14.40
Service fee
+0.00
Sell price
$494.40
Debited from the agent walletYour margin $14.40
Sabre fare (net)
$480.00
Agency markup 0%
+0.00
Service fee
+20.00
Sell price
$500.00
Billed on the monthly company invoiceYour margin $20.00

Example figures

Created with every booking

  • Customer invoiceNumbered, branded and stored on the booking.
  • E-ticket emailSent once the ticket is issued.
  • Credit noteRaised when a refund or void is processed.
  • Agent statementWallet top-ups, debits and credit used.
  • Finance exportSales and refunds for reconciliation.

See alsoTravel agency accountingAgent walletsPayment gateways

Getting started

Five stages from Sabre access to a live agency desk

Your team keeps selling while the platform is set up. Each stage has a clear owner, so you know what is waiting on you and what is waiting on us.

  1. 01

    Confirm Sabre access

    Regions, content scope, ticketing authority and servicing needs.

    Owner: Your agency

  2. 02

    Configure the desk

    Branches, users, roles, markups and booking policies.

    Owner: Together

  3. 03

    Connect and validate

    Search, booking and servicing paths checked against your access.

    Owner: PHPTRAVELS

  4. 04

    Test with your agents

    Real scenarios, documents, invoices and reports confirmed.

    Owner: Together

  5. 05

    Go live

    Training, support handover and monitoring of real bookings.

    Owner: Together

Decide before launch

  • Who can book, who can approve and who can service
  • One set of markups and commissions for every channel
  • How refunds and cancellations are handled and by whom
  • Which finance exports your accountant needs each month

Building with Sabre developer resources

Sabre Dev Studio publishes the API documentation, guides and sample workflows your developers can use to confirm authentication and service requirements. A custom Sabre application also needs the right credentials and testing before production access.

Your options

Four ways to put Sabre in front of your agents

The right choice depends on how much you want to build yourself, how fast you need to sell and how much servicing control you need.

OptionBest forTrade-offs
Build everything in houseBest forTeams with large engineering capacity and long timelinesTrade-offsHigh cost and slow delivery, with operational gaps until the build matures
A basic connector onlyBest forExperiments and limited workflowsTrade-offsYou still need the CRM, roles, invoicing, reporting and portals
A single-product portal templateBest forA fast consumer launch without deeper operationsTrade-offsLimited control, weak servicing and hard to scale across branches
PHPTRAVELS with SabreRecommendedBest forAgencies and OTAs that want control and speedTrade-offsNeeds a clear scope and approved Sabre access before setup

A good fit for

  • Retail and corporate agencies
  • Online travel agencies
  • DMCs and tour operators
  • Multi-branch sales teams
  • Hybrid offline and online operations

One-time licence with source code included, self-hosted on your own server.

Comparing distribution systems?GDS system for travel agentsAmadeus travel agent software

See pricingTry the live demo

Questions

Sabre software FAQs

Short answers to what agency owners ask before putting Sabre on their agents' desks.

Talk to sales

Sabre is a global distribution system that agencies use to search, price, book and service travel content. PHPTRAVELS is the business platform around that access: the agent desk, customer records, roles, markups, invoices and reports.

No. Sabre agent credentials are issued and managed by Sabre for your agency account, and PHPTRAVELS does not provide them. We connect your own platform to the access you have been approved for.

Yes. Your website or agent portal can use approved Sabre APIs for the booking workflows in your integration. Agents work in the browser while the server handles the Sabre connection. Available content, ticketing and servicing depend on your agreement and scope.

Yes. You can run a customer website and a separate agent portal, each with its own pricing rules, user permissions and reports, on the same Sabre access.

It depends on your scope and on how quickly your Sabre access is ready. Most projects follow the same path: confirm scope, configure the desk, connect and validate, test with agents, then go live with training.

Yes. Many agencies add more content sources as their markets grow. The platform is modular, so new sources can be added without redesigning your desk, roles or pricing.

Keep exploring

More from the platform