We'd like the Allotment release dates to continue releasing
unpicked rooms even after the cutoff has occurred.
When we put in a release schedule for an allotment in
Stayntouch, the system will release any unpicked rooms in block when the cutoff
is triggered, but that’s a one-time event. The system does not actually
remember that there was a cutoff date in place for a given date once the cutoff
has already passed. So, whenever an allotment reservation is canceled after the
cutoff date, unless we go in and manually release that room, it will just stay
in block, reducing our inventory and potentially preventing us from selling out
the night in question.
In previous systems I’ve worked with, the release schedule
was retroactive, so even after the cutoff date has passed, any rooms added to
the block for a given date within the cutoff window, as well as rooms remaining
in the block from a cancelled reservation, were released during that night’s
rollover. The system recognized that the cutoff had already passed, so those
unpicked rooms were released.
To some extent, Stayntouch already does that. When you first
set up a release schedule for an allotment, the system recognizes that dates in
the near future are already past the cutoff, and the release schedule reflects
that. In the screenshot below, I added a 30-day cutoff for an allotment
(today is Oct 16), and you can see that the system understands that Nov 11 is
only 25 days out, Nov 12 is 26 days out, etc., so all those dates will release
at rollover tonight.
The system should remember the release schedule and release any unpicked rooms sitting in allotment within that 30-day cutoff window. Instead, the system cuts off at 30 days and then forgets
that any of the earlier dates ever had a 30-day cutoff in the first place.
It would be great if the system could be updated to continuously release unpicked rooms for dates that are already past the scheduled release.
We'd like the Allotment release dates to continue releasing unpicked rooms even after the cutoff has occurred.
When we put in a release schedule for an allotment in Stayntouch, the system will release any unpicked rooms in block when the cutoff is triggered, but that’s a one-time event. The system does not actually remember that there was a cutoff date in place for a given date once the cutoff has already passed. So, whenever an allotment reservation is canceled after the cutoff date, unless we go in and manually release that room, it will just stay in block, reducing our inventory and potentially preventing us from selling out the night in question.
In previous systems I’ve worked with, the release schedule was retroactive, so even after the cutoff date has passed, any rooms added to the block for a given date within the cutoff window, as well as rooms remaining in the block from a cancelled reservation, were released during that night’s rollover. The system recognized that the cutoff had already passed, so those unpicked rooms were released.
To some extent, Stayntouch already does that. When you first set up a release schedule for an allotment, the system recognizes that dates in the near future are already past the cutoff, and the release schedule reflects that. In the screenshot below, I added a 30-day cutoff for an allotment (today is Oct 16), and you can see that the system understands that Nov 11 is only 25 days out, Nov 12 is 26 days out, etc., so all those dates will release at rollover tonight.
The system should remember the release schedule and release any unpicked rooms sitting in allotment within that 30-day cutoff window. Instead, the system cuts off at 30 days and then forgets that any of the earlier dates ever had a 30-day cutoff in the first place.
It would be great if the system could be updated to continuously release unpicked rooms for dates that are already past the scheduled release.