Managing business models

You can sell room inventory on Booking.com by choosing from the following two business models:

• commission model (default)
• net rate model (new)

In the future, we plan to roll out more business models to support different selling strategies.

Difference between the Commission rate and Net rate model

This section outlines the difference between the two models. Properties typically engage with Online Travel Agencies (OTAs) using one or both of these models to sell their room inventory.

Supported actions

This section outlines the actions you can perform once a property has signed up for a business model.

• Query business models available for a property
• Attach business model to a rate plan
• Query business model attached to a rate plan
• Query business model information when viewing roomrate
• See business model information for a reservation
  • OTA endpoint
  • B.XML endpoint

Query property business models

Use the business_models/properties endpoint to retrieve the eligible business models available for a property or a group of properties.

You can specify one of the following query parameters:

• property_id: The ID of the property. You can also specify multiple property IDs separated by commas. Do not specify this parameter if you specify the property's business model ID. If both are specified, the property_business_model_id takes precedence. The endpoint ignores the property_id parameter.
• property_business_model_id: The ID of the property's business model. Do not specify this parameter if you specify the property ID. If both are specified, the property_business_model_id takes precedence. The endpoint ignores the property_id parameter.
• business_model: The type of business model.

GET 
https://supply-xml.booking.com/business_models/properties?property_id={{property_id}}&property_business_model_id={{property_business_model_id}}&business_model={{business_model}}

Query parameters

The following table describes the elements you can specify in the query:

Response body elements

The following table describes the response elements:

Response body

The following is a sample response body:

{
    "data": [
        {
            "attributes": {
                "is_net": false
            },
            "property_business_model_id": 5780556,
            "business_model": "commission_rate",
            "property_id": 8011855
        }
    ],
    "meta": {
        "ruid": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
    },
    "errors": []
}

Attach business model to a rate plan

Use the v1.1 OTA_HotelRatePlanNotif endpoint to attach a business model when creating a rate plan.

Following are few important considerations to note:

• You can specify a business model only when creating a rate plan, and cannot change it later.
• Make sure to use the v1.1 OTA_HotelRatePlanNotif endpoint when attaching a business model.
• You cannot update a rate plan to specify a business model. Alternatively, you cannot change the business model of a rate plan after it is created.
• While creating a roomrate using a rate plan with the net rate model, you must specify a non-refundable cancellation policy.

This section only covers information related to specifying the business model using the OTA_HotelRatePlanNotif endpoint. For more information on the rate plan and all the available request and response elements, see Managing rate plans.

POST https://supply-xml.booking.com/hotels/ota/OTA_HotelRatePlanNotif

Header parameter

Request body parameters

The following table describes the elements you must add in the request body specific to the business model change. For all related fields see the OTA_HotelRatePlanNotif endpoint documentation.

Request body

The following request body example attaches a business model to a rate plan.

<OTA_HotelRatePlanNotifRQ>
    <RatePlans HotelCode="6314570">
        <RatePlan RatePlanNotifType="New" RatePlanID="123456">
            <Description Name="Summer Rate" />
            <BusinessModel PropertyBusinessModelId="12345" BusinessModel=“net_rate”/>
        </RatePlan>
    </RatePlans>
</OTA_HotelRatePlanNotifRQ>

Response body

The following is a sample response body:

<?xml version='1.0' encoding='UTF-8'?>
<OTA_HotelRatePlanNotifRS xmlns="http://www.opentravel.org/OTA/2003/05" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opentravel.org/OTA/2003/05 OTA_HotelRateAmountNotifRS.xsd" Target="Production" Version="3.000">
    <RatePlanCrossRefs>
        <RatePlanCrossRef RequestRatePlanCode="123456" ResponseRatePlanCode="58900005"/>
    </RatePlanCrossRefs>
    <Success/>
</OTA_HotelRatePlanNotifRS>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Query business model attached to a rate plan

Run the v1.2 POST /xml/rates endpoint, to query business model attached to the rate plan, in addition to retrieving rate plans for a property.

This section covers only the information related to retrieving the business model along with the rate plan details. For more information on retrieving rate plans, see Retrieving rate plans.

POST https://supply-xml.booking.com/hotels/xml/rates

Request body

The following request body example retrieves all rate plans.

<request>
   <hotel_id>6314570</hotel_id>
   <show_rates_status>1</show_rates_status>
</request>

Response body

The following is a sample response body:

<rates>
    <rate id="18045111" active="1" hotel_id="6314570" hotel_name="The Tech W" property_business_model_id='12345' business_model= “net_rate” />Non-refundable rate</rate>
    <rate id="19454895" active="1" hotel_id="6314570" hotel_name="The Tech W" property_business_model_id='12345' business_model= “net_rate”/>Fully flexible</rate>
    <rate id="20275653" active="0" hotel_id="6314570" hotel_name="The Tech W" property_business_model_id='12345' business_model= “net_rate”/>Standard rate</rate>
</rates>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Response body parameters

The following table describes the response elements:

Query business model information when viewing roomrate

You can use one of the following endpoints to retrieve the business model inherited by the roomrate:

• The v1.3 of the GET OTA_HotelProductNotif endpoint
• The v1.2 /hotels/xml/roomrates endpoint.

Note that you cannot attach a business model to a roomrate. The business model that is attached to the roomrate is inherited from the rate plan.

This section covers only the information related to retrieving the business model along with the roomrates details. For more information, see the respective endpoint documentation:

• Retrieving roomrates using OTA endpoint
• Retrieving roomrates using B.XMl endpoint

Using v1.3 of the OTA_HotelProductNotif endpoint

This section provides information about using the v1.3 of the GET OTA_HotelProductNotif endpoint to retrieve the business model inherited by the roomrate.

Response body parameters

The following is a sample response body:

<?xml version="1.0" encoding="UTF-8" ?>
<OTA_HotelProductNotifRS>
    <HotelProducts HotelCode="1">
        <HotelProduct ReadOnly="true" ChildRate="true">
            <RoomTypes>
                <RoomType RoomTypeCode="2" MaxOccupancy="5" />
            </RoomTypes>
            <RatePlans>
                <RatePlan RatePlanCode="11" PropertyBusinessModelId='12345' BusinessModel=“net_rate”/> 
            </RatePlans>
            <ValueAddInclusions>
                <MealPlan MealPlanCode="0" />
            </ValueAddInclusions>
            <PolicyInfo>
                <BookingRules>
                    <BookingRule MinAdvancedBookingOffset="P10D" />
                </BookingRules>
                <CancelPolicy>
                    <CancelPenalty PolicyId="325235" PolicyName="general" PolicyCode="222" />
                    </CancelPolicy>
                <GuaranteePaymentPolicy>
                    <GuaranteePayment EffectiveFrom="after_cancellation_fee_begins" PrePaymentRequired="true" />
                </GuaranteePaymentPolicy>
            </PolicyInfo>
            <ValueAddedServices Name="additional package">
                <ValueAddedService serviceId="21" />
            </ValueAddedServices>
        </HotelProduct>
    </HotelProducts>
</OTA_HotelProductNotifRS>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Response body parameters

The following table provides a snippet of the response elements to show the business model parameters. For a complete list of response parameters, see the GET OTA_HotelProductNotif documentation.

Using v1.4 of the /hotels/xml/roomrates endpoint

This section provides information about using the v1.4 of the POST /hotels/xml/roomrates endpoint to retrieve the business model inherited by the roomrate.

Response body parameters

The following is a sample response body:

<?xml version='1.0' encoding='UTF-8' ?>
<roomrates>
    <rooms>
        <room id="801185509" hotel_id="8011855" hotel_name="HillTop Hotel" room_name="Penthouse Apartment">
            <rates>
                <rate id="25278032" max_persons="7" policy="General" policy_id="341337682" rate_name="summer rate" fixed_occupancy="2" property_business_model_id='12345' business_model= “net_rate”/>
                    <meal_plan meal_plan_code="10" />
                    <policies>
                        <booking_rules>
                            <booking_rule min_advanced_booking_offset="P1D" />
                        </booking_rules>
                        <cancel_policy>
                            <cancel_penalty policy_code="62" />
                            <policy_overrides>
                                <policy_override start_date="2024-01-16" end_date="2024-02-23" policy_code="12" />
                            </policy_overrides>
                        </cancel_policy>
                   </policies>
                </rate>
            </rates>
        </room>
     </rooms>
</roomrates>
<!-- RUID: [XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] -->

Response body parameters

The following table provides a snippet of the response elements to show the business model parameters. For a complete list of response parameters, see the POST /xml/roomrates documentation.