FLYR’s integration with your PMS for restrictions is a one-way integration. This means that FLYR for Hospitality does not read any restrictions which have been configured in your PMS, it can only send restrictions from FLYR to your PMS. 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 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 1’000s of rate plan x inventory type x night combinations. We, therefore, foresee a range of features we want to support in FLYR 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 for Hospitality and PMS restrictions side-by-side?
We know about different use cases how restrictions are used today in the PMS:
Operational functions: e.g. closing a property due to renovations.
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.
Revenue Management use cases: making use of restrictions to optimise your business mix and maximise revenue.
As you can imagine, from FLYR’s 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 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. So, you can manage your restrictions from FLYR for Hospitality to PMS whilst also managing restrictions in the PMS that FLYR does not know about.
Guidelines for managing restrictions
It is always best to manage your restrictions solely in FLYR as any changes made in the PMS directly, will not reflect in the product and could lead to a mismatch between systems. To avoid confusions and mismatches between FLYR and the restrictions in your PMS, here are our best practices:
Always apply new restrictions via FLYR whenever possible;
If you have existing restrictions in the PMS, migrate them to FLYR and remove them from the PMS to manage all restrictions via FLYR;
Never change the restrictions created by FLYR directly in the PMS, update these directly through the FLYR platform;
Only set strategic restriction in the PMS that cannot be set via FLYR and should always be in place. Please inform our advisory team about these restrictions so we can review and support these in the future.
What restrictions does my PMS support?
For a full overview which restrictions are supported for which PMS, please see the list below:
PMS | Closed to Arrival | Closed to Stay | Closed to Departure | MinLOS available for | MaxLOS available for |
Mews | ✅ | ✅ | ✅ | Arrival, Stay, Departure | Arrival, Stay, Departure |
StayNTouch | ✅ | ✅ | ✅ | Arrival, Stay | Arrival |
Apaleo | ✅ | ✅ | ✅ | Arrival | Arrival |
Opera | ✅ | ✅ | ✅ | Arrival, Stay | Arrival, Stay |
Clock | ✅ | ✅ | ✅ | Arrival, Stay | Arrival, Stay |
RMS Cloud | ✅ | ✅ | ✅ | Arrival, Stay | ❌ |
If you have any questions or do not see your PMS listed, please contact our Advisory team via chat.