A channel manager is the single most useful piece of software for an owner who lists the same property on more than one booking platform. Without one, every platform keeps its own calendar, and keeping them all in agreement by hand is where double-bookings come from. Connect a channel manager once and the calendars stay in sync automatically: a booking on any platform blocks those dates everywhere else.
This guide walks through connecting Beds24, a widely used channel manager, so that availability, calendar and bookings flow into one place. It assumes you already have a Beds24 account with your properties set up there.
What syncing gives you
Connecting Beds24 keeps three things in agreement, in one direction or both:
- Availability — the dates a listing can be booked flow in from Beds24, so the calendar never shows free dates that are already taken on another platform. This includes the same-day turnover case, where one guest checks out and another checks in on the same date.
- Bookings — confirmed reservations are mirrored so you can see them in one read-only place, without logging in to each platform.
- Direct bookings — when a reservation is made directly with you, it can be pushed back to Beds24 so the channel manager blocks those dates on every other connected platform too.
What is not synced is listing content — photos, descriptions, amenities, pricing. Those stay wherever you manage them today. The channel manager owns the calendar; it does not take over your listing.
Before you start
You need two things ready:
- A Beds24 account with your properties and rooms already configured.
- The ability to generate an invite code in that account (this is in the API section of the Beds24 control panel).
A note on terms: in Beds24 a property can contain several room types. Each room type maps to one listing. A property with two room types is two listings on your side.
Step 1 — Generate an invite code in Beds24
Log in to your Beds24 control panel and open the API v2 section (sometimes labelled “API access”). Generate an invite code and make sure the scopes for bookings, inventory and properties are enabled — these let the integration read your calendar and bookings and write confirmed direct bookings back.
The invite code is a one-time token. You will paste it once; it is exchanged behind the scenes for a longer-lived credential, so you never need to store or reuse the code itself.
If you manage other people’s properties through Beds24, tick the option to allow linked properties when generating the code, or those properties will be skipped.
Step 2 — Paste the code to connect
On the Beds24 integration page, paste the invite code into the connect field and submit. The integration exchanges the code for its credentials and stores them securely. On success the page switches to a connected state showing when the credential was last refreshed.
If the code is wrong or expired, you will see a clear error and can simply generate a fresh one and try again — nothing is stored from a failed attempt.
Step 3 — Map your rooms to listings
Once connected, you map each Beds24 room to the corresponding listing. This tells the integration which calendar belongs to which property on your side. The mapping is one-to-one — a room backs at most one listing — and it is remembered, so you only do this once. If a mapped room later disappears from Beds24 (deleted or re-identified), the integration flags it for attention and keeps the last-known availability rather than blanking the calendar.
What if I have no listings yet?
If your account is new and has nothing to map, use Import from Beds24 on the mapping tab. It creates one listing per Beds24 room you haven’t mapped yet, fills in the room type (a Beds24 room type becomes a Houseviser listing), and auto-maps each one — so availability sync and booking pull can start immediately. You don’t have to import everything: rooms you’ve already mapped are skipped, and you can run it again later when you add rooms in Beds24.
Imported listings land as drafts. Beds24 doesn’t send photos, and a listing needs five photos before it can be published, so each draft waits for you to add photos and approve it. Drafts are hidden from the public site but still sync availability and pull bookings in the background — nothing is blocked while you finish them. If the room type doesn’t match cleanly, the listing defaults to Apartment; correcting it is a quick edit on the draft.
Step 4 — Run your first sync
With rooms mapped, trigger a sync to pull availability and bookings for the first time. The first pull looks back about a year so that in-progress and recent stays are captured, not just upcoming ones. After that, syncs are incremental.
From here on the connection mostly takes care of itself:
- A daily background check keeps the stored credential alive so it does not expire from disuse.
- If your Beds24 account hits its rate limit during a sync, the integration backs off and retries automatically once the limit window resets — you do not need to do anything.
- If the credential ever genuinely expires or is revoked, the page shows a “connection expired — reconnect” state. Reconnecting is just Step 1 and Step 2 again with a fresh code; your room mapping is preserved.
When something looks wrong
- The calendar shows dates as taken that you expect to be free. Availability is the source of truth from Beds24. Check the dates in Beds24 itself; the calendar mirrors what the channel manager reports.
- A booking is missing. Only confirmed reservations are mirrored. Pending or inquiry-stage holds do not appear until they are confirmed.
- The page says the connection expired. Generate a fresh invite code in Beds24 and reconnect — the mapping survives.
A channel manager removes the manual calendar juggling that causes double-bookings, and connecting it is a few minutes of one-time setup. Once Beds24 is connected and your rooms are mapped, your availability stays consistent across every platform you list on.