Booking widget
The booking engine you paste into the hotel website with one line of code, charging into the hotel's own account.
What it solves
The direct booking is the only one that pays no agency commission, and most hotels lose it in the same place: a "message us on WhatsApp" on their website. The guest who already decided to book at eleven at night does not write: they go back to Booking, where they can actually finish.
You notice it in things like these
- The hotel website shows photos and a phone number, and there is no way to book on it.
- Requests arrive by message and get answered by hand, with the price looked up by eye.
- Agency commission gets paid for a guest who was already on the hotel's own page.
How it works
It always charges into the hotel's account
The accommodation charge is born in the hotel's Stripe account: the payout arrives on its schedule and a chargeback, if there is one, is its own too. yaReserva is not the merchant of that sale. There used to be an option for us to collect and it was withdrawn: in the widget the hotel is always the seller.
The gate shows EVERYTHING that is missing
Plans assigned, domains authorised, payout account verified, a cancellation policy on every plan, taxes confirmed, lodging-tax rate verified and tax profile validated. All the missing pieces are shown at once, not one at a time: showing them in turns turns setup into a guessing game.
Each missing piece links to where it is fixed
"No rate plan is assigned to the widget channel" links to Rate plans, which is where it is actually decided. A warning with no link sends you hunting through a long menu.
The plans come from one place
What the widget sells is what is assigned to its channel, the same list as in Rate plans. There used to be two lists that could disagree; now switching it on here and switching it on there are the same action. If the last plan is removed from an active widget, it switches off: serving an empty catalogue is worse than being off.
Saving is not publishing
They are different decisions and they stay apart: merging them would switch widgets on at the first save without anyone asking. When off, the widget does not vanish from the hotel's site: it renders saying it is unavailable, which beats an unexplained gap.
Test keys before the real one
With a test key the widget loads anywhere, without charging or creating bookings, so no domain is required to try it. Requiring one forced test domains into the real configuration, where they stay forever.
Where it lives in the panel
- yaReserva ecosystem
- Web Embed
- Booking widget
What it needs first
The hotel's payout account verified: without it the widget does not publish.
Set up your hotelAt least one rate plan with its cancellation policy.
Rate plans
What it does not do yet
The limits, told by us
- A just-added domain works immediately, but until we see the snippet running there it stays unverified. That is what separates "it does not work" from "you never pasted the code".
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.