Guide · Multi-account

Multiple Smoobu accounts in one booking engine: how to make all your properties bookable on a single website

Updated 9 September 2026 · Approx. 6 min read

Why do hosts have several Smoobu accounts at all?

In practice there are three typical reasons why properties are spread across multiple Smoobu accounts:

• Property management: a manager looks after holiday rentals for several owners. Each owner runs their own Smoobu account, with their own invoicing, their own login and their own contracts with the portals. That is clean and should stay that way; only the public face should be a shared one.
• Separate businesses: two houses or locations were set up as separate accounts (for tax or historical reasons) and should remain so, but they are marketed together.
• Families and communities of heirs: the apartments belong to different people who invoice separately but run one website together.

By the way, anyone who owns all the properties themselves and does not need separate invoicing is usually better off with one Smoobu account. Splitting into several accounts only pays off when invoicing or responsibility really are separate. Whether a split makes sense for tax purposes is a question for your own tax adviser.

How Smoobu describes embedding into your own website

Smoobu's own help describes it like this (as of September 2026): the code snippet for your website comes from the individual account and is account-specific. Its first line stands either for all properties of that account or for a single one. On top of that, every account has a standalone booking page of its own with its own address. It is written up in the help articles on embedding the booking system into your website and on telling the three website tools apart.

Anyone running three owner accounts therefore works with three code snippets and three booking pages. An add-on built on the official Smoobu API takes the other route: it connects several accounts at once, appears to the outside world as a single booking engine, and searches across all connected properties in one go.

How it works with BineBoost: step by step

BineBoost is a booking engine for your own website that connects to Smoobu via API keys, and to several Smoobu accounts at the same time:

1. Create a BineBoost account and connect the first Smoobu account. To do that you store the API key pair of that account with BineBoost. Its properties are then read in through the official Smoobu interface.
2. Add further Smoobu accounts: under “Smoobu connection”, enter the keys of the next owner account; you repeat the step for every further account. Every connection is listed separately and can be removed individually.
3. One shared booking engine: all properties from all accounts appear together in one booking flow, styled like your own website. The availability search checks all properties at once, live against the Smoobu calendars of every account.
4. Booking in the right account: when a guest books, BineBoost creates the reservation via the API directly in the Smoobu account of the booked property. The calendar blocks there immediately, and nothing in the owner's account setup changes: every owner sees their bookings in their own account and carries on there as before.

Day-to-day upkeep stays cleanly separated too: the nightly master-data sync runs per account, the property overview shows which Smoobu account each property belongs to, and disconnecting one connection only removes its properties from the booking engine. Photos and texts stay saved in case the account returns later.

Do bookings really land in the correct Smoobu account?

Yes. For managers that is the point that matters most. Every property is permanently assigned to its Smoobu account internally. Price requests are sent per account and merged; a booking is created exclusively through the API keys of the account it belongs to. There is no shared inbox and no manual re-assigning: the owner of apartment A sees the booking in their account, the owner of house B in theirs. BineBoost passes the stay, the fees and the tourist tax to Smoobu as separate items; down payment, security deposit and cancellation terms additionally go into the booking note. The reason comes from our own operation: a down payment amount we pass in when creating the booking is replaced by Smoobu's own rule, a security deposit amount is not (measured on 12 August 2026).

Which tourist tax and VAT rates apply to you, and how down payment and cancellation terms have to be worded, is not something the software decides. In practice both are shown separately; have your own rates and terms checked by a tax adviser and a lawyer beforehand.

What to look for in any multi-account solution

1. Booking routing: does the reservation land in the correct account automatically, or in a collective account from which it has to be distributed manually?
2. Live availability per account: are prices and calendars really read live from every account (no stale copies)?
3. Independence of the owners: does each keep their account, their invoicing and their own settings? Can a single connection be removed again?
4. Data protection: are the API keys stored encrypted and guest data processed in line with the GDPR (data processing agreement)?
5. Cost: a fixed price per property or a commission per booking? With many properties across several owners, commissions add up fast. How much that is over a year is shown by the commission calculator.

Frequently asked questions

How many Smoobu accounts can I connect?

There is no fixed limit: connect as many accounts as you manage. Each connection uses its own API keys.

Does every owner have to change anything in their Smoobu account?

No. They create an API key pair once in their Smoobu account and pass it to the manager. Everything else they carry on managing in Smoobu exactly as before.

Can I hide properties from individual accounts?

Yes, every property can be switched active or inactive individually, independently of its account. Billing counts the active properties, at least one.

What happens if an owner changes manager?

Their account's connection can be removed again. Their properties then disappear from the booking engine, and their Smoobu account remains untouched.

Does this also work with just one Smoobu account?

Yes. One account is the normal case, several accounts are an extension. If you connect only one account, you see the same booking engine.