Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Room mapping breaks the different names suppliers send for the same room into room type, class, view, bed, feature and capacity tags, and groups the same room under a single room ID linked to the hotel's HM ID (e.g. HM-1048213-R03). This way, the prices different suppliers offer for the same room can be compared side by side.
{
"room_id": "HM-1048213-R03",
"hm_id": "HM-1048213",
"name": "Standard Double Room, Sea View, Balcony",
"type": "room",
"class": "standard",
"view": "sea",
"bed": "double",
"features": ["balcony"],
"max_occupancy": 3,
"supplier_rooms": {
"A": "DBLSV-B",
"B": "DZMB",
"C": "STD-DNZ"
}
} "DBL SV BLC", "DZ Meerblick Balkon" and "Deniz Manzaralı Balkonlu Çift Kişilik Oda" link to the same room ID; prices are compared in a single row.
Room abbreviations and spellings in TR, EN, DE and RU are kept in a rule dictionary; where the dictionary falls short, the tagging model steps in.
Each room name is broken into six tags. Filtering and sorting by view, bed type or capacity needs no separate parsing.
Land-view and sea-view rooms have different tags, so they stay under separate room IDs and are never shown in the same row.
Several room names can be matched instantly in a single request; bulk processing and file delivery are also available for the entire inventory.
Names from three suppliers for the same room
supplier,hotel_code,room_code,room_name
A,HTL-88213,DBLSV-B,Dbl Sea View Balcony
B,40917,DZMB,DZ Meerblick Balkon
C,TR-ANT-551,STD-DNZ,Standart Oda Deniz Manzaralı Balkonlu (2+1) A single room record broken into tags
{
"room_id": "HM-1048213-R03",
"hm_id": "HM-1048213",
"name": "Standard Double Room, Sea View, Balcony",
"type": "room",
"class": "standard",
"view": "sea",
"bed": "double",
"features": ["balcony"],
"max_occupancy": 3,
"supplier_rooms": {
"A": "DBLSV-B",
"B": "DZMB",
"C": "STD-DNZ"
}
} Sample data; the hotel, room names and codes do not belong to a real property.
The room name is split into words and abbreviations. Letter case, punctuation, capacity in parentheses ("2+1") and language differences are normalized.
Each part is matched against the TR, EN, DE and RU abbreviation dictionary: "SV", "Meerblick" and "Deniz Manzaralı" fall under the same view tag.
Parts that are not in the dictionary or have more than one meaning are assigned by a tagging model to type, class, view, bed, feature or capacity.
Rooms linked to the same HM ID are compared by their tags. Names with matching tags are linked to the same room ID; conflicting records go to human review.
Results come back instantly in the API response, or as a file for bulk jobs. Each supplier room code is stored together with the room ID it is linked to.
Each supplier writes room names according to the rules of its own system. One uses abbreviations (“DBL SV BLC”), another uses the catalog language of German tour operators (“DZ Meerblick”), and another sends the hotel’s Turkish name as is. With 10 room types and 5 suppliers in a hotel, the number of names to match rises to 50. Manual matching is slow, and differences in view or capacity are easily overlooked.
Room mapping breaks every name into the same six tags and does the comparison on these tags rather than on names. For a detailed explanation of the topic, see the what is room mapping guide, and for the general framework, the hotel mapping guide.
| Tag | What it describes | Example values |
|---|---|---|
| Type | Room category | Room, suite, junior suite, studio, family room, villa, bungalow, apartment |
| Class | Comfort level | Economy, standard, superior, deluxe |
| View | What is seen from the window | Sea, partial sea, land, garden, pool |
| Bed | Bed layout | Single, double, twin, king, queen |
| Feature | Additional equipment | Balcony, terrace, jacuzzi, swim-up room, connecting room |
| Capacity | Maximum number of guests | SGL = 1, DBL = 2, TRP = 3, QUAD = 4; 2+1, 2+2 |
The rule dictionary links the spellings of the same concept in four languages to a single tag. The rows below are examples; the full list is in the room type abbreviations guide.
| Concept | EN | DE | TR | RU |
|---|---|---|---|---|
| Single occupancy (capacity 1) | SGL | EZ (Einzelzimmer) | Tek kişilik | одноместный |
| Double occupancy (capacity 2) | DBL | DZ (Doppelzimmer) | Çift kişilik | двухместный |
| Two separate beds (bed: twin) | TWN | 2 Einzelbetten | İki ayrı yataklı | две кровати |
| Family room | FAM | FZ (Familienzimmer) | Aile odası | семейный номер |
| Sea view | SV | Meerblick | Deniz manzaralı | вид на море |
| Balcony | BLC | Balkon | Balkonlu | балкон |
| Suite | STE | Suite | Süit | люкс |
At most suppliers, DBL indicates a room for two guests; it does not always specify the bed type. That is why “DBL” is read first as capacity (at least 2 guests). If the name has no TWN or “twin”, the bed tag becomes double; if there is a clearer hint such as “king”, that is used. The type tag, on the other hand, is the room category: “DBL Sea View” is a room, “Junior Suite” is a junior suite.
Room mapping works only among the rooms of the same hotel; that is why the hotel’s HM ID is first determined with hotel mapping. For price comparison to be accurate, board type mapping is needed alongside the room. For terminology, see the room mapping and supplier code glossary pages.
Request
curl -X POST https://api.hotelmapping.org/v1/rooms/map \
-H "X-API-Key: $HM_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"hm_id": "HM-1048213",
"rooms": [
{ "supplier": "B", "code": "DZMB", "name": "DZ Meerblick Balkon" },
{ "supplier": "B", "code": "FZLS", "name": "FZ Landseite" }
]
}' Response
{
"hm_id": "HM-1048213",
"groups": [
{
"room_id": "HM-1048213-R03",
"type": "room",
"class": "standard",
"view": "sea",
"bed": "double",
"features": ["balcony"],
"max_occupancy": 3,
"matched": [
{ "supplier": "B", "code": "DZMB", "name": "DZ Meerblick Balkon", "confidence": 0.98, "decision": "auto_match" }
]
},
{
"room_id": "HM-1048213-R07",
"type": "family_room",
"class": "standard",
"view": "land",
"bed": null,
"features": [],
"max_occupancy": 4,
"matched": [
{ "supplier": "B", "code": "FZLS", "name": "FZ Landseite", "confidence": 0.91, "decision": "review" }
]
}
]
} Code samples are illustrative; field names may change in the v1 release.
Yes. Room names are compared only with rooms of the same hotel. That is why the hotel's HM ID is determined first, and then the supplier room names for that hotel are grouped.
The new name is re-tagged. If the tags are unchanged, it stays linked to the same room ID. If they changed, the record goes to the review queue and, if needed, is linked to a different room ID.
The threshold logic from hotel mapping is planned to apply to rooms as well: 0.97 and above is linked automatically, 0.80 to 0.97 goes to a specialist, and below 0.80 opens a new room record. Specialist decisions feed back into the dictionary and the model.
At launch, the rule dictionary covers Turkish, English, German and Russian abbreviations. Coverage for Arabic and other languages has not been finalized yet.
No. Room mapping standardizes static room data only. Price and availability come from the supplier to your system; we only tell you which room they belong to.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.