Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Static hotel data from Hotelbeds is processed on hotelmapping.org as a ready connector: hotel codes, room names, board codes and destination codes are standardized and linked to a permanent HM ID. As a result, Hotelbeds inventory merges into the same hotel card as your other suppliers.
Hotelbeds is a B2B accommodation supplier (bedbank) that sells hotel rooms wholesale to agencies, tour operators and other travel companies. It operates under the HBX Group. It provides static hotel content and availability/rate data through separate APIs.
For an agency that works with several suppliers alongside Hotelbeds, the same hotel appears multiple times in the list when no mapping is done. A Hotelbeds hotel code is meaningful only inside the Hotelbeds system; it cannot be compared directly with another supplier’s code. Hotel mapping gathers these codes under a single permanent identity, the HM ID. If you are new to the topic, start with the what is hotel mapping guide.
| Hotelbeds data | Standard output |
|---|---|
| Hotel code | HM ID (e.g. HM-1052207) |
| Room code and room name | HM room ID, room type, view, bed |
| Board code | Standard code: RO, BB, HB, FB, AI, UAI… |
| Destination code | Hierarchy in the form TR-07-MURATPASA-LARA |
| Coordinates | Latitude and longitude selected from supplier records (validation planned) |
You can see how board codes are translated on the board mapping page. For the bedbank concept, see the glossary definition.
In a global bedbank catalog, hotels are added, closed or updated every day. A one-time mapping is not enough; changes must be reprocessed on a regular basis.
Room and board information arrives with the supplier's own code list. The same abbreviation can mean something different at another supplier, so codes cannot be compared until they are translated into a standard dictionary.
Destination codes are kept at a different level by each supplier. A hotel one supplier calls Belek may be listed under Serik or Antalya by another; the hierarchy has to close that gap.
In large catalogs the same property can appear with several codes for different sections or different contracts. Whether these codes link to the same HM ID or to separate records is decided by rules and human review.
{
"supplier": "hotelbeds",
"code": "918274",
"supplier_name": "LARA PALM HOTEL",
"hm_id": "HM-1052207",
"name": "Lara Palm Hotel",
"destination_id": "TR-07-MURATPASA-LARA",
"confidence": 0.993,
"matched_at": "2026-11-02T08:14:00Z"
} 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.
Links supplier destination codes to a country → province → district → resort area hierarchy and to IATA codes.
Converts spellings like AI, UAI, Soft AI and HB+ into 10 standard board codes. AI and UAI offers stay apart.
Static data is received through the ready connector; the connection typically works with the API access of your own Hotelbeds account. If you prefer, you can also upload a file you exported, as CSV or JSON.
hotelmapping.org does not sell rooms and is not a supplier. Mapping is done on the data of suppliers you already work with; if you do not work with Hotelbeds, you do not need this connector.
The HM ID is permanent and is never reused. The new Hotelbeds code goes through mapping; if it belongs to the same property, it is linked to the existing HM ID. Exposing code change history through the API and webhooks is planned.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.