How to Handle Non Yieldable Rates

​@crawforc can´t you set it on the RMS for the rates you want to sent the restricition for? On our RMS we can do so. isn´t there a option to select specific rates or groups?

Yes, on a rate restriction level I can do this. 

I want to be able to set/automate a room type restriction strategy, but have some rate plans that can override that strategy/be nonyieldable. 

Hi crawforc,

There's actually a native way to do exactly what you're describing, exempt a rate from property level restrictions, it just isn't a flag on the rate itself. Which route fits depends on whether your corporate rate is a contracted allocation or a standing rate.

If the corporate rate is a contracted allocation (a block of rooms held for that company at a fixed rate for a period):
Use an Availability Block for it. Blocks have a setting to exclude the block rates from global restrictions, so the property level min stay or closed to stay you push from the RMS won't touch them. Once excluded, only restrictions you set directly on the block rate or its rate group apply. That's the cleanest match to a non-yieldable rate, and it's built for exactly this, contracted rates that shouldn't be caught by global rules.

If it's a standing corporate rate (bookable anytime, not a block):
There's no per-rate "ignore restrictions" checkbox, so you handle it by scope instead of override. Two steps:

1. Keep the corporate rate in its own rate group, separate from your yieldable BAR and derived rates. Mews even uses "corporate rates" as the textbook example of a standalone rate group, so you're going with the grain of the system here.

2. Scope from the RMS, not the room type. The reason the room type approach bites you: a restriction scoped to a space category applies to every rate on that category with no per-rate exception, that's by design. A restriction scoped to a rate or rate group does not. So exclude the corporate rate from the set your RMS manages, and the RMS pushes its min stay only to the yieldable rates. The corporate rate never receives it. In Atomize that's just choosing which rate plans the engine controls, which is how we keep our fixed rates out of it.

So: block plus "exclude from global restrictions" if it's contracted inventory, or its own rate group plus exclude from the RMS managed set if it's a standing rate. Both give you the room type level automation everywhere else with the corporate rate sitting still.

If you want it even simpler, a true per-rate non-yieldable flag on standard rates would be a clean addition, worth dropping on feedback.mews.com.

Erick // The Haus Group

Thank you, I appreciate the response!

The rate group approach wouldn’t work for me - it’s a standing corporate rate and I want to apply restrictions by room type specifically via the RMS based on available inventory for the current day and next day; the goal is keeping straight line availability.