External systems that have group room blocks typically allow groups to go through a series of statuses that determine whether the blocked rooms should be taken from inventory. This is important as once a hotel promises a number of rooms to a group, it has to make good on that promise.

With the way availability is updated in Mews currently, space categories can be overblocked and cause our users to fail to have all promised rooms available for their guests.

Example:

1. Hotel has space category "King Villa" with 10 rooms available for every day in July

2. External system creates an availability block "A" for July 1st to July 5th, blocking 10 "King Villa" rooms for each day

3. Group "A" in the external system has its status marked as "Definite", which in this example means the contract has been signed and those rooms are promised to the group.

4. External system creates an availability block "B" for July 4th to July 8th, blocking 5 "King Villa" rooms for each day. Despite July 4th and 5th having all their rooms blocked by a definite group, this availability will be successfully blocked in Mews.

5. Reservations for the "B" block get created in Mews before reservations for "A" get created

6. When a user tries to create reservations for the July 1st to July 5th for the "A" block, not all of the inventory will be available.

In Mews there needs to be some type of overbooking prevention or statuses on availability blocks to determine whether their availability adjustments should take priority over other block's availability adjustments.