OHIP Opera Room Charge
A Module for Hotels 📝 Note: This module requires an active PMS/HMS API subscription. ⚠️ An additional monthly subscription fee of 89.00 EUR applies for access to the hotel PMS/HMS integration service (e.g., Opera OHIP, Infor, Cloudbeds, Guestline, TrackHS, WebRezPro ...). This fee covers: - Secure API access to the guest folio system - Real-time guest lookup and room charge posting - Ongoing support and maintenance of the integration
1. POS Sale Creation The process begins on the Odoo Point of Sale interface, where the cashier creates a new sale. Products are added to the cart just like in any regular POS transaction. At this point, the order is ready to be processed for payment.
2. Proceed to Payment Once all items are added to the sale, the cashier proceeds by clicking the “Payment” button. This action takes the user to the payment screen, where different payment methods are available. This step prepares the transaction for finalization, either by traditional methods (cash, card) or by charging it directly to a guest’s room using the integrated Room Charge option.
3. Select "Room Charge" and Search Guest On the payment screen, the cashier selects the custom "Room Charge" payment method. A popup window appears, allowing the cashier to search for a hotel guest. This can be done by entering the guest’s last name, room number, or reservation reference. The system then queries the PMS (Property Management System) in real time to locate the guest’s current folio.
4. Guest Found and Posting the Charge
Once the correct guest is found, their details are displayed in the popup, including room number and name. The cashier reviews the guest info, then clicks the “Post” button to send the sale to the guest’s room. The system confirms the operation, and the POS transaction is marked as paid. A log entry is generated to record this posting.
5. POS Log Entry Overview
After posting the charge, the backend system logs detailed information about the transaction. This includes the POS order ID, timestamp, guest details, room number, amount charged, and whether the posting to the PMS was successful.
6. PMS Side - Folio Overview
On the PMS side, the guest's folio is automatically updated with the newly posted charge. The description includes details such as the POS source, items purchased, and total amount. This posting behaves like any other hotel charge, and is visible to front desk staff for review and billing at checkout.
7. PMS Folio Entry Details
The folio entry within the PMS includes granular information such as the charge type, department code (e.g. restaurant, minibar), tax breakdown, and reference to the POS order. This level of detail ensures proper reporting and financial reconciliation between the POS and PMS systems.
Support
%201.svg?90e23fd)
Need
Help?
tom@beesql.com
Got questions or need help? Get in touch.
tom@beesql.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module