Reference · built on requestOperator by FibricHospitality & guests

Linen Par

Compares clean linen on hand and laundry output with the rooms forecast, and proposes a linen order or a laundry shift change.

About

Linen runs out on the day the house fills, not the day the count was taken. Linen Par reads the clean linen count per item from the sheet or inventory system where housekeeping records it, the laundry shifts on the roster, and the occupancy forecast from the property management system: OPERA Cloud's reservation statistics and housekeeping facility forecast, or Mews reservations by date. It works out the days of cover per item against the rooms due to turn.

When cover falls under the par you set, it proposes a purchase order for the item, or an added laundry shift if the shortfall is throughput rather than stock. The executive housekeeper approves. An order or a shift is written once, with a receipt.

This is a reference listing. It documents what Fibric would read from Linen Par 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

  • Clean, soiled, and in-process counts per linen item from a Google Sheet, read by range, or from records in an Airtable base
  • Item stock on hand, reorder level, and preferred vendor in Zoho Inventory, and the purchase orders already open for linen
  • Arrivals, departures, and occupancy by date from OPERA Cloud getReservationStatistics, and the housekeeping attendant and task forecast from getFacilityForecast
  • Reservations by date in Mews through reservations/getAll, with PersonCounts, for properties on Mews
  • Laundry rosters in Deputy through Roster/QUERY by area and date, or shifts in 7shifts by location and department

Proposed actions

  • Target capability: propose a purchase order in Zoho Inventory for the linen item below par, with quantity, vendor, and the cover calculation attached
  • Target capability: propose an added laundry shift in Deputy through POST /api/v1/supervise/roster, with start, end, and area, for the manager to publish
  • Target capability: propose a par change for an item when weeks of counts show the standing par is too high or too low
  • Target capability: propose a count request to housekeeping when the last count is older than the interval you set

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

What you can build

  • Order sheets before the sold-out weekend

    OPERA Cloud statistics show a full house through the weekend and the count in the Google Sheet gives less cover than par. The operator proposes a Zoho Inventory purchase order to the preferred vendor for approval.

    With Oracle OPERA Cloud, Google Sheets, Zoho Inventory

  • Add a laundry shift instead of an order

    Stock is above par but the Deputy roster shows one laundry attendant on a heavy turnover day in Mews. The operator proposes an added shift in the laundry area for the manager to publish.

    With Deputy, Mews

  • Ask for a fresh count first

    The last towel count in Airtable is older than your interval and arrivals in Mews are rising. The operator proposes a count request to housekeeping before it proposes any order.

    With Airtable, Mews

Requirements

  • A linen count kept per item in Google Sheets, Airtable, or Zoho Inventory, with a date on each count
  • An Oracle OPERA Cloud connector with the rsv and hsk API groups subscribed, or a Mews connector with reservation read access
  • A Deputy or 7shifts connector with the laundry area or department on the roster
  • Par levels per item and room type, and the pieces of each item a room turn consumes, so occupancy becomes linen
  • Laundry output per shift in pieces or weight, from your own records, for the throughput side
Authentication
Reads counts through the Google Sheets or Airtable credentials your connector holds, reads stock and proposes orders through the Zoho Inventory OAuth token, reads the property system through its connector, and proposes shifts through the Deputy permanent token or the 7shifts access token.

Limits

  • It counts what housekeeping counts. Linen in guest rooms, on carts, or at an outside laundry is known only if a count includes it.
  • OPERA Cloud allows a 30-day span on getFacilityForecast and 90 days on getReservationStatistics, so a season is read in slices.
  • No purchase order is issued, no shift is published, and no par is changed until the executive housekeeper approves.
  • Discard and rewash rates are yours to supply. It does not infer linen loss from the counts alone.

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 Linen Par ↗

Questions and answers

What does a person approve?
Every purchase order, shift, par change, and count request. The proposal shows the count and its date, the forecast it used, the days of cover, and the quantity or shift proposed. The executive housekeeper approves, edits, or dismisses.
What record is left?
A receipt per proposal: the count read, the occupancy forecast, the calculation, the order or shift as approved, who approved it, and the Zoho Inventory purchase order id or Deputy roster id, so the order can be cancelled or the shift removed.
Does it need a linen tracking system?
No. It reads the count wherever housekeeping keeps it: a Google Sheet, an Airtable base, or Zoho Inventory items. A tag or RFID system can feed the same count, but this listing does not include one.
Ask about Linen Par

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.