You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been following the application for a long time and since I have experience in the hotel industry I will allow myself to tell you what is really missing for it to be adopted:
Currently it's just a portal management of a hotel website
The application must manage the portal booking but also the reception of customers with check-in and check-out.
A customer may leave the hotel two days before the check-out date, so the rooms must be returned to the availability stock in order to resell them.
There is also the case of customers who cancel their booking
It's also necessary to manage the extras at the time of the customer's stay (in the current case the hotel must do the work on another application)
Allow the change of rooms, because a customer may not be satisfied with the room and requires its change. And then update the availability of the rooms (their numbers)
Integrate employee traceability! There is direct booking by the customer on the web but also a customer can call the hotel by phone and request a reservation, so the employee must book him and we need to know this employee because there are groups of different work in the morning and at night. This also helps to assess employee performance.
I content myself with these remarks, I try to support you to go as far as possible with your application and give it a lot of potential so that it is fully adopted in the hotel industry.
And at the same time I congratulate you for the work already done!
The text was updated successfully, but these errors were encountered:
Thanks for your contribution to our project and for providing insight into the hotel industry.
Currently, QloApps implements all of these functionalities except for managing customer extras during stay. We are working on this feature and will provide this with the next release of QloApps. In the next release Admin will be able to create normal products in QloApps and assign them to orders.
The new version will will be released in the first week of april.
Here are the points related the other queries.
Admin can manage customer check-in and check-out from the order page below order status panel.
When the admin check-out a specific room before its check-out date, the room becomes available for booking.
Rooms cancellation and refund process is implemented in QloApps by default, Follow this blog to check how can you implement refund process.
Rooms can be easily rallocated bt using reallocation buttin on order page
Rooms can be reallocated with another rooms or admin can also swap two occupied rooms with each other if the booking dates are same.
In QloApps Admin can create a direct booking from backend. Check out How to create booking from QloApps backend. When admin creates booking from backend, QloApps save which employee have created the booking.
I have been following the application for a long time and since I have experience in the hotel industry I will allow myself to tell you what is really missing for it to be adopted:
I content myself with these remarks, I try to support you to go as far as possible with your application and give it a lot of potential so that it is fully adopted in the hotel industry.
And at the same time I congratulate you for the work already done!
The text was updated successfully, but these errors were encountered: