Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
We merge your hotel inventory running on Juniper with the same hotel at your other suppliers under a single permanent HM ID. The Juniper hotel code, any sub-supplier codes, room names and board codes are standardized; hotel IDs from your existing mapping provider or your own system are kept as cross-references.
Juniper (Juniper Travel Technology) is a travel technology company that develops booking engines, B2B and B2C sales, and supplier connectivity software for tour operators, bedbanks and travel agencies.
A tour operator or agency using Juniper can connect to several suppliers through the platform. When the same hotel arrives from these suppliers under different codes, the list bloats and price comparison breaks. By linking each record to a single permanent HM ID, we solve this problem at the source.
| Juniper data | Standard output |
|---|---|
| Hotel code and sub-supplier codes | HM ID (hotel mapping) |
| Room name and room code | Room ID, room type, view (room mapping) |
| Board code and name | RO, BB, HB, HB+, FB, AI, UAI… (board mapping) |
| Zone codes | Country → province → district → resort area (destination mapping) |
| Hotel IDs from other systems | Stored as cross-references |
Static hotel data on the Juniper side is received, normalized and scored against nearby candidate hotels. A score of 0.97 or higher matches automatically; records between 0.80 and 0.97 go to an expert for review; below 0.80 creates a new HM ID. The result returns to you through the REST API and a daily dump.
Tour operators and bedbanks that use Juniper as their booking infrastructure benefit most from this connector. For the background on board code confusion, see the board types guide, and for the general process, the what is hotel mapping guide.
A hotel record on a platform like Juniper can carry both the platform's own code and the code of the supplier beneath it. We link both codes to the same HM ID; whichever one you query with, you reach the same hotel.
The platform can run at each customer with a different supplier set, zone tree and board list. That is why mapping is done on the real data in your installation, not on a generic table.
The same board type can arrive as "Ultra All Inclusive" at one supplier, "UAI" at another, or Spanish "Ultra Todo Incluido". All spellings are translated into a standard code.
{
"supplier": "juniper",
"supplier_code": "JNP-207731",
"raw": {
"name": "Kemer Pine Garden Hotel",
"zone": "Kemer - Goynuk",
"room": "Family Room Garden View",
"board": "ULTRA ALL INC"
},
"hm_id": "HM-1061590",
"room_id": "HM-1061590-R04",
"board": "UAI",
"destination": "TR-07-KEMER-GOYNUK",
"external_ids": { "client": "OTL-2231" },
"confidence": 0.993
} 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.
Converts spellings like AI, UAI, Soft AI and HB+ into 10 standard board codes. AI and UAI offers stay apart.
Links supplier destination codes to a country → province → district → resort area hierarchy and to IATA codes.
Mapping inside a platform is usually limited to the suppliers connected to that platform. The HM ID also links your suppliers outside Juniper and the hotel pages on your site to the same identity; board mapping and destination mapping are added on top. Bulk mapping of contracted hotels through a portal and API is on our roadmap.
No. We store the hotel IDs from your existing mapping provider or your own system as cross-references; these IDs return together with the HM ID in the API response.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.