The <Pricings /> element is a container for any number of <Pricing /> elements. Each <Pricing /> contains a set of price information.

Pricing attributes

  • Currency: is the only mandatory attribute. All price information within the element is calculated based on this setting. In a simple case you may have various <Pricing /> elements each of which contains price information for a different currency.
  • SourceMarket: If prices differ depending on the source market, i.e. the country where the travel product is on sale you can use this attribute. It take a two-letter ISO country code such as IT, ES, US, FR, etc. Currently the attribute can only have one country code.
  • RatePlan: Many hotels use rate plan codes where each code relates the rates to a series of conditions, a meal plan and frequently a source market e.g. non-refundable, breakfast included or package-rate, accommodation only.
  • Label: Apart from optionally giving the Pricing a name, the label information is also used in cases where various pricing elements with an identical combination of Currency, SourceMarket and RatePlan is needed. This may happen for instance if one pricing is only available under certain conditions, for instance for a certain occupancy and another price applies within the same rate plan with a different occupancy (see example below).
    <Pricing Label="1 or 2 adults" SourceMarket="DE" Currency="EUR" RatePlan="BAR20">
        <Room Start="2019-01-01">124 124 120.50 121.50 121 121 ...</Room>
            <Guest Type="Adult Adolescent" MinCount="1" MaxCount="2" />
    <Pricing Label="3 or 4 adults" SourceMarket="DE" Currency="EUR" RatePlan="BAR20">
        <Room Start="2019-01-01">88.50 88.50 88.50 89 89 88.50 ...</Room>
            <Guest Type="Adult Adolescent" MinCount="3" MaxCount="4" />


<Pricing /> has a <Conditions /> child element. If the defined conditions are not fulfilled this <Pricing /> element will be discarded. In the above example this is used to define two different Pricings for different numbers of guests. Another example would be to discard a rate plan which is not available for last minute or for stays of less than 4 days.

Room and Guest prices

A <Pricing /> element may have <Room /> and <Guest /> child elements which are the basic price components. All existing <Room/> and <Guest> elements will be summed up if they their attribute values apply.


The <Room /> element contains a space separated list of floating point numbers each of which specifies the price at a specific day. Room has a Start and and End attribute.

  • Start: The Start attribute is mandatory and is the day for which the first price in the list applies.
  • End: If End is not specified the end date is automatically set to the last price in the list. If the end date is specified and lies behind the last price in the list, the whole list will be repeated until the end date is reached. If the same room price is valid for a longer period of time it is therefore possible to just include this one price and set Start and End accordingly.
  • LOS: This attribute is only used in case of dynamic rates if each price in the <Room /> and <Guest /> elements is the total amount for a specific length of stay at the corresponding arrival day. if LOS is not set, each price in the the <Room /> and <Guest /> elements represent the price (or price component) which is to be charged for each day. See examples below, it explains, how a price for a stay with arrival (check-in)="2019-01-03" and departure (check-out)="2019-01-06" is calculated.
    <!-- The <Room /> element in the following <Pricing /> element has no LOS attribute. The first number 
    in the list represents the room price for the 1st of January (because this is the date set in the start
    attribute), the second one for the 2nd of January, etc. Therefore you take 
    the 3rd,4th and 5th price and add them together: 452 EUR.
    <Pricing RatePlan="BAR20">
        <Room Start="2019-01-01">160 151 151 150 151 151 150 152 152</Room>
    When the LOS attribute is used you will see many identical <Pricing /> elements with different values for LOS: LOS="1", LOS="2", 
    LOS="3", etc. You need to find the element where the length of stay (LOS) is three and just pick that price: 452 EUR.
    <Pricing RatePlan="BAR20" >
        <Room Start="2019-01-01" LOS="3">453 450 452 451 456 456 455 456 450</Room>


The <Guest/> element works similar to the <Room />, only that the prices are applied per Guest. It does not have the LOS attribute because LOS-based models specify per-room prices. It has a Type and an Index attribute.

  • Type: is used to specify the guest types for which this price component applies. It can take various guest types (see example below).
  • Index: If different prices apply for each guest depending on the number of guests the index specifies for which guests the prices apply. If there are gaps between the index values, the guests for whome there is no index number will get the price with the lower index applied (see example below).
<!-- In this example the first and the second adult or adolescent (these guest types are defined on hotel level) 
will pay the prices specified in the <Guest /> element with the Index 1. The third guest will have the 
price applied as specified in the <Guest /> element with Index 3.
<Pricing RatePlan="BAR20">
    <Guest Type="Adult Adolescent" Index="1" Start="2019-01-01">160 151 151 150 151 151 150 152 152</Room>
    <Guest Type="Adult Adolescent" Index="3" Start="2019-01-01">45 46 46 45 43 43 43 43 34</Room>





Optins are optional extras that are not included in the price but which can be booked additionally. Examples are entry tickets for a gala, free use of the spa and sauna or even car rentals.

Last modified 4 months ago Last modified on Sep 20, 2017 4:04:57 PM