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

Why does Pace 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 Pace 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 Pace 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 Pace'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 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 Pace. So, you can manage your restrictions from Pace to PMS whilst also managing restrictions in the PMS that Pace 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 Pace, there will be no impact. However, if you change a restriction in the PMS which was created via Pace, Pace won't be notified about this change in the PMS. Pace will therefore likely re-push this restriction into your PMS the next time we resync - unless you edit or delete the restriction via Pace.

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 Pace if you also created them in Pace.

Did this answer your question?