WebHotelier in Saudi Arabia: implementation and integration, assessed independently. We do not resell it and we hold no partner position with the vendor — this page exists to help you decide, including deciding against.
webhotelier is the booking engine inside the vendor's webhotelier | primalres hospitality e-business ecosystem. So the fit question is narrower than the brand suggests: it is a question about how guests book directly with you, and about what has to talk to what once they have.
Direct bookings matter to your commercial model and your current booking path is losing people — the journey is clumsy, it does not work properly in Arabic, or it cannot take the payment methods your guests actually use. You run more than one property and want one booking experience across them. And you have a property management system you intend to keep, so what you need is a booking front end that integrates with it, not a replacement for it.
We do not recommend changing booking engine when your direct-booking problem is commercial rather than technical. If your own rates are worse than the ones guests find elsewhere, no booking engine will fix that, and you will have paid to move the same problem to a new screen. We also advise against it when your property management system is the real constraint — if the PMS cannot expose availability cleanly, the engine in front of it inherits the mess. In both cases start with an impartial assessment of the booking chain end to end.
Stated narrowly, from the vendor's own site: webhotelier is the booking engine within the webhotelier | primalres ecosystem, which the vendor describes as a hospitality e-business ecosystem. We deliberately do not reproduce the vendor's product counts, add-on counts or customer totals here — those are marketing figures, and repeating them on an advisory page would make them ours. What the engine does for your property is a scope question we put to the vendor in writing.
A booking engine is a front end to your inventory, and it is only as truthful as the availability feed behind it; overbooking incidents are almost always an integration story, not an engine story. Bilingual and right-to-left presentation needs testing on real content, not on a demo, because a guest-facing booking path that breaks in Arabic costs you the booking. And the ecosystem framing cuts both ways: the more of it you adopt, the better the pieces fit each other and the more it costs to leave.
Three things change the shape of a booking project in the Kingdom. Guest-facing content has to work properly in Arabic as well as English, right-to-left included, and that is a content and testing commitment rather than a checkbox. Payment has to accept what Saudi guests actually carry, which is a question for your payment providers before it is a question for the engine. And every stay eventually becomes a tax document: VAT is charged at 15%, and the Zakat, Tax and Customs Authority's E-Invoicing (Fatoorah) requirements have been in force since Phase 1 on 4 December 2021 and Phase 2 on 1 January 2023, so the folio has to reach your e-invoicing path in a form it can clear. We test that chain, because a booking engine that is beautiful and a folio that will not clear is a bad trade. See the hospitality and property management category, and travel and tourism for the sector picture.
We publish no price; the vendor publishes none, and an invented figure would be worse than silence. Four lines matter: the subscription or commission as quoted to you; the integration with your property management system and payment providers, which is where the effort actually goes; the bilingual content and testing work, which is consistently underestimated; and the running cost of keeping those integrations current. Note that the biggest number in a direct-booking business case is usually not on this list at all — it is the commission you do or do not stop paying, and that figure is yours, not ours.
Three routes, honestly. Your property management system's own booking engine, if it covers your journey — usually the cheapest integration because there is none. A specialist booking engine such as this one, when the PMS engine is the weak link. Or a custom booking path over the PMS API, which gives the most control and the most maintenance. We score them against your actual booking funnel; our independent software comparisons show the shape of that work.
We start from the booking funnel you have: where people arrive, where they leave, what the PMS can actually expose, and what your payment providers support. That evidence decides the answer. We take no margin on any licence and do not bid on implementations we scope, so "keep what you have" is a live outcome.
Property management system first, because availability and rates are the whole product; then payments; then the folio-to-invoice path; then whatever analytics and marketing tools need the booking event. We prove availability and rate accuracy before anything else goes live.
Reservations and front-office staff need to know what the engine can and cannot do before a guest asks, and revenue staff need to trust the numbers coming back. Training is built around real booking scenarios including the awkward ones — modifications, cancellations, group blocks. The first high-occupancy period after go-live runs with us on call.
We publish no counters here. The outcome that matters is agreed with you before the work starts — typically booking-funnel completion and the share of stays booked directly — and it is measured against your own baseline. A figure from another property tells you nothing about yours.
It tracks the property count, the state of the PMS interface and the amount of bilingual content to produce — not the engine. We size it after the funnel and interface review and put the assumptions in writing beside the estimate.
Subscription or commission, PMS and payment integration, bilingual content and testing, and keeping the integrations current. We model all four with your numbers and set them against the distribution costs you are trying to change.
We make no compliance claim on any vendor's behalf. What we do is establish where guest data is hosted, confirm in writing what the vendor states about it, and test that the resulting folio reaches your e-invoicing path in a form it can clear against ZATCA's published requirements. Your compliance function assesses; we assemble the evidence.
Your PMS's own engine first, then specialist engines, then a custom path over the PMS API. Each is recorded in the assessment report with the reason it was kept or dropped.
A booking engine is designed to sit in front of a property management system rather than replace it. Whether it integrates with yours is an evidence question, answered by an interface inventory and a written vendor confirmation per integration, which the assessment collects.
There are none here, and that is deliberate rather than modest. Unaudited counters on a vendor page are decoration; we would rather be the firm that does not print them. What we will state without a number: we take no licence margin, we do not bid on implementations we scope, and every engagement ends in a written recommendation you keep either way.
We name organizations only with their consent and in direct conversation, never on a product page. Ask for references in hospitality and we will arrange the calls.
No composite case study appears here. Relevant work is walked through attributably in a first conversation — the standard we suggest you hold every bidder to, ourselves included.
We publish no testimonial quotes on this page. Speak to our references directly; it carries more weight than a curated pull-quote.
We hold no reseller or partner position with the vendor and we claim no accreditation in relation to this product. On a page whose entire value is independence, that is the qualification rather than the gap. What qualifies the advice is method: a documented booking funnel, an interface inventory, a written scope, and no financial interest in the outcome.
Continue with the hospitality and property management category, our independent software comparisons, travel and tourism, or an impartial assessment.
Bring us your booking funnel and your PMS interface documentation, or let us assemble them. You will leave with a written position on whether to change engine and what it would cost. Request a demo or book an impartial assessment.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.