What is room mapping? Why are room names so messy?
Room mapping groups the different names suppliers send for the same room in the same hotel under a single standard room ID. The name is split into type, class, view, bed, feature and capacity parts, and records with the same parts are grouped. Prices are then compared on the right room, and the room sold matches the room given.
- Author
- hotelmapping.org Editorial Team
- Last updated:
- 12 min read
Room mapping in short
When an agency buys the same hotel from more than one supplier, each room of the hotel also arrives under a different name from each supplier. One supplier writes “Dbl Sea View Balcony”, another “DOUBLE ROOM SEAVIEW”, a third “Standart Oda Deniz Manzaralı”. Room mapping decides whether these names describe the same physical room and, if so, groups them under a single standard room ID.
Room mapping is the next step after hotel mapping. First it is settled that different supplier records belong to the same hotel, and the hotel gets a permanent HM ID. Then the room names under this hotel are compared. A hotel ID is required to define a room, because the name “Deluxe Room” can describe the largest room at one hotel and a slightly renovated version of the standard room at another.
For a short definition, see the room mapping glossary entry; for how the product works, see the room mapping product page.
Why are room names so messy?
Hotel names have at least one real name; room names often do not. A room name is formed as it passes through the hands of the hotel, the channel manager, the supplier and sometimes the agency’s own software. At each step something is added, shortened or translated. The main causes of the mess are:
- Free text: At most suppliers the room name comes not from structured fields but from a text box. Even within the same supplier, the spelling varies from hotel to hotel.
- Abbreviations: Abbreviation is common in systems with character limits and in tour operator catalogs: DBL, TWN, SV, LV, FAM, JS. There is more than one abbreviation for the same concept (TRP, TPL, TRPL) and some abbreviations have two meanings depending on context. For a detailed list, see the room type abbreviations guide.
- Multilingual sources: A resort in Turkey can distribute the same room under Turkish, English, German and Russian names. “Deniz manzaralı”, “Sea View”, “Meerblick” and “вид на море” describe the same view. Cyrillic names arrive converted to the Latin alphabet in some systems, which adds transliteration differences.
- Mixing of room and rate: Board type (“AI”, “Half Board”), refund condition (“Non Refundable”), campaign (“Early Booking”, “Promo”) or sales channel information is added to the room name. These parts describe the rate, not the room, but because they sit inside the name, two identical rooms look different.
- Hotel-specific marketing names: Names such as “Lagoon Suite” and “Pine Garden Room” make sense only at that hotel. The name gives no direct information about the room’s type and view.
- Capacity notation: Notations such as “2+1”, “2AD+2CH”, “DBL+EXB” describe capacity but each supplier uses a different format. Because “2+1” is also used in Turkey for the number of bedrooms in apartments and villas, it needs extra care.
- Truncation and capitals: Some systems cut the name at a certain number of characters or convert it all to capitals. A name like “SUP DBL SSV BLC” can be the remnant of a truncated long name.
The same room, five different names
The table below shows how the balcony, sea view standard double room of the fictional Sunset Bay Resort & Spa hotel can arrive from five different sources. The hotel name and codes are examples.
| Source | Supplier room code | Incoming room name | What to watch for |
|---|---|---|---|
| Supplier A | DBLSV-B | Dbl Sea View Balcony | None |
| Supplier B | DZMB | DZ Meerblick Balkon | German abbreviation and name |
| Supplier C | STD-DNZ | Standart Oda Deniz Manzaralı Balkonlu (2+1) | Class and capacity information |
| Supplier D | R-2041 | DOUBLE ROOM SEAVIEW AI NRF | Board type and refund condition; no balcony information |
| Supplier E | 7781 | Двухместный номер с видом на море и балконом | Russian name |
For a person, seeing that these rows describe the same room is often easy; only the missing balcony information in row D leaves a question mark. For software, all five are different text. Simple text comparison counts these rows as separate rooms; an overly loose rule may merge a sea view room with a side sea view room.
What parts does a room name consist of?
The core idea of room mapping is to read the room name not as a single text but as a structure made of meaningful parts. Each part is assigned to a label. The label groups used at hotelmapping.org are:
| Label | What it describes | Example spellings | Standard value example |
|---|---|---|---|
| Type | Room category | Room, Suite, Junior Suite, Studio, Family Room, Villa, Bungalow | room |
| Class | Tier within the same type | Standard, STD, Superior, SUP, Deluxe, DLX | standard |
| View | What is seen from the window | Sea View, SV, Land View, LV, Garden View | sea |
| Bed | Bed arrangement | Double Bed, Twin, TWN, 2 Single Beds, King Bed, Queen Bed | double |
| Feature | Additional physical feature or location | Balcony, Jacuzzi, Private Pool, Ground Floor, Annex | balcony |
| Capacity | Maximum number of guests who can stay | SGL, DBL, TRP, QUAD, 2+1, 2AD+1CH, Max 4 | 3 |
| Non-room information | Parts that belong to the rate, separated from the room | AI, HB, NRF, Promo, Early Booking | (passed to the rate side) |
Abbreviations such as SGL, DBL, TRP and QUAD describe capacity, not type. At most suppliers DBL indicates a room for two; it does not always state the bed type. So the name “DBL Sea View” is read as type room and capacity at least 2; unless TWN or “twin” is in the name, the bed is assumed to be double. Categories such as suite, villa or family room go to the type label.
The last row is important. In room mapping, the first job is to filter out information that does not belong to the room. Board type abbreviations go to board type mapping; for the meaning of these codes, see the board types and codes guide. Refund and campaign information stays as a property of the rate. The remaining parts form the room’s identity.
How does room mapping work?
The details of room mapping vary from provider to provider. The flow at hotelmapping.org consists of these steps:
- Hotel context: Each room name is first tied to the HM ID of the hotel it belongs to. The supplier’s hotel code and supplier room code are stored in raw form.
- Normalization: The name is lowercased, punctuation and extra spaces are cleaned, and joined spellings are split (“SEAVIEW” → “sea view”). Names in Cyrillic and Arabic script are converted to the Latin alphabet; the original name is stored too.
- Parsing and labeling: The name is split into words. First the TR, EN, DE and RU abbreviation and synonym dictionary runs; for words with no counterpart in the dictionary, a labeling model steps in. Each word is assigned to one of the type, class, view, bed, feature, capacity or non-room information labels.
- Grouping: Within the same hotel, names whose labels agree are put in the same group. The group gets a standard room ID: e.g.
HM-1048213-R03. - Confidence score and decision: Each match gets a match score. High-scoring matches are approved automatically; ambiguous ones fall into a queue checked by a specialist. The thresholds in hotel mapping are planned to apply to rooms as well: 0.97 and above automatic, 0.80–0.97 human review, below 0.80 a new room record. Room-specific thresholds will be finalized after they are measured with a test set.
- Feedback: Every decision by the specialist is added to the dictionary and the model. This way, when the same spelling arrives again, it is recognized automatically.
Example: from raw room names to a standard room
In the example below, the room names of four suppliers from the table (A, C, D and E) are sent to the POST /v1/rooms/map endpoint. Field names are an example based on the API v1 design; the hotel and codes are fictional.
{
"hm_id": "HM-1048213",
"rooms": [
{ "supplier": "A", "code": "DBLSV-B", "name": "Dbl Sea View Balcony" },
{ "supplier": "C", "code": "STD-DNZ", "name": "Standart Oda Deniz Manzaralı Balkonlu (2+1)" },
{ "supplier": "D", "code": "R-2041", "name": "DOUBLE ROOM SEAVIEW AI NRF" },
{ "supplier": "E", "code": "7781", "name": "Двухместный номер с видом на море и балконом" }
]
}
The response splits the names into room groups. Each group carries the standard room ID and the room’s labels; in the matched list, each name has the information separated from the room, a confidence score and a decision:
{
"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": "A", "code": "DBLSV-B", "removed": [], "confidence": 0.98, "decision": "auto_match" },
{ "supplier": "C", "code": "STD-DNZ", "removed": [], "confidence": 0.97, "decision": "auto_match" },
{
"supplier": "D",
"code": "R-2041",
"removed": [{ "text": "AI", "kind": "board" }, { "text": "NRF", "kind": "rate" }],
"confidence": 0.91,
"decision": "review"
},
{ "supplier": "E", "code": "7781", "removed": [], "confidence": 0.97, "decision": "auto_match" }
]
}
]
}
Supplier D’s row falls into the review queue ("decision": "review") because the name has no balcony information. If the hotel has a room type with the same view but no balcony, this name may belong to that room as well. In the other three rows, type, view and balcony information agree, so the records link directly to the same room ID. The scores in the example are to show the method; real values will be determined after measurement with the test set.
What happens without room mapping?
In a system without room mapping, problems usually surface not on the sales screen but at the moment the customer arrives at the hotel:
- Wrong price comparison: When the system looks for the “cheapest double room”, it compares one supplier’s land view room against another supplier’s sea view room. The offer that looks cheapest is actually a lower room.
- The same room repeating in the list: The customer sees the same room under four different names at four different prices and cannot tell which to choose. This can both lower conversion and shake trust.
- Room sold differs from room given: The customer buys a “Sea View Room”; the supplier passes the booking on with its own “Standard Room” code and the hotel gives a land view room. The result is a complaint, a refund request and extra work for the operations team.
- Manual mapping load: Some agencies try to solve this problem by hand with a team. But as new suppliers, new seasons and new room names arrive, the list keeps going stale.
The cost of these problems varies from agency to agency; no reliable industry-wide rate is known. For the general cost of duplicate records, see the cost of duplicate hotels article.
Hard cases
Some room names cannot be resolved with a rule dictionary. Knowing them determines which questions to ask, both when building your own system and when choosing a provider.
Run of house (ROH)
In a “run of house” sale, the room type is not known at booking time; the hotel gives an available room on arrival day. ROH is not a room type but a sales format. So it is not matched to a specific room; it is kept as a separate “room assigned by the hotel” record.
Family rooms
“Family Room” describes a separate two-bedroom unit at one hotel and a large room with an extra bed at another. The same hotel can also have both a “Family Room” and a “Family Suite”. In this case, extra information such as capacity, number of bedrooms and square meters is decisive. Without the information, the record is not matched automatically.
View tiers
“Sea View”, “Side Sea View”, “Partial Sea View” and “Frontal Sea View” can be different rooms. If a supplier writes only “Sea View” and skips the tier, this name can be matched safely only if the hotel has a single sea view room type.
Building and location
In large resorts, the same room type is sold at different prices in the main building and in an additional building (annex, club building, bungalow section). If the name has no building information, matching is done by looking at the hotel’s room list and the counterparts at other suppliers.
Marketing names
Names such as “Lagoon Suite” or “Pine Garden Room” are not in the dictionary. Which standard room these names correspond to is determined from the hotel’s own room list or by a specialist’s review. Once a decision is made, the name is stored as a hotel-specific synonym.
How do room, hotel and board mapping work together?
To compare a price row correctly, the answers to three questions must be the same: same hotel, same room, same board type? The three mappings are therefore linked:
| Layer | Question | Output |
|---|---|---|
| Hotel mapping | Do these records belong to the same property? | HM ID (e.g. HM-1048213) |
| Room mapping | Do these names describe the same physical room? | Room ID (e.g. HM-1048213-R03) |
| Board type mapping | Do these spellings describe the same board type? | Standard code (e.g. AI, UAI) |
If hotel mapping is wrong, room mapping also works with the rooms of the wrong hotel. If board type is not separated from the room name, the same room looks like two different rooms. That is why hotelmapping.org keeps these three layers in the same data model. For the board side, you can try the board code converter tool.
Checklist for building your own room mapping
Whether you do room mapping with your own team or buy it from a provider, the answers to these questions should be clear:
- Does room mapping work on records whose hotel mapping is complete?
- Are board type, refund condition and campaign information separated from the room name?
- Is there a maintained dictionary for TR, EN, DE and RU abbreviations and synonyms?
- Does every match have a confidence score, and do ambiguous records go to human review?
- Is the supplier’s original room name and code stored, or overwritten?
- Are room IDs permanent? What happens to the old ID when a hotel changes its room types?
- When you report a wrong match, how long does the correction take to take effect?
Some of these questions are covered in detail at the hotel level in 12 questions to ask when choosing a hotel mapping API.
Summary
Room names are messy because they are written as free text, abbreviated, translated into different languages and mixed with rate information. Room mapping splits these names into meaningful parts, filters out information that does not belong to the room and groups names describing the same room under a single room ID. The result is correct price comparison and the room sold being the same as the room given. For the full list of abbreviations, see the room type abbreviations guide; for product details, see the room mapping page.
Frequently asked questions
What is the difference between room mapping and hotel mapping?
Hotel mapping decides whether different supplier records belong to the same property and gives the property an HM ID. Room mapping comes next: it compares the room names under the same HM ID and groups the names that describe the same room under a single room ID (e.g. HM-1048213-R03).
What happens if room mapping is not done?
The same room appears in the list more than once, while different rooms can be compared on the same price row. A typical result is a room sold as sea view being given at the hotel as a land view room, which turns into a customer complaint.
What happens to the board type and refund condition in the room name?
These are properties of the rate, not of the room. During room mapping they are separated from the room name: board type goes to board type mapping, and refund condition and promotion information are passed to the rate side. The room ID describes only the physical room.
Can every room name be matched automatically?
No. Sales such as run of house, where the hotel assigns the room, incomplete names and hotel-specific marketing names can stay ambiguous. These records are not matched automatically; they fall into a queue checked by a specialist, and the decision is fed back to the dictionary and the model.
hotelmapping.org Editorial Team
DIJI.TECH hotel data team
The DIJI.TECH team working on hotel mapping, supplier integration and travel software.
Related products
Room mapping solutions
Breaks room names into type, class, view, bed and capacity; groups the same room under one room ID.
Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
- Only with us
Board mapping solutions
Converts spellings like AI, UAI, Soft AI and HB+ into 10 standard board codes. AI and UAI offers stay apart.
Related articles
- Room type abbreviations glossary: SGL, DBL, TWN, TRP, SV, LV, FAM Room type abbreviations glossary: SGL, DBL, TWN, TRP, SV, LV, FAM and more. Type, view, bed and feature codes with TR, EN, DE and RU equivalents.
- What is hotel mapping? How it works: a complete guide What is hotel mapping? How supplier records merge into one ID, the 9-step process, score thresholds, room and board mapping, and how to measure quality.
- Board types and codes: the RO, BB, HB, FB, AI, UAI guide What are board types? Meaning of the RO, BB, HB, FB, AI and UAI codes, common spellings in four languages, and how to map them in supplier data.