Inbound: what you import
Each marketplace publishes an iCal address for your listing. Paste it into 1Melo once and those reserved dates start blocking your direct booking page automatically. Connect as many as you list on.
Calendar sync
The fastest way to lose a guest is a double booking. 1Melo connects the calendars you already keep, so the dates you have sold in one place close in the others.
Each marketplace publishes an iCal address for your listing. Paste it into 1Melo once and those reserved dates start blocking your direct booking page automatically. Connect as many as you list on.
1Melo gives you one iCal address of your own. Add it to each marketplace and your direct bookings, imported events and manual blocks all close those dates there too.
iCal is the format every major platform agrees on, and it is a polling format. Nobody pushes anything: each side fetches the other's file on its own schedule. That has two consequences worth being blunt about.
Changes are not instant. A booking taken on one platform becomes visible to another when that other platform next fetches. Minutes to hours is normal across the industry. Any tool promising real-time synchronization over iCal is describing something the format cannot do.
A short overlap window exists. Between the moment a marketplace booking is made and the moment 1Melo next fetches that feed, those dates are not yet known here. This is inherent to iCal, not specific to 1Melo.
An iCal feed is a complete snapshot rather than a list of changes. 1Melo treats it that way: on each run it compares the whole feed against what it imported last time. New events are added, changed dates are updated, and events that have disappeared from the feed are marked removed — which is how a cancellation on another platform frees your dates here.
Your published feed carries occupancy and nothing else. Every entry is a plain reserved block. It never contains a guest name, an email address, a phone number, a price, a confirmation number or the internal note you wrote on a maintenance block.
Nor does it say why a date is taken. A direct booking, an imported Airbnb stay and your own week in the property look identical to anyone reading the feed.
Not every closed date is a booking. Owner stays, maintenance windows and anything else can be blocked by hand, with a private note for your own reference. Those blocks behave exactly like a booking as far as availability is concerned: they close the dates on your booking page and they go out on your feed.
Questions
Any platform that publishes an iCal feed, which includes Airbnb, Vrbo and Booking.com. 1Melo does not use marketplace APIs and is not partnered with any of them — it reads the standard iCal address each platform gives you.
iCal is a polling format, so it depends on how often each side fetches. 1Melo re-checks your connected feeds on a schedule, and each marketplace fetches yours on its own. In practice changes travel in minutes to hours. No iCal-based tool can be instant.
Three kinds of occupancy: your direct bookings, the events imported from other calendars, and any manual blocks you have set. Each appears as a plain reserved block with no guest name, no price and no internal note.
Yes. Cancelling a booking releases its dates immediately and they drop out of the next feed fetch. The reservation record itself is kept — nothing is deleted.
Yes. Owner stays, maintenance and any other reason can be blocked by hand. Those blocks hold the dates on your booking page and are published on your outbound feed, so the marketplaces close them too.
Every sync run is recorded, so you can see when a connection last succeeded and whether it failed. A feed that stops responding does not silently drop dates — the events it already imported stay in place until a successful run says otherwise.