easistudio wrote:Just my opinion but I wouldn't trust reception staff with backend access to your system.
Thanks for the input! One thing we thought of as a potential issue is what if the site owner used multiple booking solutions, ie one for there systems internally and one for web access. I figured we would either need to build some sort of import / export feature or build a complete solution to make our solution powerful enough to be able to do the whole process and suggest to the site owners (who buy our solution) to use only our solution for all bookings. Based on that your input is very helpful. I was thinking of a backend, but your are right the reception staff needs access to CERTAIN things, but not the whole backend.
As far as why we are considering building a booking system in OC, it is simple. I have used OC for a little while now and it is a very powerful CMS. The menuing, the cart, payment handling, affiliates, multiple domain support, multiple store support and much of the core logic supports so many aspects a hotel or even multiple hotel environment needs. It's multiple nesting menus and several other things make it a natural base for a hotel booking system. All that is missing is the booking solution.
However, at this point, I haven't received enough interest to spend the extra time to make the solution I will end up creating a global solution so I may just build it (initially) for our needs and then if there is interest consider enhancing it down the road to offer it as a solution to others.
