i'm having some quite big issue with an unsatisfied customer. I was using uc_hotel for her relais, but it seems like the system just asks how many adults / children are getting in, and which room type they want.

The problem:
1) there are 50 free double rooms (max. 2 people / night)
2) 6 friends (3 couples) want to make a reservation
3) they search for availability for 6 persons
4) uc_hotel says there is no place for them to stay, because the limit for room is 2 people / night and they selected themselves to be 6 people.

My customer didn't mention this detail in his specifications nor while the development process, until now. Seems like she wants to sue me because the site is not ready yet, saying all booking sites work this way (they ask "adults" "children" and "rooms" or "adult per room").

I need to show her some example of sites using this module, to prove that the way this module works is *indeed* usable, even if working in a different way. Could you post some links ? Thanks


larowlan’s picture

There's a demo link on the project page.
Fwiw if you wrote a custom module you could add the features described using the form api and some form alter hooks.

dman’s picture

Well I dunno about how the rest of the world does it, BUT ...
I thought I'd see what you describe, so I picked an expensive chain hotel randomly and looked to see what they do.
I found that just trying to book 8 guests into https://www.hyatt.com/ produced the message

The number of adults and/or children you have selected exceeds the maximum allowed per room. Please click here to return to the previous page and reduce the number of guests you have selected to view availability.

... and [click here] didn't work.
It doesn't seem that any Hyatt hotel in all of France has room for 8 guests! Even with multiple rooms. I didn't look much further, but it seems like this feature is a special request.

If a place with the budget of the Hyatt doesn't do this, I think your client may be asking a bit much for a one-off site.

If this feature request not in the contract, it's not in scope. However, I do understand that neither of you would have considered it at the outset.
* if this was a feature the client required, it should have been specified.
* if this was a feature you could have anticipated, you may have itemized or excluded it.


It's also a pretty fuzzy area. When you are dealing with a client who isn't familiar with technical specifications or how websites work, they can come up with some pretty stunning assumptions. Like "It should collect the emails of anyone who even looks at a page without their having to fill in a form" sort of assumptions.

They can complain about undelivered features - if there was a feature like this that was explicitly in the contract that you didn't meet, that's a problem.
If this wasn't actually specified in the contract and you delivered something that matches the minimum described in their functional spec, then there's no way anyone can "sue".