A direct booking website is your own site with a booking engine inside it, so a guest picks dates, sees a price and pays you, with no platform commission on top. You can buy one whole from a builder such as Lodgify, Hostaway or Guesty, or put a booking engine into the site you already run. The software costs anywhere from a $99 WordPress plugin bought once to around $150 a month, and your card processor takes 2.9% and 30 cents on a domestic card.
A guest should be able to see the nights you really have free, pay the price they were quoted, and finish without being handed to a checkout with somebody else's name on it. The booking then has to reach the calendar you read every morning. Sites break in the middle of all that. The pages on either side of the break look perfectly normal, so nobody who works on the site notices. The quickest way to find out about your own is to book three nights on it tonight, with your own card.
The four parts, and what each one costs
Your website is the part you already own, carrying your photographs and your room descriptions, and it is where a guest reads your terms. The booking engine is the software inside it that prices a set of dates from your calendar and collects a card. The processor is whoever actually moves the money. Your channel manager usually arrives inside the property system you already pay for, so check the one you own before you buy a second.
| The part | What it does | What it costs |
|---|---|---|
| Your site | The pages a guest reads before they decide | Lodgify from $14 a month at one property billed yearly, or a WordPress plugin at $249 a year or $99 once and $55 to renew |
| The booking engine | Prices a set of dates from your calendar and takes the card | Little Hotelier from $39 a month plus 1%, eviivo from $50 for a single property, Hostfully from $15 a property, innRoad at an estimated $150 |
| The card processor | Moves the money and stores the card for the balance | Stripe at 2.9% and 30 cents on a domestic card, 1.5% more when the card was issued abroad, 1% more if you convert the currency |
| The channel manager | Keeps your own site and every platform on one set of open nights | Usually inside your property system already |
Prices checked in August 2026, with the Lodgify plans read again in September 2026. Two of the systems here quote instead of publishing, and a quote for a ten room property is a different conversation from the headline figure: Guesty's cheapest plan, at $9 a month plus 1% of each reservation, is sold for one to three listings, and anything from four upward is priced on a call.
Before you spend anything here, look up what the platforms charged you last year and compare these costs against it.
If you already run a property system, start with the booking engine that came with it, since you are paying for it anyway. Shop only once you have tested that one and watched it fail. If you have no system and a handful of units, a builder gives you the site and the engine on one bill. Take the WordPress route only if your site is already on WordPress and somebody you trust keeps it updated.
The test: book your own property tonight, with your own card
Give it twenty minutes. Use your phone on cellular data, so you see what a guest sees instead of what the office wifi shows you. Tell nobody who worked on the site. Pay with a card you can refund in the morning, since the test card your developer left in the account will sail through steps that a real one fails.
-
Start from Google. Search your property name the way a guest would and click whatever comes up first. One tap from there to a date picker is the result you want. If a platform listing outranks your own site, or if a visitor has to hunt through a menu to find where dates are chosen, you have found your first job.
-
Book three nights next month for two people, and go all the way to the card. Pay. Within a minute the charge should be sitting in your processor and the reservation on your calendar. Write down anything else that happens: an error message a guest could do nothing about, a payment that goes through with no reservation behind it, a reservation with no payment. Hostaway's own documentation describes a different arrangement again, where the card is checked and charged as the reservation is created, and a failed charge deletes the reservation.
-
Read the first price on the screen. The FTC's fee rule has covered short term lodging, your own website included, since May 2025: the total with every mandatory fee inside it has to be shown more prominently than any other price. Tax can sit outside that number as long as the guest sees the final amount before paying. If your cleaning fee only appears on the last screen, you have both a legal problem and a guest who feels tricked at the worst possible moment.
-
Search dates you know are full. Guests ask for dates that have gone more often than dates that are free, so look hard at the page that comes back. It should keep the date picker in front of you, with the nearest nights that do work offered underneath. On plenty of sites the only thing left to press is the back button, which usually leads straight back to the platform listing the guest arrived from.
-
Put in one more guest than the unit can hold. Try the maximum first, then one above it. The site should turn down the extra guest at the point where the count is chosen. The failure to watch for is a price quoted for a booking the system will later refuse, which your guest discovers with a card already in their hand.
-
Sell one unit out of a room type where you own several, then search that night again. Properties with a single room of each name can skip this. Everywhere else, the type should stay bookable while any unit in it is free. A site that reads a single yes or no for the whole type closes it as soon as one unit sells. Those refused searches show up nowhere in your reports.
-
Read the confirmation email as a guest. One email should tell them what they were charged, what is still to pay and when it comes off the card, along with the cost of canceling. If all it says is a total and a thank you, some guests will phone the next morning to ask.
-
Refund yourself, then check two places. The money should come back, and the night should be open again on your own site and on every platform within minutes. Sometimes the refund lands in your processor and the night stays closed. When that happens, your booking engine and your property system are no longer passing messages to each other, and every night you cancel from now on will quietly stay off sale.
Write down what broke, with a screenshot, and send it to whoever owns the site. Then put it in the diary for a month from now, and again for the day after anyone changes your rates or your booking page.
What the test caught at our own place
I co-own MINT @Naschmarkt, 18 serviced apartments in five apartment types in Vienna, and my own team at Ekamoira built the site it sells from, which is where Fullstreak came from. I had been through every screen of that booking flow more times than I can count. It still took a deliberate attempt to book a stay before anything came out.
What stopped me was a guest count. I asked for four people in an apartment that takes three, the price came back without complaint, and I carried on through a checkout that took my name and my card and then refused the booking at the final step. The part of the system that prices a stay and the part that writes the reservation were answering the question of how many people fit in different ways.
Both Double MINT apartments take three guests. The booking engine and the property system now read that number from the same place, and there is one more check before any card is charged. I lost no money that evening, since I was the guest. What bothered me for the rest of the week was that I had no way of knowing how many real guests had hit the same wall, or for how long. The software had never sent us a word about it.
Where the guest actually pays, system by system
Before you sign anything, find out where the guest types their card and what the vendor charges you for taking it. Most will keep the payment on your own domain, and several will only do it on the right plan.
| System | Where the guest pays | What its own pricing page says |
|---|---|---|
| Cloudbeds | A Cloudbeds page on the standard setup, your own site on the premium one | A quote, and no commission on engine bookings |
| Little Hotelier | On your own site, or on one it hosts for you | From $39 a month plus 1%, Pro at $179 |
| Beds24 | On a Beds24 web address, unless you pay to put it on one of yours | From 15.50 euros a month, 19 to use your own address |
| Lodgify | Your site, with no redirect | No booking fee on any plan, $14 to $62 a month billed yearly or $18 to $77 monthly, at one property |
| ThinkReservations | One checkout across its sites and its engine | No plans and no figures, a call instead |
| ResNexus | Not stated | Custom, by unit count and season |
| Hostaway | Your site, with no redirect | Website Pro at $49 a month plus 0.5%, and 1.8% on US guests, with the base plan by quote |
| Guesty | Its own site, or a booking box dropped into yours | From $9 plus 1% at one to three listings, four and up on a quote |
| OwnerRez | Your site, or hosting on your domain | $40 a month for the first property and less for each one after, with no commission or per booking fee |
| Hostfully | Your own pages, with its booking box inside them | Growth at $15 a property plus 1% and 0.85%, Pro at $25 with both waived |
| Hospitable | Your own pages, or a web address it gives you | Basic at 1%, Premium at 4% plus 3% processing |
| Mews | A Mews page if you link out to it, your own if you put its booking box on the page | A form on all three tiers |
| eviivo | Your own site | From $50 for one property, $125 for several, extras by room |
| innRoad | Its booking box, pasted into your site | No fixed price, with an estimate of around $150 a month |
| WordPress plugins | Your own cart and checkout | WooCommerce Bookings at $249 a year, HBook at $99 once and $55 to renew |
Checked on August 2026, with the Lodgify row read again in September 2026.
Neither ThinkReservations nor ResNexus gives you a number to budget against. Ask for one in the first five minutes of the demo. The three questions I would put to any of them are in choosing a booking engine for a small hotel, and if you are still deciding whether to buy a builder at all, we have compared what every system in this field publishes.
If you hire someone to build it, what will your system let them do?
Every vendor publishes the answer in its technical documentation. The sales pages blur it. Some systems will only let an outside site read availability, and on those your developer can show a guest dates and a price, but the booking itself still has to happen on the vendor's page.
| What an outside site can do, per the vendor's own documentation | Systems |
|---|---|
| Hold the dates, then take the money | OwnerRez alone, where a quote can block the calendar and lapse before a booking exists |
| Create the booking, then charge the card | Cloudbeds, Beds24 on a single call with no hold in front of it, Lodgify, Hospitable and Guesty |
| Connect an outside site, on the vendor's terms | Hostaway, Mews on its Enterprise tier only, and Hostfully |
| Read availability, and little else | ThinkReservations, where eleven of the twelve documented paths only read and the twelfth sets daily rates |
| Nothing, unless you are a travel agency | ResNexus, which keeps anything that writes a reservation behind a certification for online travel agents |
| No way to create a reservation from outside at all | eviivo, innRoad and Little Hotelier through its parent SiteMinder |
| Everything, because the booking never leaves your own database | WooCommerce Bookings and HBook |
Checked on August 2026.
Two things I could not settle from the documentation and would put to a salesperson: exactly what Hostfully's open connection lets an outside site create, and whether a failed card on Lodgify leaves a booking that somebody has to cancel by hand. Ask a third while you have them on the phone: do the card fields on my own page come from you or from the processor, and what does that leave me responsible for? We build on all of these and we sell none of them. Whatever your property system is, it stays in charge of what is booked; a good build writes to it rather than replacing it.
Once it works, point something at it
Most of the free traffic to a site like this comes from guests who have stayed with you before, and from travelers who find you on a platform and then search your name to see whether you have a site of your own. Work both of those before you spend anything on advertising. The longer list, in the order I would take it, is in how to get more direct bookings at a small hotel.
Who should leave this alone for now
Below about $350,000 a year of bookings, the sums stop working. At a 15% commission, that much business hands roughly $52,500 a year to the platforms, and a build has to win back a good share of that to cover itself inside twelve months. It is where we draw our own line, and somebody with three units on a platform is better off putting the same money into filling them. Who this is built for has the longer version.
Wait as well if you are not yet taking platform bookings. For most properties the platforms are the cheapest way to build demand in the first place, and a booking page can only catch what already exists. And if your rooms are still sold from more than one calendar, put them on one calendar before you invite anybody to buy a night directly, or your own site will sell a night that has already gone.
Above that line the money saved adds up quickly, and all of it rests on a checkout that holds up, so run the test before anything else. Send whatever it turns up to whoever looks after the site, and get a date for the repair. If it turns out to be something nobody there can explain, we will look at it with you.
