Live demo

Central reservations system

Central reservations system for hotel groups and travel businesses

Hold rooms, rates, restrictions and reservations for every property in one place, then sell them on your website, through B2B agents and to API partners without retyping a rate or double selling a room.

  • One inventory for all properties
  • Central rates and markups
  • Direct, B2B and API channels
  • One reservation record

What a CRS does

A single source of truth for availability, pricing and bookings

A central reservations system is the control layer above your properties and sales channels. It keeps availability and rates in one place, applies your pricing rules, pushes the result to every selling point and stores each booking once. In PHPTRAVELS the CRS runs on the stays module, with the supplier extranet, agent portal and API in the same self-hosted installation.

  1. Add each property with its room types, policies and content
  2. Set allotments, open and close dates and stop-sell per room
  3. Price by day and season, then add markups per channel
  4. Sell on your website, B2B portal, apps and API partners
  5. Manage every booking, voucher and invoice from one admin
Try the CRS demoSee pricing
Property
Harbour View Hotel, Lisbon
Room type
Deluxe double · 12 rooms
Dates
1–20 Dec
Rate plan
Winter season · $148 per night
Channels
Website, B2B agents, API partners

How it works

From room load to reservation report

The same flow for every property and channel, so your reservations team works one process.

  1. Load

    Properties, room types, content and cancellation policies.

  2. Allocate

    Allotments, open and closed dates and stop-sell per room.

  3. Price

    Seasonal rates plus markups per channel and market.

  4. Distribute

    Website, B2B portal, apps and API partners read live availability.

  5. Book

    Payment, confirmation, voucher and invoice on one record.

  6. Manage

    Changes, cancellations, refunds and reports from the admin.

Inventory sources

Owned properties, partner hotels and supplier APIs

A CRS is only as complete as its inventory. Combine three sources in one search, each with its own rules and markups.

  • Owned and contracted properties

    Your own hotels and the rooms you contract directly, with your rates and allotments.

  • Partner extranet

    Partner hotels log in to update their rooms, rates and availability under your markups.

  • Supplier and system APIs

    Bed bank content with your own credentials, plus PMS or channel manager links as custom integrations.

Hotel suppliers you can connect:

  • Agoda
  • Amadeus
  • Booking.com
  • Hotelbeds
  • Hotelston
  • RateHawk
  • Stuba
  • TBO Holidays
  • Travelport
  • Wanderbeds
See every integration

Back office

Reservations, partners and money in one place

Central reservations run in the same admin as your other products, agents and accounts.

  • Markups and commissions

    Fixed or percentage, per property, supplier, city or channel.

  • Roles and access

    Admin, reservations staff, hotel partner, agent and customer accounts.

  • Agent rates and wallet

    Net rates, commissions and prepaid wallet balances for B2B agents.

  • Multi-currency

    Show rates and take payment in the currencies your markets use.

  • Vouchers and invoices

    Generated and emailed automatically when a reservation is confirmed.

  • Reservation reports

    Bookings by property, channel and agent, revenue and supplier payables.

Compare

Separate tools per property vs a central reservations system

Groups often grow with one booking tool, spreadsheet or inbox per property. This is what changes when reservations are central.

TaskSeparate tools per propertyPHPTRAVELS
AvailabilitySeparate tools per propertyUpdated in each tool and checked by emailPHPTRAVELSOne allotment per room, read by every channel
RatesSeparate tools per propertyTyped again for each channel and seasonPHPTRAVELSSet once, with markups applied per channel
OverbookingSeparate tools per propertyFound when two channels sell the same roomPHPTRAVELSAllotments and stop-sell close dates as rooms sell
ReservationsSeparate tools per propertySpread across inboxes and property systemsPHPTRAVELSOne record per booking, searchable across properties
New propertySeparate tools per propertyAnother setup and another loginPHPTRAVELSAdded to the same admin, channels and reports
ReportingSeparate tools per propertyTotals merged by hand each monthPHPTRAVELSLive reports by property, channel and agent

Use cases

Who runs a central reservations system

  • Hotel groups and chains

    Several properties sold direct and through partner agents from one inventory.

  • OTAs and agencies

    Contracted hotels and bed bank rooms combined in one reservation flow.

  • DMCs and tour operators

    Allotments held with local hotels, sold to agents and inside packages.

Why PHPTRAVELS

A CRS you own and can extend

  • Source code included

    Self-hosted under a commercial licence, so your developers can adapt every rule.

  • Unlimited properties

    Add as many hotels, room types and partners as your portfolio needs.

  • 24 languages

    Sell in your markets' languages and currencies, including right-to-left.

  • B2C, B2B and API

    One installation feeds your website, agent portal and partner API.

FAQ

Central reservations system questions

What hotel groups and travel companies ask before centralising reservations.

Talk to sales

A central reservations system (CRS) is software that holds availability, rates, restrictions and reservations for one or many properties in one place and distributes them to every sales channel, so each channel sells from the same data.

A CRS controls selling: inventory, pricing and distribution. A property management system (PMS) runs on-site operations such as check-in, housekeeping and folios. PHPTRAVELS is the selling layer; a PMS can be linked through the API or a custom integration.

No. A channel manager mainly pushes rates and availability to OTAs for a property. A CRS owns the master inventory, pricing rules and reservation records across properties, and channels read from it.

A CRS is your own system for your inventory and bookings. A GDS is an external network that travel sellers use to find and book inventory; it is one possible channel that receives content controlled by your CRS.

Every channel draws from the same allotment per room and date. When rooms sell, availability drops everywhere, stop-sell closes dates, and API rooms are rechecked before payment.

Yes. Every plan includes the full source code under a commercial licence and you host it yourself, so your team can add rules, channels and integrations.

Keep exploring

More from the platform