Rate rules synced with the 4 main channels
Rate rule | Airbnb | Booking.com | Vrbo | TripAdvisor |
Additional Person | YES (1) | YES | YES | NO |
Arrival Only | YES | YES | YES | NO |
Charge at least | YES (change the min stay) (3) | YES | YES | YES (change the min stay) (3) |
Charge at least if available | YES (change the min stay) (3) | YES | YES | NO |
Charge at least full period | YES (change the min stay) (3) | YES | YES | YES (change the min stay) (3) |
Departure only | YES | YES | YES | NO |
Full period only | NO | YES | YES | NO |
Prevent gap | NO | YES | YES | NO |
Prevent if booked ahead of (2) | YES | YES | YES | YES |
Prevent if booked less than (2) | YES | YES | YES | YES |
Strict minimum price per night | YES | YES | YES | NO |
Week-end night | YES | YES | YES | YES |
Stay at least | YES (4) | YES | YES | YES (change the min stay) (3) |
Stay shorter than | YES (change the min stay) (3) | YES (change the min stay) (3) | YES | YES (change the min stay) (3) |
Early booking (2) | NO | YES | YES | NO |
Late booking (2) | NO | YES | YES | NO |
Occupancy less than | NO | YES | YES | NO |
(1) must be handled in the app settings
(2) As the sync of the rates is only once a day, these rules, that are relative to the current day are partially supported, according to the time of the sync.
(3) The minimum stay takes in this case the value of the maximum number of days set up in the rule. Ex. You have a min stay of 1 day in the season and set up the charge at least 2 days, then the min stay sent to the portal will be 2 days as they don't handle this kind of complex rules.
(4) 2 scenarios depending of the pricing type:
LOS (V2) pricing - yes the rate rule available on core is considered and included in pricing received from core, and then propagate to Airbnb. That’s why weekly/monthly discount is not available to set on change settings form, as this would lead to potentially doubling the discount.
For Nightly Rates (V1) :
- stay at least X days with discount (negative increase) - this rule is not included and doesn’t affect anything
Example:
Base Rate: 100/nightscenario 1.stay at least 7 days > discount 10% (price increase: -10%)
This would be ignored, we will send:nightly rate: 100, minimum stay: 1
If someone books for 7 days they won’t get discount and that’s all, no risk of underpricing
- stay at least X days with price increase (positive) - it’s included in the nightly rate we send, but also affects minimum stay to match it threshold.
Example:
Base Rate: 100/nightscenario 1.stay at least 7 days > increase 10% (price increase: 10%)
This would not be fully ignored, we will send:nightly rate: 110, minimum stay: 7
To fully map the rule it would mean - <1,6> nights 100; 7+ 110
Comments
0 comments
Please sign in to leave a comment.