Properties
      Back to home
      1. Knowledge Base
      2. NextPax Core - (CMS)
      3. Properties

      Property - Amenities

      In this section we will discuss the amenities section of the property pages, the different set of amenity groups we support and other functionalities around amenities.

      Amenities are one of the most known differentiators to be used for documenting the accommodations. The amenities are used often by OTA's for further classification, filtering and/or grading the quality of the property. NextPax offers a robust amenity system, syncing all available amenities from the OTA's in Core.

      A consideration here is that the OTA's build or allow amenities based on B2C A/B testing research and are very careful about what amenities they for that reason offer. In the case that we are not offering a amenity - it means that the amenities are not supported by the main OTA's. 

      Moreover there are two type of amenities, those that are imported from a PMS, proprietary system, and those that are manually added. For Supply API and Nxtbeds users the amenities are always provided by the respective systems used. We have created the 'manually added' option, so that accommodation partners can always enrich their content in NextPax, even if their own PMS doesn't support certain amenities, or setting amenities at all.

      Amenity Groups

      In order to structure the amenities section better, we designed the use of amenity groups. In this way we classified and organised all amenities within certain groups. One can navigate between the groups by clicking the 2nd level sub-menus from comfort to business, or by scrolling through the amenity list to discover the different amenity groups.

      Amenity Mapping

      An important note is there that for all PMS systems and direct integrations that are not running via our Supply API, but via API's of the respective partners, NextPax needs to normalise and map all the incoming amenity codes towards the NextPax amenity codes. This mapping is done at the system level of a particular integration/PMS, and applied to all accommodation partners using the particular system. 

      Supply API users, even if external PMS systems are involved, they are already using the NextPax amenity codes in our API. This means that the mapping of amenities is happening with the Supply API user and not with NextPax.

      Nxtbeds users are using the amenity codes of NextPax, no mapping at all is required.