Reference · built on requestOperator by FibricHospitality & guests

Cover Forecast

Projects covers per outlet and service from the house count, meal packages, and group blocks, and proposes prep quantities and buffet pars.

Request accessPricing ↗

About

Breakfast covers follow from who is in the house. Cover Forecast reads arrivals and the house count from your property management system, the reservations whose package includes a meal, and the group blocks with a banquet on the books. It reads past covers per revenue center from closed checks in Oracle MICROS Simphony or dine-in orders in Toast, and lines them up with public holidays from Nager.Date, so a Monday that is a holiday is forecast as one.

For each service it proposes a cover count per outlet, then the prep quantities and buffet pars that follow from it. The chef or outlet manager approves. It changes no par and prints no prep sheet on its own.

This is a reference listing. It documents what Fibric would read from Cover Forecast and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Reservation statistics and pace for the property through the OPERA Cloud rsv module, getReservationStatistics and getReservationPace, for arrivals and house count by date
  • Reservations consuming a package on a given date through getReservationsByPackage, so a breakfast-inclusive rate counts as covers
  • Group blocks and their pickup through the blk module, getBlockDailyStatistics and getBlockStatistics, for the services a group will fill
  • Reservations in Mews through reservations/getAll with PersonCounts per age category, and availability through services/getAvailability
  • Past covers per revenue center from closed Simphony checks, GET /api/v1/checks with includeClosed=true, using guestCount and openTime
  • Past dine-in covers in Toast from GET /ordersBulk by businessDate, using numberOfGuests and the dining option
  • Public holidays by country and subdivision from Nager.Date, with holidayTypes such as Public, Bank, and School

Proposed actions

  • Target capability: propose a cover count per outlet and service, with the house count, packages, blocks, and history it was built from
  • Target capability: propose prep quantities per menu item from the cover count and your recipe yields, for the chef to approve
  • Target capability: propose buffet pars per station and refill points for the service, replacing the standing par for that day only
  • Target capability: propose a revised count when block pickup or arrivals move after the forecast was approved, with the delta and its cause

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Set breakfast pars from tonight's house

    The house count and package reservations from OPERA Cloud, with closed Simphony checks for the same weekday, give tomorrow's breakfast covers. The operator proposes buffet pars per station for the outlet manager.

    With Oracle OPERA Cloud, Oracle MICROS Simphony

  • Prep for a holiday brunch

    Nager.Date flags a public holiday. Past covers from Toast on the same holiday and the Mews reservation count set the projection. The chef approves the prep quantities.

    With Holidays & FX Reference, Toast, Mews

  • Re-forecast when a block washes

    Block daily statistics show a group cut its rooms. The operator proposes a revised cover count and lower pars for the affected services, with the delta and its cause.

    With Oracle OPERA Cloud

Requirements

  • An Oracle OPERA Cloud connector with the rsv and blk API groups subscribed, or a Mews connector with reservation and service read access
  • An Oracle MICROS Simphony or Toast connector for each outlet, with closed checks or bulk orders readable for the history you want
  • Recipe yields and buffet par sheets per outlet, in the units your kitchen uses, so a cover count becomes quantities
  • The country and subdivision of each property, for the Nager.Date holiday calendar
  • A map from packages and rate codes to the outlet and meal period they entitle
Authentication
Reads the property system through the OPERA Cloud application key and bearer token or the Mews ClientToken and AccessToken your connector holds, reads checks through the Toast or Simphony connector, and reads Nager.Date without a key.

Limits

  • Banquet event orders sit in a sales and catering system such as Amadeus Delphi. A banquet count arrives only if you export it.
  • OPERA Cloud allows a 90-day span on getReservationStatistics and getBlockDailyStatistics, so a season is read in slices.
  • It forecasts covers and proposes quantities. It does not order food, change a menu, or post a purchase order.
  • An outlet with no POS history for a meal period is forecast from house count and packages alone, and the proposal says so.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Cover Forecast ↗

Questions and answers

What does a person approve?
The cover count for each outlet and service, and the prep quantities and buffet pars that follow from it. The proposal shows the house count, packages, blocks, holidays, and history it used. The chef or outlet manager approves, edits, or dismisses.
What record is left?
A forecast receipt per service: the inputs read and when, the projected covers, the approved pars and quantities, who approved them, and the actual covers from the POS once the service closes, so the next forecast learns from the miss.
Does it place orders or change menus?
No. It proposes counts, quantities, and pars. Purchasing, menu changes, and staffing stay with the people and systems that own them. Nothing is written to the POS or the property system.
Ask about Cover Forecast

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy