# Hotel software: the six systems a property runs on and how to choose them > Hotel software is not one product but a stack of six: a PMS for operations, a channel manager for OTA distribution, a booking engine for direct sales, a pa - Canonical: https://guruhotel.com/blog/hotel-software-guide - Last updated: 2026-08-19T00:00:00.000Z ## Short answer Hotel software is not one product but a stack of six: a PMS for operations, a channel manager for OTA distribution, a booking engine for direct sales, a payment layer, a revenue tool and a POS. Most properties buy them separately and connect them. Knowing which layer solves which problem is what keeps you from paying twice for the same function. ## Overview The six layers, and what each one actually does "Hotel software" and "hotel management system" are used as if they meant one thing, which is why vendors talk past each other in demos. In practice a working property runs six distinct functions. Some vendors bundle several; none does all six well, and no property needs all six on day one. LayerWhat it solvesWhat happens without itPMSReservations, room assignment, check-in/out, housekeeping, foliosYou run the hotel on a spreadsheet and lose the guest historyChannel managerKeeps availability and rates in sync across OTAsManual extranet updates and overbookingsBooking engineLets guests book on your own websiteEvery reservation arrives through an OTA and pays commissionPayment layerCharges cards, handles deposits, refunds and chargebacksCard details collected by email or phone, and PCI exposureRevenue managementSuggests rates from demand, pace and competitor dataStatic rates that miss both high-demand and soft datesPOSRestaurant, bar and spa charges posted to the roomOutlet revenue reconciled by hand at night auditThe PMS is the source of truth — everything else connects to it The architecture question matters more than any individual feature. Your PMS holds the real inventory: which rooms exist, which are sold, which are blocked for maintenance. Every other system should read from it and write back to it, so a booking taken on your website at 2am appears in the arrivals list before the front desk opens. When two systems each think they own inventory, you get double bookings — and the guest, not the software, absorbs the failure. Two questions to ask every vendor before signing: - Which system owns availability? If the answer isn't "your PMS", ask what happens when both are edited in the same minute. - Is the connection two-way and in real time? A nightly file export is not an integration. Ask for the sync interval in seconds and what the retry behaviour is when the PMS is down. What to buy first, by property size Buying order matters more than brand. The mistake that costs the most is a small property paying for enterprise revenue management before it has a booking engine — optimizing the price of rooms it still sells through commissioned channels. PropertyBuy firstAdd nextUsually not yetUnder 15 roomsBooking engine + payments on your own siteLightweight PMS, channel managerRMS, POS15–50 rooms, independentPMS + channel managerBooking engine, paymentsFull RMS50+ rooms or F&B outletsPMS + POSChannel manager, booking engine, RMS—Two or more propertiesMulti-property PMSCentral channel manager and one booking engine per brand—GuruHotel sits in the direct-sales layer of this stack rather than replacing the PMS — see how the direct layer fits alongside hotel management software. How hotel software is priced Four pricing models dominate, and they are not comparable line by line. A per-room subscription is predictable and independent of how well you sell; a commission on direct bookings costs nothing on an empty month and scales with revenue. What makes the comparison honest is calculating annual cost against your real occupancy, not against the list price. - Per room per month — the standard PMS model. Predictable, but you pay the same in low season. - Per booking — common for channel managers. Cost tracks volume, so audit it against your OTA mix. - Commission on direct revenue — used by booking engines. No fixed cost, and the vendor only earns when you sell direct. - Setup and onboarding fees — one-off, frequently negotiable, and the line item vendors drop first to close a deal. Before comparing quotes, ask each vendor to price a full year at your actual occupancy and average rate. List prices assume a property that doesn't look like yours. Five mistakes that show up two years later The problems that hurt a hotel software stack are rarely feature gaps found in the demo. They are structural decisions taken at signing whose cost only becomes visible when you try to change something. - Buying a suite for one module. Properties often pay for a full platform because the channel manager inside it was good, then run the rest of it badly. - Not asking who owns the data. Check before signing that you can export guest and reservation history in a usable format; otherwise the switching cost is your entire database. - Letting the OTA supply the tech. Free tools from a commissioned channel are rented, not owned, and they optimize for that channel's volume. - Skipping the direct layer. Hotels routinely automate distribution to channels that charge 15–25% before building the channel that charges nothing. - Never auditing the stack. Review the whole set once a year: paid seats nobody uses and duplicated functions across two vendors are the two findings that repeat. How GuruHotel helps GuruHotel turns a hotel's official website into a direct booking channel: an AI-built site, a conversion-optimized booking engine, real-time inventory synced with your PMS (Cloudbeds direct, 345+ more via Channex) and Stripe-powered payments — commission-free on every direct reservation. ## FAQ ### What software does a small hotel need? A property under 15 rooms needs three things: a way to take bookings on its own website with payment attached, a way to keep OTA calendars in sync, and a record of who is arriving. That can be a booking engine plus a lightweight PMS. Revenue management tools and a POS solve problems a small property does not have yet. ### Is a PMS the same as hotel software? No. The PMS is one layer of the stack — the operational core that holds reservations, rooms and folios. "Hotel software" covers the PMS plus everything connected to it: channel manager, booking engine, payments, revenue tools and POS. Vendors that sell a PMS often bundle other layers, which is where the terms get blurred. ### Do I still need a channel manager if my PMS connects to OTAs? Not necessarily. Some PMS platforms include channel management, and for a property on two or three OTAs that is usually enough. The case for a separate channel manager appears when you sell on many channels, need rate rules per channel, or your PMS connects to OTAs through a slow file-based sync. ### Can I start with just a booking engine? Yes, and for very small properties it is often the right first purchase: it is the only layer that adds revenue rather than managing it. A booking engine on your own site turns the traffic you already receive into commission-free reservations. Operational software becomes necessary as volume grows past what one person can track. ### How does GuruHotel relate to this? GuruHotel provides an AI-built hotel website, a direct booking engine, real-time inventory and Stripe-powered payments, helping independent hotels grow commission-free direct bookings alongside their OTA channels. ## Related - [Booking engine](/booking-engine) - [Hotel website builder](/hotel-website) - [PMS integrations](/integrations) - [What is GuruHotel](/what-is-guruhotel)