Lodgify and your own website: what works and what does not

Key takeaways

• Lodgify covers channel sync, the booking engine, payments and confirmations; your own website is still needed.
• The embedded flow can be adapted in colours and language, but not in step sequence, field logic and detailed wording.
• Before the widget, room pages need real content: size, beds, amenities, location, price range.
• Qovio describes that Lodgify charges a fee on direct bookings depending on the plan; compare this with the higher plan that has no fee.
• Embedded scripts add to loading time; test the booking page against a good LCP of 2.5 seconds.

Lodgify takes care of synchronising with the portals, the booking engine, payment processing and confirmations. What it does not take over is the page on which a guest decides to book your property, and that is exactly where the limits of the embedded booking flow lie.

This article describes which tasks you can hand over, which stay with you, and which costs appear on the invoice that are not obvious from the pricing page.

What Lodgify takes care of day to day

The core is channel sync: availability, prices and minimum stays go to the connected portals, and bookings come back and close the nights everywhere else. Added to that are a booking engine for your own site, the connection of a payment provider, booking confirmations and message templates, and a website builder with templates for holiday accommodation.

For small operators this is a complete set of tools from one supplier, and that is the real advantage: one invoice, one login, one contact in case of a fault. If you currently maintain availability in three extranets, that alone brings immediate relief. The question is not whether Lodgify fulfils these tasks, but where customisation ends.

How connecting to your own website works in practice

There are three routes. First, embedding: a script or frame brings the search field, calendar and booking flow onto your own page. Second, redirecting: your page shows content and prices, and clicking "check availability" leads to a booking page hosted by Lodgify. Third, the builder: the entire website is built within Lodgify.

In practice, the first two combined are the most workable. Your own page carries content, images, structure and speed; the booking is handled by the system that knows the inventory. The handover matters: the click should already carry the date range, number of guests and unit, so the guest does not enter the same details twice. This handover is the point where a connection is either clean or not.

A side question to clarify early is the address in the browser. If the click leads to a foreign domain, attentive guests notice the change; many providers therefore allow a subdomain of your own for the booking page. Setting that up takes 20 minutes and saves the guest from wondering whether they are still in the right place.

Where the embedded booking flow reaches its limits

As a rule you can adjust colours, font sizes within the frame, language and currency. You cannot adjust the step sequence, the field logic, the exact wording of cancellation and payment notices, or the behaviour on incorrect entries. If your property keeps its own tone of voice, it stops at the edge of the widget.

Two further limits become apparent later. The first concerns discoverability: content that exists only inside the embedded area does not belong to your site and contributes nothing to it, so room descriptions, facilities and price ranges must sit on your own pages. The second concerns measurement: you can see where visitors drop out only as far as the system reports it. A step-by-step report like that of a self-built flow is not available to you.

What must be on your page before the widget

The decision is made before the calendar. That is why every unit needs its own page with real details: square metres, bed layout, floor and lift, kitchen or kitchenette, bathroom with bath or shower, view, balcony, air conditioning, Wi-Fi, parking, pet rule. Add four to eight photos that show the room, not only details.

Equally important is a price range per season in plain text. Anyone who sees a figure only after the third click leaves. And the route to booking must be visible on each of these pages without scrolling.

This content belongs to you and stays with you, even if you change the booking system later. That is exactly why you should not maintain it in the provider's builder. To check whether your existing site already provides this foundation, a technical check of the hotel website will clarify it.

Which fees apply and how to compare them

The monthly fee is the visible part. The less visible one is the booking fee: Qovio describes in its review that Lodgify charges a fee on direct bookings depending on the plan, and that the highest plan goes without this fee [Q1]. In addition come the charges of the payment provider, which apply regardless.

Therefore never compare the monthly prices of two providers, but the annual total: base fee, booking fee on your expected direct revenue and payment charges. Other providers bill differently; Smoobu, for example, publishes plans per property and month, staggered by contract term (accessed 20 September 2026) [Q2]. Which model is cheaper depends solely on how much revenue runs through your own booking flow.

Working through the figures for six holiday apartments

Six holiday apartments with 150 occupied nights each give 900 nights a year. At four nights per stay, that is around 225 stays. Assume 40 percent of these come directly: 90 bookings. At an assumed rate of EUR 140 per night, that is around EUR 50,400 in direct revenue.

At an assumed booking fee of 1.9 percent (insert the rate from your own offer), that comes to around EUR 960 a year in booking fees alone. This sum is the yardstick against which you measure the surcharge for the plan without a booking fee: if the annual surcharge is below it, the higher plan is the cheaper option, and increasingly so the better your direct bookings perform. All figures here are assumptions; the only real figure is your own direct revenue from the previous year.

What embedding does to loading time

Every embedded booking tool brings its own scripts, fonts and styles. On an otherwise lean page, that is the single largest cost. So do not test the start page, but the page with the widget, and do it on a phone over a mobile connection. web.dev considers a Largest Contentful Paint of 2.5 seconds or less good, measured at the 75th percentile of page loads [Q3].

Two measures almost always help: load the widget only once its area is visible or the guest taps "check availability", and reserve the necessary space from the start so nothing jumps.

What you have to take care of yourself

The content stays with you: descriptions, photos, price ranges, house rules, cancellation and payment terms, in the version you also use on the phone. Also the upkeep of seasonal periods and minimum stays, because a system only calculates what you enter.

And there remains the monthly check: a test booking through your own site, a look at the confirmation email, a comparison of the next 14 days with what the portals show. How this synchronisation works technically is described in the channel manager connection.

When another solution makes more sense

If your booking flow is meant to be part of your brand presence, with its own language, its own extras and its own processes for groups, every embedded solution reaches its limits, and a flow built directly on your own system is the more honest answer. If you already run a PMS that keeps occupancy and invoices, you pay twice for functions that Lodgify also provides. And if you rent out just one apartment through one channel, you do not need the set-up.

Conversely, for three to fifteen units without in-house IT it is a workable set-up, provided your own site in front of it is right. Comparable considerations for another system are covered under connecting Smoobu to your own website.

Next, look at your direct revenue from the previous year and calculate the booking fee of your plan on it; with this one figure you can plan the Lodgify connection to your website properly. Book a call.

Sources and further reading

[Q1] Qovio: Lodgify reviews, pricing and booking fee

[Q2] Smoobu: pricing and plans (accessed 20 September 2026)

[Q3] web.dev: Largest Contentful Paint (LCP)