We would like some form of temporary OTA isolation / reception‑only mode, where, for example:

• Changes made by reception (room moves, removing blocks, emergency allocations), do NOT sync to OTAs until the mode is turned off.

• A short, manual pause (e.g. 5–10 minutes) on OTA updates while operational changes are being made

The Problem:

Currently, Mews only allows one type of room block. The 'Out of Order' block.

When running close to full occupancy, there could be some daily operational issues, unexpected maintenance problems, guest conflicts, or urgent relocations.

To manage these situations, we always keep at least one room blocked with the said 'Out of Order' block, as a security/emergency room.

In case we have to move a guest to that emergency room, we must:

1. Temporarily remove the block
2. Move the guest’s reservation into the room
3. Reapply the block afterwards

The issue is that the moment the block is removed, the room becomes available to connected OTAs (e.g. Booking.com).

In high demand times, this has caused us real overbookings, even though the emergency block was removed for less than a minute, during that short window, the room was sold online. (or potentially the block was not re‑synchronized as fast as it was removed).

This creates a serious operational risk during emergencies, where reception needs to act quickly without worrying that a necessary internal change will cause an overbooking.