Lodgify channel manager: Airbnb, Booking.com, and your site

The Lodgify channel manager is the bit that keeps Airbnb, Booking.com, Vrbo and your own site on the same calendar so you don’t sell the same Saturday twice. It’s Lodgify’s distribution layer, not a separate product you bolt on after the website. If you only needed the general explainer, that’s channel manager for Airbnb. Here I’m talking about Lodgify’s version — including iCal versus API, and when a custom site on the same calendar is cleaner.

I keep OTAs and the direct site on the same PMS calendar for every cottage I ship. If you’re still shopping the category, the shortlist is best channel manager for Airbnb hosts. Below is how Lodgify’s version actually behaves when a UK cottage is the listing.

What a Lodgify channel manager does

It pushes availability and rates to connected OTAs and pulls reservations back into Lodgify. A site booking is another channel into the same property. Airbnb, Booking.com and Vrbo are the API channels; one Lodgify FAQ also names Expedia, though the pricing compare row omits it. In the UK, Booking.com is the one not to skip; Vrbo is connectable and usually secondary. Google Vacation Rentals is a separate Professional and Ultimate feature — not Starter, features move — and Google takes no referral fee. Individual homeowners cannot list GVR directly; under 500 properties a connectivity partner is the path.

That’s the whole job, really. One property, one set of rates, several shop windows. When a Saturday goes on Airbnb, it has to vanish on Booking.com and on your own calendar the same hour — not overnight, not “we’ll update iCal when we remember”. If you’ve ever had two families turn up for the same week, you already know why this exists.

Lodgify’s channel manager does not connect to Sykes, cottages.com or Hoseasons. SuperControl’s Sykes connection blocks dates; cottages.com and Hoseasons APIs currently need three properties. Read the SuperControl comparison before you assume the global OTA stack is enough.

Connecting Airbnb and Booking.com

Use Lodgify’s official channel integrations, map the room type, copy rates and minimum stays, then take a cheap test stay that must block the other listing the same hour. Don’t go live in peak season on a half connection. A quiet midweek is when you find out the room type mapped to the wrong listing.

1. Set up the property and rates in Lodgify first.
2. Connect Airbnb through Lodgify’s official channel integration.
3. Connect Booking.com the same way and map the room type.
4. Connect the website or booking widget to the same Lodgify calendar.
5. Take a test booking on each channel and confirm the others block.
6. Do not rely on iCal as the long-term Airbnb and Booking.com sync.

Get the property clean in Lodgify before you connect anything. Wrong minimum stays will sync faithfully to every channel. That’s not a channel-manager bug. That’s a messy engine.

iCal sync vs two-way API

iCal sync Airbnb Booking.com is the backup, not the architecture. Feeds lag, rates travel badly, and double bookings are how you find out. Two-way API is what “channel manager” is supposed to mean. Use iCal only as a bridge while you migrate.

If a listing is still on iCal “because it was easier”, that’s the first thing I’d change. Easier until the first overlapping Saturday.

Keeping the direct booking website in the same calendar

The Lodgify website, WordPress widget, or a custom Lodgify API site must book into the same property. A second WordPress calendar is how you recreate the old problem. Custom is cleaner when Lodgify’s website builder fights conversion; it still has to book into the same Lodgify property.

Connected channels keep the calendar honest. A bookable site is what moves the stay off the OTA.