Skip to main content

Resolving the "ROOM_OCCUPANCY_DISCREPANCY" Alert on Booking.com

Sandra Álvarez avatar
Written by Sandra Álvarez
Updated this week

When you connect your accommodations to Booking.com through Channel PRO, it's essential that the basic information for each room matches between both systems. One of the most common alerts is the ROOM_OCCUPANCY_DISCREPANCY, which arises when the maximum occupancy set in Avantio (VRMS) does not match the one established in the Booking.com Extranet.

This discrepancy might seem like a minor detail, but it directly affects the availability your guests see and can cause confusion in bookings. Resolving it is quick and will prevent potential issues.


Why does this alert appear?

The alert is triggered because:

  • In the VRMS (Avantio) you have defined a certain maximum occupancy.

  • In the Extranet of Booking.com that same room is configured differently.

When both values do not match, the system detects the discrepancy and triggers the alert.


Step-by-step to resolve the alert

  1. Access the VRMS (Avantio) and open the file of the affected accommodation.

  2. Review the configured maximum occupancy field.

  3. Enter the Extranet of Booking.com and go to "Property" → "Room Information".

  4. Check the maximum occupancy indicated in Booking.com.

  5. Adjust the values in one of the two systems until they match.

  6. Save the changes and wait for the synchronization to complete.


Helpful tip

Before activating a new accommodation on Booking.com, check that the maximum occupancy configured in Avantio matches the one in the Extranet. This will prevent alerts and potential synchronization blocks.


Best practices

  • Keep an internal reference list with the maximum occupancy of each accommodation.

  • Every time you modify a room on Booking.com, also update the file in Avantio.

  • Perform periodic checks, especially if you manage several accommodations with different configurations.


Common mistakes

  • Forgetting to update Avantio after modifying the occupancy on Booking.com.

  • Setting a different occupancy by mistake in the VRMS file.

  • Only reviewing at the company level and not the individual accommodation file.


Quick checklist

☑ Review the maximum occupancy in Avantio.
☑ Review the maximum occupancy in Booking.com.
☑ Confirm that both values match.
☑ Save changes and verify synchronization.


Frequently asked questions

What happens if I don't correct the alert?
The availability seen by guests may not reflect reality, which can lead to booking issues and negative reviews.

Can I set different occupancies in each system?
No. The maximum occupancy must match for synchronization to work without errors.

How long does it take for the alert to disappear after correcting the data?
Usually a few minutes, although sometimes it can take up to 24 hours.

Does this alert affect already confirmed bookings?
No. It only impacts the future availability information sent to Booking.com.

Did this answer your question?