Connecting several booking platforms without unnecessary return loops
Use Homadu as the central point for calendar exchange and keep the source of blocks clear.
Create one clear connection plan
With several rental platforms, connecting every calendar directly to every other calendar can be tempting. The same block can then return through several routes. Instead, create a plan where each platform sends its own calendar to Homadu and receives only the other necessary sources from Homadu.
Homadu tries to recognise your own returning events, but a clear connection plan remains important. Other platforms can name or identify events differently. Do not leave old direct connections active without knowing what role they still play.
Example with Airbnb and Booking.com
- Create an Airbnb calendar and a Booking.com calendar in Homadu for the same accommodation, each with its own import link.
- Edit the Airbnb calendar and select Booking.com as a source calendar for the export to Airbnb.
- Edit the Booking.com calendar and select Airbnb as a source calendar for the export to Booking.com.
- Add the corresponding channel-specific Homadu export link at each platform. Check old direct connections before removing them if necessary.
Check the other direction too
Your own Homadu event should be offered through both channel exports. An Airbnb event should be forwarded to Booking.com, and vice versa. After processing, compare known dates and check that the original source is still correct. If you add Vrbo later, check all source selections again.
iCal is periodic rather than immediate. Even correct connections involve processing time. For important changes, check availability on the involved platforms yourself; the connection does not guarantee that simultaneous requests are impossible.