Fixing Reconnection Behavior for Booking.com

When we connect a new Booking.com listing and merge it with a property, the pricings and availability with reservation blocks are passed onto the Booking.com calendar within minutes. Unfortunately, it does not behave the same if we reconnect an existing/already merged Booking.com listing. When we reconnect a Booking.com listing, it only pushes the pricing to the listing, neither availability nor existing reservation blocks. As a result, the property becomes vulnerable to double booking during the reconnection process. Given that it's a reconnection, having higher chance of existing reservations, and we don't have a manual syncing process/button, it becomes very concerning to have Hospitable behave like this.

So far, my understanding is that after talking with the support team, Hospitable does not send the same events to Booking.com when there is a reconnection instead of a new connection process.

Also, considering that Hospitable is now able to pull Booking.com listings to Hospitable, it feels that reconnection should be improved to prevent any unwanted double booking scenarios, when someone is trying to debug a something with Booking.com.

Thank you