FAQs
How can we help?
Yes — visually and technically. It matches your design and lives on your own domain, so guests move from site to booking without ever feeling they've left.
To be confirmed — no figure available yet.
No. Bookings made through your own engine cost you no commission — that is the whole point of owning the channel.Almost certainly. Simple Booking has certified integrations with 109 property management systems, alongside 500+ native connections across RMS, CRM, BI, channel managers and more.
To be confirmed — the migration process is not documented anywhere.
Yes. Every guest has a personal Guest Area to modify their reservation, upgrade their room, add services or cancel independently, and to review their full booking history with you. They sign in with a password, with the Google or Facebook account they used to book, or with just their booking number and email.
Yes. PCI DSS certified, fully encrypted, with 39 supported gateways and multi-currency support.
Yes. It meets WCAG 2.1 AA and European Accessibility Act requirements, and has done since the regulation came into force.
Yes. Real-time reporting inside the platform, plus native Google Analytics integration to connect traffic sources, on-site behavior and campaign performance in one view. The engine also includes a customizable consent mode, so tracking respects what each guest agreed to.
The booking engine and your direct channels have it immediately. The main connected channels are reached in a few hundred milliseconds, through your property's own distribution queue. Bookings come back instantly from direct channels; from intermediated channels it depends on their API — push, pull or hybrid — and we implement the fastest model each one supports.
From your PMS, from an external channel manager, from the Simple Booking back office, or from the hotelier mobile app. All four take the same path.
There is one inventory. The booking engine, your direct channels and every connected channel read the same availability, so there is nothing to reconcile and nothing to drift. On top of that you can set automatic closing and last-room rules by channel, rate plan, period and inventory level.
Yes — that's the default. Everything stays open to the last available unit, because that's what maximizes revenue. If you'd rather trade some of that for certainty, the rules let you tighten it as far as you want.
Yes: different rate plans, rooms and restrictions per channel. But the system is built so you rarely need to — prices and restrictions can be derived from a single inventory and a single rate, so one change updates everything correctly.
Yes. A calendar view with bulk edits across a date range, down to room type and meal plan, covering rates, inventory and restrictions together.
130+ channels across OTAs, wholesalers, bed banks, tour operators and GDS — all of them certified two-way XML connections. The full list is on the Integrations page.
Two things, and they don't cover the same channels. On both, the promotion APIs let you build offers and promos for low-demand periods from inside the Simple Booking back office, instead of in the channel's own extranet. On Expedia, the integration also covers the conversation: incoming guest messages reach Simple Booking as they're sent, you reply from the back office — including from inside the booking — and reviews and your replies to them are handled there too. Guest messaging is Expedia only; it isn't every channel, and it isn't meant to be. These APIs exist where the integration goes deep enough to be trusted with them.
It's a status the channel grants, not a logo we chose. Booking.com and Expedia reserve it for partners with complete APIs, strict SLAs and sustained performance — monitored continuously by them and by us.
Yes. 116 property management systems are certified, alongside 500+ native connections across RMS, CRM, BI and more.
To be confirmed — activation time and who does the room mapping.
All four: Amadeus, Sabre, Galileo and Worldspan. Each one through a direct XML connection into the GDS database, with no intermediary in between.
No. GDS rates and availability are distributed from the same central inventory that feeds your website, your OTAs and every other channel. There is nothing to set aside and nothing to reconcile at the end of the day.
No. Properties are distributed under a shared chain code, so you don't have to accredit yourself separately with each of the four networks before you can sell.
Yes — corporate rates, negotiated company agreements and consortia rates are handled as rate types in the platform, alongside your public rates.
Your public GDS rate is a published rate, so parity applies to it exactly as it does anywhere else. A negotiated rate is different: it belongs to a signed agreement, so it sits outside the public comparison.
We do. Commission on a confirmed booking is settled automatically, and the bookings reconcile in your back office.
No. Consortia and corporate RFPs are managed centrally by our GDS team, who also advise you on which programs are worth bidding for in the first place.
It earns its place fastest for business, city, airport and conference hotels, for chains and groups, and for any property that already has corporate demand it isn't capturing. If agencies ask you for availability and you have meeting space, the channel is already looking for you.
No. A call at the front desk or an email to the hotel address gets entered into Converto by hand, and from there it behaves exactly like a request from your website form — same states, same quote page, same record. Requests can also arrive from your booking engine, or from another system over the API.
Yes, and it's one of the better reasons to have it. When the booking engine finds nothing for those dates, the guest can send the hotel a request instead, with the dates and the number of guests already filled in and room for anything they want to add. A search that would have ended becomes a request waiting in your back office.Yes. The quote is a landing page of its own, and the booking is completed there — the guest chooses one of your proposals, adds any services they want, and pays with the methods and gateways your hotel already uses. You receive a reservation with the quote attached, not an email saying yes.
Yes, until the date on the quote. The price is locked — what the guest saw is what they pay, even if your rates moved afterward — and every quote carries an expiry date the guest can see. After it, the prices lapse and any availability you were holding goes back on sale. Availability is treated differently while the quote is live: by default it's re-checked at every step, and any proposal that's no longer available drops out rather than being sold twice. On any individual quote you can switch that off and hold the rooms instead.
Yes, within limits you set. Each operator can go below your published rates according to their role and permissions, up to the amount they're authorized for and no further. It's the difference between giving the front desk room to close a deal and giving them the price list.
It's part of it. Converto is a standard module and the base version is included in every version of Simple Booking — you don't have to buy a quote manager separately to start answering requests properly. The advanced features sit in the higher versions: advanced statistics, deeper customization of the emails and landing pages, and reusable content parts.
For most people, no. Half our clients never need training at all, and for the other half there are free training sessions every week — for as long as they're a client, not just while they're getting set up.
Every time a guest searches. There's no interval to configure and no overnight job: the check is triggered by the search itself, so the comparison always refers to the room and dates in front of that guest.
Yes, within limits you define. You set the maximum adjustment as a fixed amount in your own currency and as a percentage; Rate Match realigns your direct rate inside that boundary and never beyond it. The worst case is a rate you have already decided you can live with. Every adjustment is written to the back-office log and raises an automatic alert.
The live public price for your room type and your dates against the price for the same room and dates on the major OTAs your guests compare against. They're all queried in parallel, so the result is back in seconds rather than minutes — and asynchronously, so your booking engine never waits for it. What gets adjusted is the price of your cheapest comparable room: the one the guest is comparing.
Then price is only half the argument, and Rate Match is built for that half. Where you can't go lower, your own channel can still offer what a channel can't: free cancellation on your terms, upgrades, early check-in and loyalty benefits — shown next to the rate inside the booking engine.
No — and the platforms themselves are the evidence. Simple Booking is a Booking.com Premier Connectivity Partner and, since 2026, one of only 19 Expedia Elite partners worldwide. The Channel Manager distributes to 130+ channels. Rate Match isn't about selling less through the channels; it's about not being undercut on your own website.
It runs natively inside Simple Booking's Booking Engine: no separate installation, no extra script, no second dashboard. Everything it does is visible in the Analytics section of your back office, search by search.
Either of two things, and you choose. We can connect you — your live rates and availability published to Google Hotel Center and the metasearch platforms, with your official website in the comparison and on the free booking links — and leave the campaigns to you or to the agency you already work with. Or we run the campaigns ourselves: metasearch, Performance Max for hotels, Google Ads, Meta ads. Either way the rates come from the same engine that sells them, which is why the listing doesn't drift.
No. Free booking links put your official rates in the comparison organically — no auction to enter, nothing to pay per click — and they come with the Hotel Ads connection. Sponsored placement is the opposite: an optional media spend that buys top positions while the guest is still planning. What's included in your setup depends on your plan and your market, so that part is a conversation rather than a price list.
Google Hotel Ads, Tripadvisor and trivago — connected directly and natively, and we're a Premium Partner of all three. Tripadvisor and trivago are built for the hotel to run its own campaigns, so there the connectivity is usually all you need; on Google Hotel Ads we can take the campaigns off your hands as well. And if you'd rather work through a dedicated metasearch management platform, we're already integrated with the ones most hotels use — the full list is on the Integrations page.
From the same inventory your booking engine and your 130+ channels use. There's no second price list, no separate upload and nothing to reconcile — which is what keeps a metasearch listing from advertising a room you've already sold.
No, but they compound. Results are ranked on price: paying for a position with a rate that's beaten on the next line is paying to send the guest elsewhere. Rate Match checks the major OTAs at every guest search and corrects your cheapest comparable room within seconds, inside limits you set.
If you run a loyalty club, yes — on Google Hotel Ads, which is the one platform that really supports it today. It's also the one way to win the ranking on price without touching your public rate: a parity agreement covers the rate you publish to everyone, and a member rate isn't that. The guest doesn't have to be a member already — they can sign up inside the booking and unlock the rate immediately, which is where most new members come from.
Traffic and conversions come through the native Google Analytics integration, with a built-in consent mode so campaign results stay measurable without ignoring what guests agreed to.
It can be, and it comes down to repeat business. Large resorts, seaside villages and mountain properties with a returning seasonal audience get the most out of one — we run clubs for properties up to 2,000 rooms. If your guests mostly come once, a club will do less for you, so your own repeat rate is the number to look at first.
Yes — that's what it's built for. Each member gets a single identification code on registration, valid at every property that takes part, and they can book at any of them under the conditions each one sets. Small groups and large chains work the same way.No, and that's the point. Every property can create its own member offers, and enable member discounts only in the periods it chooses. The club is shared; the pricing is not.
No. APIs are available to connect an existing loyalty system two-way, member list included, so the program your group already runs keeps running. On the PMS side nothing has to be arranged at all: the data of guests who book on a member rate reaches your PMS like any other booking.
Three ways. They may already be one, in which case they're synced across. They can join on the club's own mini-site, which comes with the club and lists the benefits and the participating hotels. Or they can join inside a booking, at any participating hotel, and unlock the member rate immediately — no prior registration.
In your booking engine, and — where the platform supports it — in the metasearch comparison, as member rates. That's the one way to show a lower price in the ranking without touching the public rate your parity agreements cover.
Nothing breaks: the guest sees all the other rates exactly as they would otherwise. A club adds prices for the people who qualify; it never takes prices away from anyone else.
No. The shop is open to anyone who reaches it — a guest with a booking, a guest without one, or somebody who has never stayed with you and only wants to buy dinner. That's the whole point of it being a shop rather than an add-on inside the booking flow.
A gift card is the product somebody buys; a voucher is the booking credit inside it. You set the two amounts, and the credit you issue can be worth more than the price you charge — a € 200 gift card can carry € 300 of booking credit, which is how prepaying becomes worth somebody's while. It's also why the whole thing works: the shop doesn't issue a certificate for your front desk to interpret, it issues credit inside the system that sells your rooms.
Yes. At checkout the buyer chooses to send it as a gift by email and adds the recipient, their own name and a message. Two confirmation emails go out — one to the buyer, one to the recipient, with the voucher code and a button that opens a search for a stay.
Yes, on a stay worth the same or more, in whole or in part. It comes off the total in your booking engine rather than sitting as a credit in a separate system — and your booking engine also accepts vouchers from third-party voucher platforms integrated via API.
If they're inside your free cancellation window they cancel on their own from the Guest Area and pay nothing — no penalty, no voucher, no phone call to your front desk. If you've already taken the money, you decide: refund it, or issue a voucher for the same amount, good for a future stay. The guest keeps the value and you keep the revenue.
It appears once, and only when the guest is on their way out — never on arrival, and not in response to a cursor drifting toward the top of the screen. The trade being offered is a fair one: their email address for the search they spent time building. A guest who isn't interested closes it and carries on booking.
An email address, which is the only required field, plus first and last name if the guest chooses to give them, and the privacy notice. Nothing else.
Wherever they left off. If they had chosen a room and services, the cart comes back filled; if they had started entering their details, those are there too; if they hadn't picked a room yet, they land on the results for their own search.
Availability and prices are re-checked when the guest arrives, and they're told what changed. If what they picked is no longer available, they're taken to what is — rather than to an error.
One.
No. Booking Recovery is native to the booking engine, which is also the reason it can re-check availability and prices when the guest returns — an external script has no way to do that.
Yes. Recovered bookings can be queried and identified, and the guests who left their details can be listed and exported, whether or not they booked.
Not on a timer. The link stays good for as long as the stay does: if the dates have passed by the time the guest clicks, they're told the search has expired. While the dates are still ahead, they always land on something — what they chose at the price they saw, or what changed and what's available instead.
No, and that's deliberate — an area a guest can't get into is worth nothing. They sign in with a password if they made one, with the Google or Facebook account they booked with, or with just their booking number and the email address they used. Every guest who booked can get in.
Their own details and contacts, the card on the booking, and requests or notes on the reservation. They can add services and add-ons before arrival, take an upgrade if your rules and your inventory allow one, and cancel. What's available and under what conditions follows the rules you set.
The cancellation policy is checked, whatever the policy says is owed is charged, the room goes back on sale, and the guest gets a confirmation. Inside the free-cancellation window nothing is charged at all. Nobody on your team is assigned anything, which is also why the room is available again immediately rather than in two days.
It's the natural instinct, and the arithmetic goes the other way. A cancellation that waits in a queue is a room you weren't selling while it waited — and the guest who has already decided usually doesn't change their mind, they just get a worse impression of booking direct. Where you do want to keep something, the option isn't friction: it's offering credit to spend with you instead of a refund.
Yes — the full history of what they've booked with you. It's the reason a returning guest doesn't start from an empty form, and it's why a second direct booking takes a fraction of the effort of the first.
No. The Guest Area is part of the booking engine — technically it lives in the same place. It's a separate area for the guest, not a separate purchase for you.
No. Each offer is built for one reservation and only exists if the conditions you set are met — the room they booked, what's still unsold, and the rules you configured. A guest already in your best available room isn't offered anything.
As far ahead of the stay as you decide. The distance from the arrival date is one of the settings, not a fixed behavior, and it's the setting that matters most: the earlier the offer goes out, the longer you have to resell the room the guest leaves.
They open the upgrade on their own reservation, see the room and exactly what the price change is, and accept or ignore it. If they accept, the reservation is modified there and then — no reply to wait for, and nothing for your front office to process.
It goes back on sale immediately. That's the point of offering the upgrade before arrival rather than at the desk: both rooms are still sellable, so you're not giving one away to fill the other.
Yes. You can attach a discount to the upgrade so the guest is comparing their room against a better one at a price you chose. Whether that's worth doing is a revenue decision, and it's yours to make per case.
No. It's a module you switch on and configure once, inside the back office you already use. It runs on your reservations and your inventory — there's no list to build, no audience to maintain and no external tool in the loop.
No, and you can't use it inside the booking engine — that's a deliberate choice, not a gap. A tag container can inject any script anyone adds to it, and the booking flow is also the payment flow. Instead, you hand over your GA4 and Meta IDs, and the Simple Booking team configures and validates the tracking. On your own website you're free to run whatever you like; the checkout is the part we keep closed.
That's the only way it works. The agency supplies the GA4 or Meta ID and the data goes into the hotel's accounts — not ours. Nobody needs access to the booking engine's code, and if you change agency later, the measurement history stays where it is.
Nothing on the booking engine. On the hotel's own website a code update is usually needed, so the tracking stack and the correct parameters are in place — and the script is handed over ready to paste, not described in a document.
The count survives; the person doesn't. The
purchaseevent still reaches Meta and Google Analytics, cookieless and with no identifiers attached — which is exactly what Consent Mode v2 defines for a denied state. You keep the number of bookings. You don't keep the visitor. The consent banner itself is built in and fully configurable.It means first-session attribution, and we name the model because it's the honest way to state the number: an agency reading first session knows precisely what's promised. Server-side delivery of the
purchaseevent is what keeps it there, when the browser side alone would not.Yes. Conversions from Google Hotel Ads, Tripadvisor and trivago are tracked and injected into Google Analytics, as well as being available in the product's own reporting. Without that, a metasearch booking normally arrives with no attribution at all.
Yes. A single hotel's booking engine can carry more than one GA4 tag, and the multi-property front end — the one where a guest chooses between the properties of a group, a chain or a destination — takes a separate tag of its own.