Rate Rules

Summary and examples

The rate rules transaction is used to obtain detailed information about a specific room rate, including:

Room and rate descriptions
Detail rate information (totals, rate changes)
Individual taxes and fees
Policies (guarantee, deposit, cancellation, commission etc)
Restrictions and booking requirements

The request should contain:

The same parameters contained in the availability request (Single Property Availability or Enhanced Shopping) such as arrival/departure dates, number of guests, number of rooms etc
The specific rate plan code and room type code for the desired rate returned in the availability response. Note that the rate plan code in the availability response may be different from the one if the request (if sent), and so it is the code in the availability response that must be used in the rate rules request message.
Any rate qualifiers returned in the availability response for the desired rate, such as a corporate ID, should also be included.

It is recommended that the rate rules request be a mandatory step for the user before booking and that the response data be stored with the guest reservation. The rate rules information can reduce customer service issues.

The following is an example rate rules request:

<HotelML xmlns="
http://www.xpegs.com/v2001Q3/HotelML
">
<Head>
<Process DataPath="/HotelML/Form/PropertyInformation" Function="TI_PropertyInformationV1_1" Token="1307536926020"/>
<Route Destination="00" Source="01"/>
</Head>
<Form>
<PropertyInformation PropertyCode="UI;61829">
<PropertyRate NumberOfAdults="2" NumberOfBeds="1" NumberOfRooms="1">
<RatePlan Code="A66" InDate="2011-09-01" OutDate="2011-09-04">
<RoomType Code="C2D"/>
</RatePlan>
</PropertyRate>
</PropertyInformation>
</Form>
</HotelML>

The corresponding response is shown below:

<HotelML xmlns="
http://www.xpegs.com/v2001Q3/HotelML
">
<Head>
<Route Destination="01" Source="00">


<Operation Action="Create" App="TIDispatcher" AppVer="1.12.40.2.8.1.20.4.2.7.12.1.12.2.2.1.8.1.2.6" DataPath="/HotelML" StartTime="2011-06-08T12:42:47.626+00:00" Success="true"  TotalProcessTime="1359"/>
</Route>
</Head>
<Property xml:lang="en" Code="UI;61829" Token="1307536926020">
<Rate>
<RatePlan Code="A66" CommissionableStatus="NonCommissionable" Description="Fall Back Brazil Fall Back Brazil" InDate="2011-09-01" MarketingText1="ACCESS TO OVER 3000 UTELL HOTELS WORLDWIDE." OutDate="2011-09-04"
SpecialRequirementsText="Credit Card Guarantee is Required upon Booking" TaxInformation="14.75pct MISC Tax 3.50 OCC Tax Per
Room Per Stay">
<RoomType AmenityText="No Smoking Rooms/Facilities" BookableRate="215.20" Code="C2D" NativeCurrency="USD" RateFrequency="Nightly" RoomDescription="Cozy Double Double - A Comfortable Room" TotalRate="685.60" TotalRateInclusive="797.23" TaxQualifier="Unknown">
<CommissionPolicy Description="Non-Commissionable"/>
<GuaranteePolicy Description="Credit Cards: VI,CA,DC,AX,DS"/>
<CancelPolicy Description="CANCEL BY 1600 20110831 LOCAL PROPERTY TIME TO AVOID PENALTIES"/>
<Amenity xml:lang="en" Code="NSMK" Confirmable="true" Room="true"/>
<BookingRequirement MaximumStay="0" MinimumStay="3"/>
<RateChange Charge="215.20" CurrencyCode="USD" Date="2011-09-01" Frequency="Daily"/>
<RateChange Charge="255.20" CurrencyCode="USD" Date="2011-09-02" Frequency="Daily"/>
<RateChange Charge="215.20" CurrencyCode="USD" Date="2011-09-03" Frequency="Daily"/>
<TaxDetail Amount="14.75" Application="PerRoomPerStay" Basis="Independent" CurrencyCode="USD"
Description="14.75pct MISC Tax" EffectiveStartDate="2011-09-01" EffectiveEndDate="2011-09-04" Order="1" Type="Miscellaneous" Unit="Percent" Inclusive="no"/>
<TaxDetail Amount="3.50" Application="PerRoomPerNight" Basis="Independent" CurrencyCode="USD" Description="3.50 OCC Tax Per Room Per Stay" EffectiveStartDate="2011-09-01" EffectiveEndDate="2011-09-04" Order="2" Type="OccupancyTax" Unit="Monetary" Inclusive="no"/>
</RoomType>
</RatePlan>
</Rate>
</Property>
</HotelML>

PreviousRequest & Response message format NextRequest message format

Last updated 2 months ago