When you connect your accommodations to Booking.com through Channel PRO, it's essential that the basic information for each room matches in both systems. One of the most common alerts is ROOM_OCCUPANCY_DISCREPANCY, which appears when the maximum occupancy set in Avantio (VRMS) doesn't match the one set in the Booking.com Extranet.
This mismatch might seem like a minor detail, but it directly affects the availability your guests see and can cause confusion with bookings. Fixing it is quick and will help you avoid potential issues.
Why does this alert appear?
The alert is triggered because:
In the VRMS (Avantio) you've set a certain maximum occupancy.
In the Extranet of Booking.com that same room has a different value set.
When these values don't match, the system detects the discrepancy and triggers the alert.
Below are two screenshots of the fields you need to check:
AVANTIO
From the accommodation profile in the VRMS:
BOOKING.COM
From the "Property" section → "Room Information":
Step-by-step guide to resolve the alert
Log in to the VRMS (Avantio) and open the profile of the affected accommodation.
Check the maximum occupancy field you've set.
Go to the Extranet of Booking.com and navigate to "Property" → "Room Information".
Check the maximum occupancy listed on Booking.com.
Adjust the values in one of the two systems so they match.
Save your changes and wait for the synchronization to complete.
Frequently asked questions
What happens if I don't fix the alert?
The availability shown to 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 correctly.
How long does it take for the alert to disappear after correcting the value?
Usually just a few minutes, but 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.