All Collections
Restrictions Management
How Flyr Restrictions work with your PMS
How Flyr Restrictions work with your PMS

Understand how restriction management in Flyr Hospitality interacts with restrictions in your PMS

Lukas Hughes avatar
Written by Lukas Hughes
Updated over a week ago

Flyr Hospitality's integration with your PMS for restrictions is a one-way integration. This means that Flyr Hospitality does not read any restrictions which have been configured in your PMS but can only send restrictions from Flyr Hospitality. This type of integration is very common for RMSs and PMSs when it comes to restrictions. Here are a few pieces of information that are good for you to know when using it.

Why does Flyr Hospitality not support a two-way integration?

Albeit, two-way integrations are great to keep systems in sync, they also rely on the fact that both systems offer the same set of features. Restrictions have nuances and can be applied to 1000s of rate plan x inventory type x night combinations. We, therefore, foresee a range of features we want to support in Flyr Hospitality to help with easing these management challenges. As we don't want to rely on PMS partners building them out exactly the way we need them to, it is more scalable for us to only offer a one-way integration so we can focus on delivering the best features and user experience for our customers.

How should I use Flyr Hospitality and PMS restrictions side-by-side?

We know about different use cases how restrictions are used today in the PMS:

  1. Operational functions: e.g. closing a property due to renovations.

  2. Rate plan configurations: specifying a set of restrictions when creating a rate plan, e.g. fixing a MIN LOS 7 to a rate plan that gives a discount when staying 7 or more nights.

  3. Revenue Management use cases: making use of restrictions to optimise your business mix and maximise revenue

As you can imagine, from Flyr Hospitality perspective we always want to focus on the latter point as we believe that's where we can create the most value for your business. We, therefore, will always prioritise features that support this use case the most. However, we understand that managing all restrictions (across all use cases) in one solution is always preferable.

Despite being a one-way integration we, therefore, want to ensure you that we will never remove any restrictions in your system unless they have been created via Flyr Hospitality. So, you can manage your restrictions from Flyr Hospitality to PMS whilst also managing restrictions in the PMS that Flyr Hospitality does not know about.

What happens if you change something in the PMS?

If you do change something in the PMS which has been never created via Flyr Hospitality, there will be no impact. However, if you change a restriction in the PMS which was created via Flyr Hospitality, Flyr Hospitality won't be notified about this change in the PMS. Flyr will therefore likely re-push this restriction into your PMS the next time we resync - unless you edit or delete the restriction via Flyr Hospitality.

So, in short: Feel free to edit & delete any restrictions in the PMS that have been created in the PMS. But only update restrictions in Flyr Hospitality if you also created them in Flyr Hospitality.

Flyr Hospitality <> Restrictions Relationship

As we have already mentioned, it is always best to manage your restrictions solely in Flyr Hospitality as any changes made in the PMS directly, will not reflect in our feature and could lead to a mismatch between systems 😕

Further to this, there is specific way that the relationship between restrictions work for Mews properties and if changes are made in the PMS itself, we cannot guarantee that our restrictions will be put into place in Mews as there might be a “more strict” restriction already in Mews that overrules the restriction.


  • Flyr Hospitality sets a Stay Min LOS 3 in Mews for date x

  • User sets a Closed or a Min LOS 5 in Mews

  • Both are more strict than Flyr Hospitality's Min LOS 3

  • Although Flyr Hospitality restrictions will exist in Mews, it won’t be in effect as the existing restriction in Mews is more strict

To circumvent any debates about “what is more/less strict” we strongly advise to manage all restrictions (types that exist in Flyr Hospitality) from Flyr Hospitality 🙌 this should be a far smoother and simpler process all in all, ultimately being more beneficial in the overall Restriction Management of the property or group 💪

Did this answer your question?