OPERA Cloud breakfast report and package posting: a practical guide

How breakfast packages work in OPERA Cloud, why the breakfast list rarely matches the morning, and how to get covers back into OPERA.

Updated 18 October 2026

At six in the morning someone prints the breakfast list. By half past seven it has coffee on it, three names crossed out twice, a room number written in the margin, and a note that 214 says breakfast is included but the list says it isn’t. At eleven, someone tries to make it match OPERA.

This guide is for the people who live with that list: front office, F&B and night audit at hotels on OPERA Cloud. It explains where the breakfast list comes from, why it so often disagrees with the morning, and what it takes to get the morning back into OPERA.

An illustrative morning with a printed list. The rooms are made up.

How OPERA Cloud knows a guest has breakfast

In most OPERA Cloud hotels, breakfast is a package. Oracle describes package elements as “additional products or services included in the rate or sold in addition to the rate” (Oracle: Package Codes). A breakfast package is set up once and then reaches a reservation in one of two ways:

Through the rate code. A rate such as “room and breakfast” carries the breakfast package, so every reservation on that rate is entitled to it.
Added to the reservation or block. A guest on a room-only rate buys breakfast at check-in, or a group’s contract includes it.

Each package has a few settings that decide what OPERA does with it:

Posting rhythm: how often it posts, for example every night or only the first night.
Calculation rule: per adult, per child, per person or per room.
Transaction code: where the revenue goes when it posts.
Allowance (with Advanced Packages): a value the guest can spend, with OPERA handling what happens when they spend less or more.

Not every hotel models breakfast this way. Some put it in the rate description, use separate rate codes or market codes, or note it in comments. If your property does, the list you print will only be as good as those habits.

OPERA posts breakfast because a guest is entitled to it. What happens at the door has to be added by someone.

Posting happens at night audit, not at the door

This is the part that causes most of the trouble. Package items are posted to the reservation “during End Of Day, based on the Frequency specified” (Oracle). OPERA posts breakfast because the guest was entitled to it, not because anyone saw them eat.

With allowance-based packages, OPERA does expect something to happen during the day: the actual breakfast is posted “manually in OPERA Cloud or posted by an integrated system” such as a point of sale, and at the end of the day OPERA settles the difference (Oracle):

Consumption up to the allowance goes to the package ledger.
Anything above the allowance goes to the guest’s bill as an overage.
An allowance that isn’t used is posted as package profit.

Either way, OPERA only knows who ate if someone tells it. If no one does, the system reports what guests were entitled to, and the morning that actually happened lives on paper.

Where the breakfast list comes from

Many hotels print their breakfast list from an OPERA report that lists in-house reservations with their breakfast packages, or from a package forecast. The exact report depends on your OPERA version and on how your property has set up packages, which is why two hotels in the same chain often use different ones.

Whichever report you use, it answers the question “who is entitled to breakfast tomorrow?”. It can’t tell you:

who actually came, and when;
who wasn’t on the list but should have been: a late booking, a room move, a breakfast bought at the desk;
who ate and isn’t entitled, and should have been charged.

Hotel staff run into the edges of these reports often enough that the questions keep coming up on the OPERA users’ forum, for example “Breakfast report for opera cloud” and “Breakfast Report doesn’t filter Included / Excluded packages”. If your list mixes guests whose breakfast is included with guests who need to pay, the restaurant has to sort that out at the door, usually by calling reception.

Making the list better before the morning

You can do a lot with OPERA’s own setup before you change anything else:

Use one breakfast package per meaning. “Included in rate” and “bought separately” are easier to report on as different package codes than as one code with notes.
Keep breakfast out of free text. A comment that says “BB” is invisible to reports and to any integration. If breakfast lives in the rate description, consider adding the package to the rate code.
Agree on one report and one print time. The list printed at 22:00 doesn’t know about the 23:30 walk-in. Print after night audit, or as late as the restaurant can live with.
Decide what happens to guests not on the list. Write it down: charge to room, check with reception, or let them in and fix it later. Many of the calls to the desk come from this one gap.

Getting the morning back into OPERA

However good the list is, someone still has to record what happened. With paper, that is the job after eleven: tick marks back into reservations, charges for the guests who weren’t included, and a guess about the names nobody could read.

A digital check-in at the door can record it as it happens, or once the tablet is back online. Here is how Kløvr does it, as one example of what to look for:

What reaches OPERA depends on how the hotel has set up breakfast. The table below says the same.

At the door	What lands in OPERA
Breakfast is included through a breakfast package	Kløvr is adding this: the breakfast will be recorded as consumed against that package. For now nothing is posted to OPERA; the tablet keeps the list of who ate
Breakfast is not included	A charge is posted to the guest’s bill with the hotel’s breakfast transaction code
Breakfast is included in the rate, with no package	Nothing is posted, and Kløvr keeps the count

OPERA has no single standard field for “breakfast included”, so Kløvr follows the rules each hotel already uses: packages, rate codes or market codes. When the rules can’t decide (an unusual group arrangement, say), the guest is sent to reception rather than charged or waved through on a guess.

What hotel IT should know about OHIP

Any system that writes breakfast into OPERA Cloud should do it through the Oracle Hospitality Integration Platform (OHIP), Oracle’s official API platform for OPERA Cloud. A few things worth knowing when a vendor says it integrates:

Partners build and test against Oracle’s own sandbox environments before any hotel connects.
The hotel’s own OPERA administrators approve a partner’s access to the property. It isn’t a back door.
Nothing from OPERA has to be installed on site.

A short checklist

Breakfast is a package on the rate code wherever possible, not a comment.
Included breakfast is a package; breakfast bought at the door posts to its own transaction code.
The list is printed after night audit, from one agreed report.
There is a written rule for guests not on the list.
Covers are recorded the same day, paper or tablet. Where OPERA needs it, that’s a package consumption or a charge; Oracle’s guide to managing package allowances and charges covers the manual route.