Merge Properties (for Booking.com Connection)
Purpose
The Merge Properties feature allows Operations to combine multiple separate Airbnb properties into a single property for Booking.com integration. This is needed because Airbnb and Booking.com structure their listings differently:
On Airbnb, each room must be listed as a separate property, since Airbnb doesn’t support multiple rooms under one listing.
On Booking.com, you can list multiple rooms under a single property, each with its own rate plans.
For landlords who rent multiple rooms in the same building (e.g., a guesthouse with 5 separate rooms), this means they’ll have five Airbnb properties but one Booking.com property with five rooms. The Merge Properties feature bridges this difference and allows a smooth Booking.com connection.
When to Use This Feature
You should use Merge Properties when:
The landlord has multiple Airbnb room listings that represent different rooms within the same property.
The landlord’s Booking.com listing groups those rooms under a single property.
You need to connect these multiple Airbnb-based properties in Hububb to one Booking.com property.
If the landlord has only one Airbnb property and one Booking.com property (e.g., a single apartment), then you don’t need to use merging — just use the “Connect Single Property” flow.
User Flow (Operations)
What Happens Behind the Scenes
When the Merge Properties action is triggered, several steps happen automatically.
Child Property Verification
The system checks that all selected Airbnb properties:
Belong to the same landlord,
Exist in the database, and
Have rooms, rate plans, and pricing data.
If any are missing, the merge is stopped to prevent broken setups.
Creating a Parent Property
A new parent property is created in Hububb and on Channex. This new property acts as the single point of connection for Booking.com and represents the combined structure of all selected child properties.
The parent property aggregates:
Total number of rooms, beds, and bathrooms,
Combined capacity, pricing, and amenities,
The address and base settings from one of the child properties.
All images from the child properties are also copied to the parent.
Creating Rooms & Rate Plans
For each child property:
A new room is created under the parent property on Channex.
A rate plan is generated based on the child property’s pricing.
Availability and restrictions are copied over from the child property to ensure consistency.
This builds a structure in Channex that matches how Booking.com expects to receive it (one property, multiple rooms).
Linking and Status Updates
Once rooms and rate plans are created:
Records are saved in Hububb linking each child property to the new parent.
Each child property’s status is marked as Merged, so they no longer appear as independent listings for channel connections.
The parent property is indexed in search and ready for Booking.com connection.
Connecting to Booking.com
After merging, the system immediately initiates the Booking.com connection using the parent property. From this point, the connection process follows the same flow as a standard Booking.com integration (test, mapping, activation).
Key Notes
Merging is permanent — once properties are merged into a parent, they cannot be connected individually to other channels. Make sure to select the correct set of child properties before proceeding.
All availability and pricing updates should now happen on the parent property. These changes are automatically synced down to the original rooms behind the scenes.
Why This Matters
This feature eliminates manual work for Operations and prevents incorrect mapping scenarios. Before it was introduced, there was no way to connect multiple Airbnb rooms to one Booking.com property, which caused mapping failures or forced landlords to restructure their listings.
With Merge Properties, Hububb now reflects how Booking.com actually structures properties, while still allowing flexible per-room listings on Airbnb.
Setup in Channex
When the Merge Properties functionality is used (e.g., merging 5 Airbnb properties into one Booking.com property), Hububb creates an additional “parent” property in Channex that represents the merged structure.
For example, if a landlord has 5 separate Airbnb properties (each representing a single room), the resulting Channex setup looks like this:
This means there are now 6 properties in Channex: 5 original Airbnb child properties, and 1 parent property with multiple rooms mapped for Booking.com.
Calendar Synchronization Between Merged Properties
The key challenge after merging is keeping calendars in sync between the individual Airbnb properties and the merged parent Booking.com property.
Whenever a new booking comes in through any OTA (Airbnb or BDC), Hububb receives it via Channex webhooks. The system checks if the property involved is part of a merge, either as:
A child property (Airbnb), or
The parent property (Booking.com).
If it is part of a merge, both calendars are updated:
The original Airbnb property’s calendar (e.g., Room 1)
The corresponding room in the parent property’s calendar (e.g., Room 1 within the merged BDC property)
Similarly, any availability or restriction updates to a calendar are mirrored across the merged pair. This ensures that if a booking is received for Room 1 on Airbnb, the corresponding Room 1 in the merged parent property on BDC is immediately blocked, preventing double bookings.
Calendar updates must always be made through Hububb, not directly in Channex. Directly modifying availability or restrictions in Channex bypasses Hububb’s synchronization logic and can lead to inconsistent calendars and double bookings. Hububb is the single source of truth for merged calendars.
Merged "Parent" property in Channex connected to Booking.com: ![[Screenshot 2025-10-03 at 15.21.58.png]]
Child Airbnb properties in Channex connected to Airbnb: ![[Screenshot 2025-10-03 at 15.22.56.png]] ![[Screenshot 2025-10-03 at 15.23.04.png]] ![[Screenshot 2025-10-03 at 15.23.10.png]] ![[Screenshot 2025-10-03 at 15.23.19.png]] ![[Screenshot 2025-10-03 at 15.23.27.png]]
Adding More Properties to an Existing Merge
Operations can add additional properties to an already merged parent property when new rooms are added to the landlord’s inventory.
How It Works (Operations UI)
What Happens in the Backend
This feature gives Operations flexibility to expand existing merged setups as landlords grow their inventory — without having to redo the entire Booking.com connection process from scratch.
![[Screenshot 2025-10-03 at 15.36.36.png]] ![[Screenshot 2025-10-03 at 15.36.55.png]]