- Rates/rules aren't updating properly, but the Booking.com API appears to be connected and functioning correctly.
- I got a Booking.com booking, but it has different rates from what seems like should be configured per OwnerRez.
- Booking.com has different property IDs for the same property.
Rates/rules aren't updating properly, but the Booking.com API appears to be connected and functioning correctly.
- Check Change Sync Mode to see if there are other available rates. Sometimes they delete one plan and need to switch to another and you'll see it in the list. In this case, you can see that there is only one plan, as there should be, so that's not the issue:
- If that isn't the problem, get feedback from the customer to see what the other rate plan is. Did they create it on accident, or is it intentionally supposed to be a derived rate plan from the OwnerRez plan? Get a screenshot of the Rate plans list so we can see what's going on.
- If it's extra, have them delete it.
- If it's supposed to be derived, but isn't, then they either need to contact booking.com support or try deleting and recreating again and making sure it's derived this time. Probably the latter first, since booking.com support can take some time. See additional notes below on derived rates.
I got a Booking.com booking, but it has different rates from what seems like should be configured per OwnerRez.
Wrong Rates
With booking.com rate problems, the first place to look is the rate on the booking (e.g. https://app.ownerrez.com/bookings/5923302/channel) vs the rate on the channel (e.g. https://app.ownerrez.com/settings/channels/215824407):
Notice that they are different. This means that the guest did not book with the rate we sync to booking.com but with some other rate on their (possibly a discount rate or such) which the host has created on booking.com.
The response to this should be that the host needs to remove any other rates that we're not syncing over.
Derived Rates
When the client creates a derived rate in Booking.com, they can override the rules that are set on the main rate plan by OwnerRez via the API. This is not visible in OwnerRez and will lead to bookings that appear to violate rules. Also, derived plans seem to be a bit glitchy -- sometimes even if the client doesn't override the rules intentionally, booking.com won't correctly apply the rules from the main rate plan.
You can see that this has happened by looking at the CSE to see if the rate was rewritten. This is found in the Channel tab of the Booking, Booking Added action, Data button.
Since the derived rate plan wasn't created by OR, we can't control this. There are two ways to fix it:
1) The client can contact booking.com and get them to fix the derived rate plan (in this case the Weekly rate) so that the rules (such as min days before arrival) on the derived plan will inherit from what OwnerRez is pushing to the main rate plan.
OR
2) They can delete the derived rate plan and just use the one main plan. This is likely easier and less confusing for the future.
Booking.com has different property IDs for the same property.
First, disconnect the property from BDC.
Then, connect the property to the correct listing number.
After you've disconnected it, you should see it listed here on the Connect Properties page. This is where you'll add the listing number, and select the Rate Plan.