Vendor Integration Mapping

Use the Vendor Integration Mapping page to enable G3 RMS to send decisions to your Selling SystemClosed Any distribution system, like a PMS, CRS or a Channel Manager, that is used to sell your transient guest room inventory. Ideally, G3 RMS sends all controls to your selling systems, but this may vary based on their capabilities. For some integrations, the selling systems may not include the reservation system that provides with data. when some room types or rate codes don't match between the systems. In that case, use this page to tell G3 RMS which code in the selling system matches the one in G3 RMS.

Note: Most clients can skip this setup. Because, when Room Types don't match, you can usually complete this mapping in the selling system which resolves the issue. You, or someone at your property, should know if that's the case. If you are in doubt, check with the support contacts of your selling system.

Setup Steps

Map Room Types

  1. Click , then Decisions, and then Vendor Integration Mapping.
  2. Select the Vendor for which you want to complete Room Type Mapping.
  3. Click Add Room Type Mapping.
  4. Select a room type code from the Room Type menu.
  5. Enter the room type for the selected vendor in the Vendor Room Type field.
  6. Repeat the steps above until all Room Types are mapped for that vendor.
  7. Click Save.
  8. If you have multiple selling systems, continue selecting vendors and mapping room types until you have accounted for all your selling systems.

Map Rate Codes

  1. Click , then Decisions, and then Vendor Integration Mapping.
  2. Select the Vendor for which you want to complete either Rate Code Mapping.
  3. Click Add Rate Code Mapping.
  4. Select a rate code from the Rate Code menu.
  5. Enter the rate code for the selected vendor in the Vendor Rate Code field.
  6. Repeat these steps until all Rate Codes are mapped.
  7. Click Save.
  8. If you have multiple selling systems, continue selecting vendors and mapping rate codes until you have accounted for all your selling systems.

Scenarios for Using Mapping

Room Type Mapping

Use Room Type Mapping if G3 RMS is sending room type level decisions for your property, and any of these scenarios apply:

  • The number of room types in G3 RMS does not match the number in the selling system. For example, you have seven room types in G3 RMS but less than or more than seven in the selling system.
  • The room type codes used by G3 RMS do not match those in the selling system. For example, your PMS has a “DBL” room type. G3 RMS uses the same name, because it’s getting data from your PMS. But in your selling system it’s called “1D”.

Rate Code Mapping

Use Rate Code Mapping if G3 RMS is sending BAR by Day rate code level restrictions for your property, or if G3 RMS is sending BAR by LOS decisions, and any of these scenarios apply:

  • The rate codes from the PMS do not match the codes for the same rate plan in one or more of your selling systems. For example, the rate code "BCOMBAR" in the PMS is coded "BDCBAR" in your CRS.
  • All the rate codes do not exist in the selling system. For example, the PMS has ten rate codes, but only five of those codes exist in the CRS.

Vendor Integration Mapping for Your PMS/CRS

One of your reservations systems, PMS or CRS, provides the data to G3 RMS, including the room type and rate codes. Therefore, in most cases, when sending decisions back to that system, you don't need to complete Vendor Integration Mapping.

However, if your property uses the Daily Continuous or BAR by Day pricing method and it's Opera-based (OPMS, ORS or MyFidelio), there are a few scenarios when you need to complete the mapping: 

  • Your property has set up a second rate code (other than the Opera daily BAR rate code) and both rate codes need to receive Daily BAR Decisions. This should be a rare scenario, since the rates can be derived (i.e. the Daily BAR Rate code -0).

  • The Daily BAR rate codes between any of the following systems don’t match: ORS, OPMS, MyFidelio.

  • A second rate code needs to receive decisions from a different room type. For example, for a rate code that requires a mandatory upgrade and a price for a higher value room type must be sold at the price of the next lowest priced room type, like Amex Centurion.

Mapping the Codes in the Selling System

Many selling systems allow you to map to the codes from the reservation system that provided G3 RMS with the room type and rate codes. In these cases, room type or rate code mapping is not required. If you are in doubt, check with the support contacts for your selling system.

In this example, the PMS is the reservation system and the CRS is a selling system that allows the below mapping:

PMS Room Type Code Room Type Description CRS Room Type Code “PMS Code” in Selling System for Mapping
STDBL Standard Double SD STDBL
EXDBL Executive Double ED EXDBL
EXTWN Executive Twin ET EXTWN

Mapping Examples

In this example, the number of rate codes is the same in the PMS (the reservation system) and CRS. Mapping is required because the codes are different, and the selling system uses the CRS, not the PMS rate codes for integration. In Vendor Integration Mapping, select the PMS rate code, then enter the equivalent CRS Rate Code.

PMS Rate Code Rate Code Description CRS Rate Code
BCOMBAR Booking.com BAR Rate BDCBAR
EXPBAR Expedia BAR Rate EXPBAR
FLEXRO BAR for Direct Channels BAR

In the example above, if G3 RMS was required to send MinLOS restrictions to BDCBAR, the BCOMBAR rate from the PMS would be mapped to the BDCBAR rate code used in the CRS.

In the next example, some rate codes match exactly, but not all exist in the CRS. The PMS and CRS receive rate code MinLOS restrictions from G3 RMS. There are five rate codes to receive restrictions in the PMS, but only three of these exist in the CRS.

In this case, set up the mapping for only those that exist in the CRS, and restrictions will be generated against these.

In Vendor Integration Mapping, select the PMS rate code, then enter the equivalent CRS Rate Code. You can apply this mapping either with or without room type mapping.

PMS Rate Code CRS Rate Code
BCOMBAR BCOMBAR
EXPBAR EXPBAR
FLEXRO FLEXRO
CORP (Not Mapped)
CORP10 (Not Mapped)

You might need to map a one-to-one relationship between room types or rate codes between G3 RMS and selling systems. However, you can also set up a single G3 RMS room type or rate code to map to several rate codes or room types in your selling systems (for example, if multiple room types should receive the same decisions). For example, Room Type A in G3 RMS can be mapped to Room Type B and Room Type C in a selling system:

  • Room Type A = Room Type B
  • Room Type A = Room Type C

You cannot send decisions from multiple room types or rate codes in G3 RMS to a single selling system room type or rate code. For example, Room Type A and Room Type B in G3 RMS cannot both be mapped to Room Type C in selling systems:

  • Room Type A ≠ Room Type C
  • Room Type B ≠ Room Type C