Hi everyone,
I’m posting here because my support ticket is currently stuck in the queue, and my Booking.com listing is completely dead in the water (showing as Closed/Unbookable on the Extranet), I really need a Hospitable staff member or engineer to take a look at our connection mapping.
Here is exactly what happened:
-
The Background: We had multiple mapping issues with this specific Booking.com listing previously. To fix it, we created a duplicate listing, muted it, disconnected it from Booking.com, and then reconnected the muted one. It initially looked perfectly fine.
-
The PriceLabs Trigger: The next day, we integrated PriceLabs. As required, we unpublished the listing temporarily to finalize the pricing settings.
-
The Glitch: After doing this, the Booking.com listing completely vanished from our Hospitable properties dashboard. Simultaneously, on the Booking.com Extranet side, the listing’s status flipped to "Closed / Unbookable."
-
Where it stands now: We called Booking.com support directly. They manually forced the status back to "Open / Bookable" on their end, but they explicitly stated that Hospitable must push a fresh calendar update to finalize the connection and normalize the listing.
-
We have tried forcing Smarty to push a sync update, but nothing is going through. The listing remains hard-locked as "Closed/Unbookable."
Because the listing has dropped off our Hospitable dashboard, we can't manage it, and standard support is taking too long to reply.
Could someone from the product or engineering team please look into our backend account mapping to see why this listing vanished from our dashboard and force a full API calendar resync to Booking.com?
Thank you!
