Map rate plans

Once a hotel is successfully connected to Apaleo, you’ll need to map the rate plans from Apaleo to the corresponding ones in your system. Apaleo does not store external rate plan IDs, so all mapping must be handled on your side. To streamline this process, we recommend fetching all rate plans from Apaleo and making them selectable when creating or mapping rate plans in your system. This eliminates the need to manually copy and paste IDs between platforms—much smoother that way!

You should only load rate plans from Apaleo that are mapped with ChannelManager as channel code.

A rate plan in Apaleo is always associated with exactly one unit group (= room category). Every rate plan has a unique identifier, which is a combination of the property code, rate code, and unit group code.

When processing ARI data or creating reservations, you must use this unique Apaleo rate plan ID. To do so, you’ll need to map the combination of your rate code and room code to the corresponding Apaleo rate plan ID on your side.

Here’s an example for a simple hotel with two room categories and two rate codes: rate codes:

While the structure of Apaleo’s rate plan IDs might look meaningful—especially if hotels use consistent naming for rate codes—you should not rely on parsing or interpreting them Yes, these IDs are built from the property ID and the rate plan code, but keep in mind: the rate plan code is defined by humans and may vary widely across different properties. It might appear structured, but there’s no guarantee of consistency or meaning. Treat rate plan IDs as opaque identifiers—use them as-is, without trying to extract information from them.

Once the mapping is done, you can subscribe to availability, rates and inventory (ARI) updates for those rate plans.