Lodgify vs SuperControl for UK holiday cottages

If you’ve been paying SuperControl fees for a login you barely open, or you’re on Lodgify and someone at a meetup told you SuperControl is “what proper cottages use”, you’re in the same fork I get emails about every month. Lodgify sells a bookable website with a channel manager for Airbnb, Booking.com and Vrbo. SuperControl is a UK holiday-let PMS sold to owners and agencies, with depth on UK agency channels and owner-services.

I build custom sites in front of whichever engine you already run — Lodgify, SuperControl, Bookalet, it doesn’t have to be a conversion. SuperControl isn’t the villain. If Sykes, cottages.com or Hoseasons still fill weeks, SuperControl is the documented UK pipe: date-blocking into Sykes, and cottages.com / Hoseasons APIs once you have three properties. If you have one or two cottages and the problem is “guests cannot book on my site”, you’re probably over-specified on SuperControl and under-specified on the website.

Who each platform is built for

SuperControl comes from the UK and Ireland self-catering world. Owners, agencies, and housekeepers live in it daily: enquiries, owner statements, extras, cleaning schedules, and a booking engine you can put on a site. Support is in a UK timezone. The gravity is operational. There is no SuperControl website builder. The public site is something you bring, or a developer builds, and then wires in.

That operational depth is why agencies stay. Split-owner reporting, extras that invoicing actually understands, a calendar a cleaner can work from, and a channel stack that already includes the UK cottage brands. If you run 15 cottages for other people, swapping that for a prettier builder is how you spend winter rebuilding process, not how you take more direct bookings. SuperControl will still sell the Owner product to a single cottage. The reasons to skip it at that size are cost shape, the three-property Awaze gates, and no builder — not a ban on owners.

Lodgify comes from the global short-term rental stack. The pitch is direct bookings: a website builder, a booking engine, and a channel manager so Airbnb doesn’t double-book you. Holiday let software in the UK sense — Sykes contracts, cottages.com, agency-style owner reports — isn’t the centre of the product. That is a channel gap, not a size ceiling. Professional and Ultimate have no published property cap. Lodgify’s own case studies include Stayhost at 144 properties and Skol at 90. For a cottage that wants Google plus Airbnb plus a site that can take a deposit, that website-led centre of gravity is usually the right one.

Bookalet sits to the side of this comparison. Cheap UK diary, fine if you barely use OTAs, weaker if you need Airbnb and Booking.com as a two-way API rather than iCal. I’ll compare Bookalet vs Lodgify vs SuperControl properly in its own piece. Here it’s only a reminder: the UK market has more than two names. Match the channels you must keep to the website problem you’re actually trying to fix.

Do not force Lodgify onto an agency that needs cottages.com or Hoseasons as an API, or a live Sykes diary kept in sync. Do not stay on SuperControl because “that’s what Sykes owners use” if you’re paying for a platform you never log into except to unblock a calendar, and your live channels are Airbnb, Booking.com and the website.

Channel manager: Airbnb, Booking.com, Sykes, cottages.com

SuperControl’s channel manager is the reason it still wins RFPs. The Sykes connection is a gated date-blocking cross-update — SuperControl’s own words: the main aim is blocking dates. It forwards a guest name. It no longer receives guest or financial data from Sykes. Sykes is not in SuperControl’s Channel Comparison Table, and it is not on the 1% OTA fee list. There is no evidenced owner-facing Sykes API for anyone else to speak either. cottages.com is the first-class UK-agency API in SuperControl’s taxonomy: two-way rates and availability, with a current minimum of three properties. Hoseasons is a gated API (SuperControl’s own docs disagree on depth) and also wants three properties.

Airbnb, Booking.com, Vrbo, Expedia and TripAdvisor are there too, with a 1% plus VAT channel service fee on the gross accommodation value of named OTA API bookings: Booking.com, Airbnb, Vrbo, Expedia, Cottages.com and TripAdvisor. Not Sykes, not Hoseasons, not Google. Direct bookings are not charged. That 1% is on top of whatever the OTA already takes.

Lodgify’s channel manager is strong where the global OTAs are the calendar: Airbnb, Booking.com, Vrbo, and listing into Google Vacation Rentals on Professional and Ultimate. That’s the mix I want for a cottage that’s trying to get off an agency-only model without disappearing from Airbnb. Lodgify will not keep a Sykes diary in sync. Sykes does not publish an owner iCal feed. If someone tells you Lodgify “does Sykes”, ask what they actually connected. iCal is how double bookings are born.

Hoseasons and cottages.com sit in the Awaze world. SuperControl treats that family as normal — and currently gates both APIs at three properties. Lodgify does not document those pipes. If a meaningful slice of your year still arrives with a cottages.com or Hoseasons reference, and you have three properties, count that as a SuperControl point. You can still take direct bookings beside those channels. The constraint is the contract and the calendar, not whether the homepage has a nicer hero.

Be precise about the job. If the job is “keep Sykes dates blocked and stop double-booking Airbnb”, SuperControl is the specialised tool. If the job is “take the booking on my own site and keep Airbnb in sync”, Lodgify is usually enough — and a custom site on the Lodgify API is how you stop the website being the weak channel. I wrote that setup in Lodgify API: custom holiday cottage website.

Direct booking website: Lodgify builder vs SuperControl engine

This is the fork that actually changes revenue. SuperControl will give you a booking engine. You (or a web designer) still have to wrap a site around it. Plenty of UK cottage sites are a dated WordPress theme with a SuperControl widget in the middle. The diary works. The page doesn’t sell the week. Guests bounce to Airbnb because the site feels like admin.

Lodgify gives you a website builder so you can launch without hiring anyone. That builder is a template. It’s faster than nothing, and it caps how distinctive and fast the site can be. The PMS doesn’t have to be the CMS. You can keep SuperControl’s engine and still put a real site in front of it. Same for Lodgify.

Owners switching from SuperControl because “Lodgify includes a website” sometimes land on a template that still cannot rank next to a five-year-old WordPress cottage with actual location pages. Included isn’t the same as converting. Count pages, speed, and whether the weekly price is visible, not whether the PMS vendor printed “website” on the plan card.

A SuperControl cottage can also have a custom site. I’m not claiming otherwise. I’m claiming that owners shopping this pair often think they’re choosing a website, when they’re choosing an operating system. Choose the OS for the channels you must keep. Then spend money on a direct booking website that can convert the traffic you already pay to acquire.

WordPress shows up in both camps. SuperControl has been dropped into ageing themes for a decade. Lodgify has a plugin that is still an embed. Neither is “a custom site”. If the theme is the reason guests cannot see a price, changing PMS will not fix the theme. Fix the site, or accept that Airbnb will keep finishing the booking you started.

SuperControl pricing vs Lodgify pricing

SuperControl’s Owner product publishes numbers. For 1–3 properties the slider is a £250 joining fee plus £555.35 a year (shown as £46.28 a month), all ex VAT. Year one for a single cottage is £805.35 plus VAT before the OTA 1% and PCI. The joining fee is not refundable; there is 30-day money-back on the licence. The Agency SKU on the same page is quote-only. I go into the shape of that bill in SuperControl pricing.

Lodgify’s pricing page publishes plans. Prices move with property count and billing cycle, and they’ve dropped the old per-booking fee on current plans — verify the live page before you budget, because vacation-rental SaaS changes the labels. The shape is still “subscription”, not “joining fee plus a cut of Airbnb”. For a single holiday let that only needs Airbnb, Booking.com and a site, that shape is easier to live with. The 2026 breakdown is in Lodgify pricing.

Add the hidden layer. Stripe on direct bookings, plus Lodgify’s 1% application fee on gateways connected through Lodgify. SuperControl’s 1% on named OTA API stays, which the OTA will often commission again because it’s baked into the sent rate. Domain, apps, a developer if the widget fights the theme. SuperControl’s cost follows UK agency economics; Lodgify’s cost follows SaaS economics. Neither is “free direct bookings”. Direct only saves the OTA commission if the website can take the stay.

Work a rough year. One cottage, £80,000 through the books, half still on OTAs: the platform cut on those weeks is the bigger number, whatever your own Airbnb payout or agency contract says. SuperControl’s 1% plus VAT on named OTA API stays is another few hundred, plus the licence. Lodgify is a few hundred in subscription if the plan fits. The software bill is rarely the expensive line. The expensive line is nights that could have been direct. Buy SuperControl if you need the Sykes date-block or the Awaze APIs. Don’t buy a cheaper OS and then lose the channels that actually fill the year.

Switching from SuperControl to Lodgify

Don’t switch PMS in August. Map the channels you would lose. If Sykes still produces a chunk of revenue you cannot replace with Google and Airbnb this year, stay, or run a hybrid with your eyes open. SuperControl can keep the Sykes date-block and still allow a direct path. Leaving is a calendar project, not a cancellation email.

If you are leaving, treat it as a migration: export or recreate rates and minimum stays, connect Lodgify to Airbnb and Booking.com before you turn SuperControl off, take a test booking that blocks the other channel, then cut the old engine. iCal-only as a bridge is how you get a double booking in the first week. I’ve migrated a live cottage diary with no downtime; the work is sequencing, not heroics.

Stay if housekeepers, owner splits, and UK agency channels are the product. Leave if you are a single let paying agency-shaped fees for a login you resent, and Airbnb plus Booking.com plus a website would cover the year. The uncomfortable middle is common: keep SuperControl for Sykes dates, put a better site on the booking engine, and only migrate if the licence still feels like a tax. I’d rather you keep the OS that matches the channels than buy Lodgify as a lifestyle upgrade.

Timeline if you do migrate: connect channels in Lodgify while SuperControl is still live, overlay the diaries for a quiet midweek, take two test bookings (site → OTA block, OTA → site block), then point the domain. Don’t run both engines as sources of truth. Pick one calendar. The rest is DNS and telling Sykes, if they are staying, which system still owns the dates.

After you land on Lodgify, you still have the website problem. The builder might be enough for a season. If it isn’t, keep Lodgify as the engine and put a custom site in front. That’s also when holiday cottage websites stop being a template conversation and become a booking-path one. The wider UK table is best holiday let software UK.

Short version. Airbnb and Booking.com, want a site guests trust: Lodgify, then a real website if the template caps you. Several properties, Sykes dates to keep blocked, or cottages.com / Hoseasons as an API (three properties): SuperControl, then fix the site. Pick the calendar that cannot double-book, then spend on the page that can take the week.