When configuring rates in the CRS and individual Booking Channels (Expedia, Hotels.com, etc.) it is critical that any rates that deviate from the configured rates in the PMS be accounted for. Failure to do this will result in incorrect rates being imported to into the PMS.

Rates are imported from the OTA field "RatePlanCode" contained in the HotelReservation XML message received from the CRS.

For example:

• The PMS sends a BAR rate to the CRS and you configure several derived rates off of this.
  • The derived rates might include additional fees, or even discounts. 
    
    
• When imported, the PMS doesn't always get the details of the derived rates, only a final cost.
  • This prevents the PMS from knowing what fees, taxes, discounts, etc., to post.
    
    

To resolve this, you must configure a Guest Package for each one of these new rates BEFORE you attempt to use them online. The Guest Package will contain a complete breakdown of the charges, fees, taxes and discount, ensuring that it posts correctly.

​

For example​:

• The PMS BAR rate is a $200 room charge per night, plus tax. 
  
  
• Expedia has a rate derived from BAR that's a 10% discount on the room charge but also includes a $35 per person dining package.
  • Expedia sends this to the PMS as a BAR rate, but if the PMS imports this as the actual BAR rate, the guest will be charged incorrectly.
    
    
• The remedy is to create a Guest Package and remap it. 
  
  • The Guest Package might look like this
    This will use the calculated BAR rate (configured as Rate Code 2 in the PMS) for VILLA CHARGE
    This will use the calculated ROOM TAX rate
    This will apply a RESTAURANT charge of $35 per person
    This will apply a discount of 10% only to the VILLA CHARGE, and the ROOM TAX will correctly calculate based on the discounted amount.
    "Folio print option: Y" will cause each line of this package to post in the guest folio.
    
    The "Package total" is only showing the Restaurant charge because the room and tax are season dependent and calculated based on the reservation date.
    
    
•  If the RatePlanCode the booking channel or CRS sends is the configured Guest Package Code (BM10 in this example), then no remapping is necessary. 
  Remapping is only needed if the RatePlanCode doesn't match the Guest Package code.  
  
  
• To remap, the interface must have remapping triggers set. The entire HotelReservation XML message will be scanned and keywords searched for. If there is a match, the RatePlanCode is remapped to the appropriate Guest Package in the PMS.
  • Create a RatePlanCode remap rule that searches the reservation message for triggers. 
    This will remap the RatePlanCode to BM10 based on these triggers, anywhere in the HotelReservation XML message. Typically if the Booking Channel includes these descriptions, they are passed on to the PMS as comments. 
    If the HotelReservation XML message contains all of the triggers, BAR, DINING, and SPRING PROMOTION, then the RatePlanCode will be remapped to BM10 in the PMS, which will post the Guest Package created earlier.
    
    You could create a Guest Package that doesn't include SPRING PROMOTION, and leave it out of the list of triggers.  
    
    The remapping logic checks for all of the triggers and they must exist for the RatePlanCode to remap. 
    
    If all triggers are found, it always remaps to that RatePlanCode.