Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Booking.com Content API specific settings are mentioned below 

  1. Amenity Features
    a) Amenity Bedroom Codes
    If some amenity is specifically defined for Booking.com to represent different beds, then we need to store the code of that amenity which is linked with Booking.com amenity codes using the reseller-addon dropdown. Booking.com has its own set of codes for different bedding type

    b) Amenity Group Codes
    There are add-ons in MXTS that are to be displayed at Booking.com, these add-ons belong to certain Amenity group code in MXTS, and codes of those group needs to be mentioned in this setting so the system will fetch the amenities and send them to Booking.com

    c) Hotel Amenity Codes
    To specify which all amenities are listed at the Resort level at, the amenity group code of those add-on/amenities needs to be entered in this setting.

    d) Roomsize Amenity CodeC
    ode of amenity if any defined for adding the room size at accommodation type to create room on Booking.com in square meter.

  2. Dynamic Field Features
    a) Description Code
    Code of dynamic field which is used on accommodation type or resort depend on what has been considered for creating property and that dynamic field will have the description which will be Booking.com specific.

    b) Hotel Checkin Code
    If setting "reseller.checkin.time" is not defined then it means every resort which will be linked and used to create a property on Booking.com should have the dynamic field which will have the checkin time defined for every resort. We can also create a dynamic field if we want to set check-in time differently only for a few resorts and other resorts having same check-in time will get the value from setting "reseller.checkin.time". So keep this setting to store that dynamic field code along with the setting "reseller.checkin.time".

    c) Hotel Checkout Code
    If setting "reseller.checkout.time" is not defined then it means every resort which we are going to link and used to create property on Booking.com should have the dynamic field created which will have a unique value for every resort. We can also create a dynamic field if we want to set check-in time differently only for a few resorts and other resorts having the same checkout time will get the value from setting "reseller.checkout.time". So we can keep this setting to store that dynamic field code along with the setting "reseller.checkout.time".

    d) Hotel Roomcount Code
    Store the code of the dynamic field to add the count that how many rooms are configured under the particular property. This setting is required only if a resort has been considered to create the property on Booking.com, if accommodation type has been considered then it will be done automatically by counting the object under that accommodation type.

    e) Hotel Star Rating Code
    At the property level, it is mandatory to send ratings starting from 1 to 5. So, a dynamic field needs to be created on accommodation type or resort level to store that rating. The code of this dynamic field needs to be entered in this setting so the rating can be sent to Booking.com .

    f) Property Type
    This is the code of dynamic field that will be used to store the value of Booking.com Property type code that represents what kind of rooms the properties are offering. Is it offering a hotel, condo, or apartment? Booking.com has a unique code for every type.

    g) Room Name Code
    When properties/Acco-type are to be linked through Booking.com content API, we cannot send any (MXTS) Acco-type name to them, we need to make sure that only ‘Booking.com English standard’ names are specified at the Acco-type level in a dynamic field, and then we need to mention the Code of that dynamic field in this setting. We need to also make sure that the ‘No’ Acco-types of the same Location should have the same ‘Booking.com English standard’ name. The same names can be differentiated by appending numeric values in front of them.
    For example One of the accommodation types can be called ‘Tent 1’ and then the other one can be named as ‘Tent 2’.

  3. Fees & Taxes Features
    a) Content Api Fees Codes
    To send fees supported by Booking.com link them with the products or extra using the reseller addon dropdown, by that linking we would be able to send the fees code which Booking.com support. Then add the codes of that product/extra in this setting to identify the resources to consider by the system.

    b) Content Api Tax Codes
    To send Tax supported by Booking.com either link them with the products or extra using the reseller addon dropdown (or can be picked directly from the Tax or Vat module), by that linking we would be able to send the Tax code which Booking.com support. We need to make sure that we add the code(s) of that product/extra in this setting to identify the resources to be considered.

    c) Enable Bookable Visible Check
    To identify accommodations on the basis of enable /visible bookable check of the particular representation in which our reseller DC is added and if its off then we disable the linking of that Acco-type

...