Minibar charges, posted to Oracle OPERA Cloud
MinibarFlow follows check-ins and check-outs in OPERA Cloud and posts minibar charges to the guest folio. It works with the manual minibars you already have.
Start Your Free PilotWhat the connection does
Your attendants check minibars on a phone or tablet. The app gets its room list from Opera and sends the charges back, so nobody types minibar lines into Opera by hand.
Rooms follow Opera
Check-ins, check-outs and room moves show up in the app without anyone entering them. The app asks Opera for changes every 15 minutes during the day, less often in the evening and at night.
Charges go to the folio
Each item a guest has taken is posted to their folio with your transaction code, the quantity and the unit price.
A check every night
Overnight the app compares its rooms with Opera's in-house list and fixes what differs: occupied or vacant, guest name, departure date.
It only adds charges
Minibar charges are the only thing MinibarFlow writes to Opera. Reservations, room status and housekeeping status are left alone.
Three ways to send charges
Every hotel starts in Export only and changes mode when the team is ready.
Export only
Nothing is sent to Opera. Your team charges from the daily billing report.
Manual approval
Charges wait in a list. A manager approves them one bill at a time, or all at once.
Auto-post
When a room check is finished, the app reads the guest folio, then posts only what reception has not already charged.

What a charge looks like in Opera
Charges are posted one line at a time, on the cashier you choose, with your own minibar transaction code. The reference ties each line back to the room check it came from.
Example charge
- Transaction code
- Your minibar code
- Description
- Minibar Room 204
- Remark
- 2 Beer
- Quantity
- 2
- Unit price
- Your price, in your currency
- Reference
- MB-7K2QF4-3

What managers see in the Billing Report
One page per day, with an Excel export.
- Posted by App: the charges the app sent to the folio
- Matched on folio: lines reception had already charged, so the app did not post them again
- Included in rate: items covered by the rate code, recorded but not charged
- Action Required: charges waiting for a manager in Manual approval mode
- A daily summary of what the app posted and what reception charged
What happens when…
…the guest has already left
You choose, and you can set it differently for the departure day and for the days after. By default nothing is posted: the charge appears in the billing report and a manager deals with it. The other option is to have the app post it to your hotel's PM room. If Opera still shows the guest as in house, the charge goes to their own folio.
…the minibar is included in the rate
Tell the app which rate codes include it, and whether they cover the whole minibar or only certain product categories. The app still records included items for stock and reports, but does not charge them.
…a posting fails
The app tries again by itself, up to four times, waiting longer before each attempt. If Opera never answered, it looks for the charge in Opera by its reference before sending anything again. After the last attempt the line shows as failed in the billing report, and a manager can charge it by hand. If the connection itself stays down, your team gets a notification.
How the connection is set up
Four steps, most of them on our side.
- 1Your IT
Approval and details
Your Opera administrator approves the MinibarFlow integration and sends us the details in the list below.
- 2MinibarFlow
We set up the connection
We do it on our side, through the Oracle Hospitality Integration Platform (OHIP). Nothing is installed on hotel computers.
- 3Together
A test on a real reservation
We run a room check, post the charge and print a test folio, so you see the minibar line the way a guest would.
- 4Your hotel
Go live in Export only
You start in Export only and switch to Manual approval or Auto-post when the team is ready. All of this is part of the free 2-month pilot.
What your IT team provides
Six things from your Opera administrator. The last one is only needed if you want late charges posted.
- Your OPERA Cloud hotel code and region
- Integration credentials for your OPERA Cloud environment
- Your Opera administrator's approval of the MinibarFlow integration
- Business events switched on for check-in, check-out and reservation updates
- A cashier ID and your minibar transaction codes
- A PM room for late charges, if you want them posted
What it does not do
The connection works with OPERA Cloud. Opera 5 on premise is not supported. Expected arrivals are not read from Opera either: your team enters them in the app.
Connections to other PMS are planned. Until they exist, a hotel on another PMS can still use MinibarFlow: the team marks check-ins and check-outs in the app and charges from the daily billing report.
Guest data
From Opera, the app keeps the guest name, arrival and departure dates, rate code and reservation number on the room, and clears them when the guest leaves. Guest names are anonymized after 30 days in room checks and after 90 days on billing records. Notifications never contain a guest name. The App Privacy Notice has the details.
Questions from front office and IT
Short answers about the OPERA Cloud connection.
No. The connection works with Oracle OPERA Cloud only.
No. MinibarFlow works with the manual minibars you already have. Your team uses phones or tablets, on iOS or Android.
In Auto-post mode the app reads the guest folio before posting and only sends what reception has not already charged. Every line has its own reference, and if Opera did not answer a send, the app looks for that reference in Opera before sending again.
Yes. In Manual approval mode, charges wait in a list until a manager approves them, one bill at a time or all at once.
The room check works offline. It syncs when the device is back online, and the charges are handled then.
Running OPERA Cloud?
Try MinibarFlow free for 2 months. Full access, no commitment.
Start Your Free Pilot