OwnerRez Global Alerts, Improved Rates Calendar, and New Arrival/Departure Rules!

I really hoped you all would also offer an Arrival / Departure Rule that would allow one or the other, but not both! Lots of people either arrive or depart on Christmas day at our ski place, but I don't want the cleaning staff to have to do a flip clean that day. Pretty please, can you add this functionality? 

I really hoped you all would also offer an Arrival / Departure Rule that would allow one or the other, but not both! Lots of people either arrive or depart on Christmas day at our ski place, but I don't want the cleaning staff to have to do a flip clean that day. Pretty please, can you add this functionality? 

Hi Dori123 - you can do either or both already. Just select Christmas Day on the Rates Calendar and set either or both to "not allowed" individually as they (Arrival and Departure) are separate settings. If one or both are already set from the season-level, you'll need to disable or delete that season, or override the season with the opposite setting.

Will the settings we do here for # of nights and arrival/departure override Pricelabs settings or vice versa?

@Shawn. above regarding Dori's comment on Christmas.  

I am not following how your solution works.  Assume I don't have anything set at the season level.  Christmas is just a random day in the middle of a rate season.  I can allow an arrival IF I don't have a departure on the same day.  I can allow a departure IF I don't have an arrival on the same day.  One depends on the other.  if I simply set either or both (arrival and/or departure settings) to "don't allow" I don't think it accomplishes the intention.  Can you please elaborate further?

It seems seasons would still be better to control Arrival/Departure rules otherwise you will have to add the rule every year.  With seasons, you can make it reoccurring for most holidays with the exception of maybe Thanksgiving

Joshua, it depends on the holiday. Many holidays change dates every year so recurring seasons wouldn't work.  Also, you have to have a 1 day season in order for that to work which is tedious.  Setting it on "the entire Christmas" holiday period (eg. 5 or 10 days) typically doesn't work because that means that no one can arrive/departure on any of the days of that season.  You typically want to pinpoint some exact dates to exclude arrival/departure, not entire seasons.  But yes, if your season is 1 or 2 days, you can do it that way as well.  That might mean you have multiple overlapping seasons.

Stacy:
The arrival/departure settings on the Settings> Rates page (shown above) will not be changed by PriceLabs settings. You can, also, go into that Settings>Rates page and override the seasonal departure settings for a particular night.

I'm with Danica  ^^^^  I can set one or the other but with this setting, one is not dependent on the other.  If I disallow both arrivals and departures, I have essentially blocked Christmas from both.

I currently manually block the opposite day depending on which reservation comes in first.    If a guest is departing Dec25 I block that night for no arrival, and vice versa, to prevent holiday turn-around.

I guess this setting gives me the option to set a policy that allows folks to either arrive or depart on holidays.  Or, I can keep doing it manually and hope I don't miss one.   

So the question is, is there a way to prioritize the setting based on an existing reservation?   

Blocks and season rate overrides on arrival/departure are overrideable.  If you combine them it makes a singular expression for the entire set of rules.  Seasons, blocks, etc all combine together so no there is no priority system.
 
Take for example
 

• Rate calendar do not allow arrival/departure on 2023-12-24 to 2023-12-26
• Create owner block off on 2023-12-25 and 2023-12-26 as well

 
The combined rules comes out like this
 
 

 
Then if you try to make a quote/booking you would get this message
 

 
You can still override over the combined block created.

Shawn H says:

Hi Dori123 - you can do either or both already. Just select Christmas Day on the Rates Calendar and set either or both to "not allowed" individually as they (Arrival and Departure) are separate settings. If one or both are already set from the season-level, you'll need to disable or delete that season, or override the season with the opposite setting.

Shawn:

I would like to set an Arrival / Departure Rule for a date that would automatically allow either but not both. This would be for set dates like Dec. 25, Jan 1, etc. If I understand correctly, your solution would have me set "no arrival" on Dec 25 after I get a reservation that departs Dec 25, or alternatively, I could set that date to "no departure" after I get a reservation that starts on Dec 25. This is not ideal, as it is not automated. I would still have to consult my list of "no flip" dates and remember to change the setting if I get a reservation that lands on one of those dates. And if I get any cancellations that affect those dates, I have to hope I'd remember to manually back out the setting

I would love to see the code allow Arrival only if No Departure that day, and Departure only if No Arrival that day. But not both. Let me know if I and the others misunderstand. 

Can you make a slight adjustment to the UI so that instead of Arrival and Departure be two separate choices it is Arrival/Departure and the pop-up has both sets of Radio buttons - that way when we are setting 2 restrictions on the same days we can set both at once... will save a lot of time.

Is there a way to upload all these restrictions via CSV so that we can have a file that we update each year and will allow to set similar rules for multiple properties at the same time - conversely, allowing us to download a CSV of these Rules will allow to double check all properties are set and create a template of modifying and uploading

In the meantime you could possible add multiple property select to the Advanced Select option along with the combining Arrival/Departure above it would save a lot of time.

Also, can you confirm that this overrides all other settings including seasons - you already confirmed above that this will not be overwritten by Pricelabs rules.

Thank you for consideration

PS not sure if I should write in here or in the recommendations area.

@Wendy -- can you clarify a bit on the setting: are you wanting to set Arrival/Departure to the same value (both allowed or both not allowed)? Or more looking for a "set changeover" that lets you pick "both, neither, check in only, check out only"?

We do have an export/import for the calendar rates -- you can see this on the spot rates tab. But it doesn't support the arrival/departure rules yet. We're working on an update to add those rules there as well.

I have no rules that prevent coming or going on specific holidays. I DO have same day turnover limitations where someone checks out on Thanksgiving (US) or Christmas I do not allow same day turnover. Is there an algorithm somewhere I can setup that scenario?

OwnerRez team: I can see that there's comments to now add scenarios where if X equals M, but Z doesn't happen, allow T, unless G is less than M, then allow A.  I can appreciate that it's just not always feasible to program every permutation that can be dreamt up.  So, I just wanted to express my appreciation for adding this feature!  It's working great and is wonderful. 

@Chris Hynes -- thanks for the quick reply. To clarify, I'm not trying to set both to the same. It is the latter of your comments. I am trying to reduce the number of steps/clicks. In most of our cases, we block both arrival and departure for the required days. Right now we have to select the dates>Set Rules>Arrival>Select Option>OK and then repeat everything again (except Select Dates) for Departure. It would be easier to have Set Rules>Arrival/Departure (or Set Change Over as you suggested) and then have 2 columns of Radio buttons for the 4 choices for each Arrival and Departure. That way the user could select just arrival, just departure, or both all in one step. Reduced manual workload :-)

Great to hear that the rules will be added to upload feature -- please announce when its done. Completely understand get the feature out ASAP and then iterate. When the import is implemented, it would be great if there is a filter option for the rules but we can easily do that in the exported data. I assume like the manual process it wont be overwritten by Pricelabs, etc

This is a great feature for New Arrival/Departure Rules, however can you clarify what Channels this works on and will be enforced?

Is there any caveat to doing this where it would accidentally black hole a particular channel from availablity.

This is a great feature for New Arrival/Departure Rules, however can you clarify what Channels this works on and will be enforced?

Is there any caveat to doing this where it would accidentally black hole a particular channel from availablity.

If I understand your question correctly, any Arrival/Departure Rules changed on the Rates Calendar will override Seasonal rules for API connected channels. This does not take into account any dynamic pricing tools connected as rules set on those may override what is set in OR.