Reference · built on requestOperator by FibricHospitality & guests

Block Pickup

Tracks group room-block pickup against cutoff dates, and proposes releasing unsold rooms and chasing missing rooming lists.

Request accessPricing ↗

About

A group block holds rooms the property cannot sell until the cutoff date, and the rooming list often arrives late or not at all. Block Pickup reads each block, its allocation by room type and night, the reservations picked up against it, the cutoff date, and the wash schedule, from Oracle OPERA Cloud, apaleo, or Mews availability blocks.

As cutoff approaches it proposes what to release back to general inventory, night by night, and a chase to the group contact for the rooming list. Where the block is filling faster than planned, it proposes holding the cutoff. The sales manager approves each release and each chase.

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

  • Blocks, allocations, and pickup, through getBlocks, getBlockStatistics, and getBlockDailyStatistics in the OPERA Cloud blk module
  • Wash schedules and cutoff, through getBlockWashSchedules and getBlockWashInfo, and the block's status history through getBlockStatusChanges
  • apaleo blocks with status Tentative, Definite, Optional, or Canceled, and the picked-up-from-block, released, and washed webhook types
  • Mews availability blocks with State, ReleasedUtc, and RollingReleaseOffset, and the reservations filtered by AvailabilityBlockIds
  • Cloudbeds roomblock and allotmentBlock webhooks: created, updated, details_changed, and removed
  • The group booking in your sales and catering system; Amadeus Delphi runs on the Salesforce platform, so its objects read through the Salesforce connector
  • Availability offered to channels through SiteMinder, so a release shows up where it can be sold

Proposed actions

  • Target capability: propose releasing unsold rooms from a block, through putBlockAllocation in OPERA Cloud, block-actions release in apaleo, or Update availability blocks in Mews
  • Target capability: propose a chase message to the group contact for the rooming list, drafted for the sales manager to send
  • Target capability: propose moving the cutoff, through putBlockCutoff in OPERA Cloud, when pickup is ahead of the wash schedule
  • Target capability: propose creating rooming-list reservations once the list arrives, through postRoomingList in OPERA Cloud
  • Target capability: propose a weekly pickup summary by block to the sales channel in Microsoft Teams or Slack

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

What you can build

  • Release what the group will not use

    getBlockDailyStatistics in OPERA Cloud shows one night of a block far behind its wash schedule with cutoff days away. Block Pickup proposes a putBlockAllocation release for that night and room type, for the sales manager to approve.

    With Oracle OPERA Cloud, Microsoft Teams

  • Chase the rooming list before it is too late

    An apaleo block is Definite, cutoff is near, and no picked-up-from-block events have arrived. The operator proposes a chase to the group contact, drafted from the block details, with the cutoff date quoted.

    With apaleo, Slack

  • Get the released rooms onto the channels

    After a release is approved in Mews, Block Pickup checks the availability SiteMinder publishes for that room type and those dates, and reports whether the freed rooms are now open to sell.

    With Mews, SiteMinder

  • Hold the cutoff for a block that is filling

    Pickup on a block is ahead of its wash schedule and the Salesforce record for the group shows a larger attendee count. The operator proposes moving the cutoff later through putBlockCutoff, with the figures beside it.

    With Oracle OPERA Cloud, Salesforce Sales Cloud

Requirements

  • A property management connector with block read and write: Oracle OPERA Cloud with the blk module, apaleo, or Mews availability blocks
  • Cutoff dates or wash schedules recorded on each block; the operator does not assume one
  • A contact for each group, on the block or in your sales and catering system, for rooming-list chases
  • A Slack or Microsoft Teams channel for the sales office, where releases and chases are approved
Authentication
Block Pickup has no login. Blocks, pickup, cutoffs, and group bookings are read through the property management, CRM, and channel connectors you connect; releases and cutoff changes go back through the property management connector after approval.

Limits

  • It reads pickup as the PMS records it. Reservations booked outside the block at the group rate are not counted unless you link them.
  • A release is proposed by night and room type. It never cancels a reservation already picked up.
  • Chase messages are drafts for the sales manager. The operator does not email a group contact directly.
  • Sales and catering systems other than those on the Salesforce platform are not read; their pickup is entered by you.

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 Block Pickup ↗

Questions and answers

What does the sales manager approve?
Each release by block, night, and room type; each chase message; each cutoff change. The card shows allocation, pickup so far, the wash schedule, days to cutoff, and the exact change. Approve, adjust the count, or dismiss.
What is kept for each release?
A receipt: the block, the pickup figures read, the release or cutoff change, who approved, the PMS write, and how to restore the allocation. Chase drafts and their outcome are logged against the block.
Does it ever release rooms or contact a group on its own?
No. It tracks pickup and proposes. A release or cutoff change is written only after approval, once, through the connector. It never cancels a picked-up reservation and never sends a message to a group contact itself.
Ask about Block Pickup

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