Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Static hotel data from WebBeds is processed on hotelmapping.org as a ready connector. Hotel codes, room names, board codes and destination information are standardized and linked to a permanent HM ID; the same hotel merges into one card with records from other suppliers.
WebBeds is a B2B accommodation supplier (bedbank) that offers hotel rooms to travel agencies, tour operators and other travel companies. It is part of Web Travel Group. It operates under different sub-brands in different regions.
WebBeds inventory can overlap with other bedbanks. Without mapping, the same hotel appears in your list as separate cards for the WebBeds record and for other supplier records. Hotel mapping merges these records under a single HM ID. For the basic concepts, see the what is hotel mapping guide.
| Topic | Approach |
|---|---|
| Duplicate codes at the same supplier | Conflict queue and human review |
| Arabic and Latin spelling | Transliteration and multilingual embedding |
| Free-text room name | Split into type, view and bed labels |
| Different board spellings | Translation to the standard board code |
Static data is received through the ready connector and stored in its raw form. Names are normalized, and Arabic names are converted to Latin script through transliteration. Each record is compared with nearby candidates; a score of 0.97 or higher matches automatically, 0.80–0.97 goes to expert review, and below 0.80 creates a new HM ID.
You can see how room names are parsed on the room mapping page. To learn how bedbanks work, read the what is a bedbank guide.
At a supplier whose inventory is collected from different sub-brands and systems, the same hotel can appear with more than one code within the supplier itself. These records must be matched first among themselves, then with other suppliers.
For Middle Eastern hotels, the same property can arrive under an Arabic name, under different Latin spellings, or under the chain name alone. Without transliteration and multilingual similarity, these records are treated as separate hotels.
Room names often arrive as free text; view, bed and feature information is written in a single line in mixed order. Comparison is not possible until they are split into a standard room type.
{
"hm_id": "HM-1061590",
"name": "Kemer Pine Garden",
"destination_id": "TR-07-KEMER-GOYNUK",
"supplier_codes": [
{ "supplier": "webbeds", "code": "3381904", "confidence": 0.987 },
{ "supplier": "webbeds", "code": "71205", "confidence": 0.972 }
],
"status": "active"
} Code samples are illustrative; field names may change in the v1 release.
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Breaks room names into type, class, view, bed and capacity; groups the same room under one room ID.
Converts spellings like AI, UAI, Soft AI and HB+ into 10 standard board codes. AI and UAI offers stay apart.
Each code is scored as a separate supplier record. Codes that fall on the same property are gathered under a single HM ID; if two codes from the same supplier land on the same hotel, the record goes to the conflict check.
Arabic names are transliterated into Latin script and compared using multilingual similarity. The name alone does not decide; location, phone and website also feed into the score.
Mapping results can be queried through the REST API or downloaded as a daily full and delta dump in CSV, JSON or Parquet format.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.