As we start to see travel slowly picking up again, we’ve put together the most important resources and advice to help you turn demand into bookings, safely and confidently. Here you’ll find the newest insights and initiatives.
Join the #Rebuilding conversation in the Partner Community
Find out how to get set up, and read about our services and features.
All of our best solutions, organised by your business needs.
Connect online with fellow Booking.com partners.
Find tips and advice to help you through this time with the hashtag #Rebuilding
Stay informed with the latest Booking.com developments, industry insights and expertise
Growing Together is our ongoing promise to build a stronger era of partnership. Explore our new commitments and the progress we’ve made on our previous ones.
That inventory +1 is an excellent idea, thank you, i'll do that! Most of the grief I have, (and it's not much grief, but just enough to be annoying), is with last minute bookings scams/issues, in fact I googled "fraudulent last minute bookings" today and got some useful information. Re prepay template, not sure of what you mean, but for regular bookings guests know they pay an immediate deposit of 50% and the balance 2 weeks before arrival, as well as a damage deposit, though if they regular booking.com members I will often not charge the damage deposit. Anyway thanks again, much appreciated...
Can't you take damage deposit by credit card?
Thanks for your detailed reply, the issue with using a stolen card is that the guest stays for 2-3 days, and 2 weeks later you get a charge back from the issuing bank and are out of pocket for $300. Today for example an obvious fake booking was made, the postal address provided did not exist, plus a few other clues, the credit card was declined, I then had to wait 15 hours before I was able to cancel the booking, mean while my calendar was blocked for that period. Number 3 on your reply stated to "add it to the new reservation template on top", add what exactly?
Thanks for your reply, all resolved now, apparently it was a network error, a bit frustrating in that I probably wasted a couple hours trying to resolve such a simple problem...