I often get feature requests from customers. Just recently I had one such request regarding availability management. The client had an as yet unencountered availability requirement that doesn’t fit into the current system scope.
On the surface it was a standard setup with full week bookings going from Sunday to Sunday. But, they wanted the ability to add on extra nights to the full week booking and not have the extra nights available otherwise. So you can buy extra nights on the condition you have already booked at least one full week. This would have required a custom solution; the integration of an extra step giving the customer the option to add on extra days to the booking. I considered going down this route but decided there was no market for a feature such as this (I’ll explain why later on) so decided against adding it as a product feature. I thought I’d lost a customer until I considered the problem for a little while and realised there is a reasonable solution.
Availability already has an “Active” field (we are delving into the database here). If I expose this not active data in the administration panel but not on the customer facing side then (if I implement one small change) I can use the system as it currently stands. I do this by using the in-built products feature; I add the extra days on as products then block off any extra days as they come through on a booking.
Although this system will work, there are some shortcomings you have to work around. The obvious one is the extra work involved. It removes some of the automation from the booking process. Once a booking is made, you have to login into the administrator panel and block of the extra days manually - they would also have separate booking ID’s and a value of zero (which is not ideal). In addition, you would have to do this reasonably quickly.
Which brings me to my next point, if you don’t block-off the extra availability promptly, you run the risk of someone booking the following week and ending up with a double booking and the extra headache that comes with!
A final drawback is that as you can’t assign products to particular availability slots, only on a site-wide basis, you could not account for seasonal variations in pricing for the extra day. So if two bookings were made on 1st February one for a peak summer week the other for an off-peak February week, in both cases an extra night would cost (say) £100. Again, far from ideal!
I told the client, there wouldn’t be much need for this conditional extra days feature. Not only have i never been asked for this before, I have not heard of any rental properties that operate this way. It is too cumbersome from an administrative standpoint, but it also has some more compelling drawbacks.
That extra day or two added on to the booking eats into your next week meaning – if you are running on a week to week basis – you can’t book out the following week! This makes no business sense at all. If a system is setup this way, you could be losing the income on one full week just for the sake of booking an extra day on the previous week. It could also disrupt your regular changeover days. Are your cleaners and other staff on the ground flexible enough to accommodate?
More often than not, being really flexible on dates and offering many options is not effective from a cost/benefit standpoint. My advice is keep things simple and straightforward unless you have the resources to cope with the extra complexity.
Do you have use conditional extra days or think it could be a valuable feature? I would love to hear your opinion.
www.propertyrentalsoftware.com