Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
We merge hotel and room records from PeakPoint Global with the same hotels at your other suppliers under a single permanent HM ID. Even if a supplier code changes, the HM ID stays fixed; room names and board types are translated into standard labels.
PeakPoint Global is a wholesaler (bedbank) founded in Istanbul that supplies hotel inventory to tour operators, travel agencies and other B2B wholesalers.
For an agency that works with multiple bedbanks, PeakPoint Global records do not merge on their own with the same hotels at other suppliers. Each supplier uses its own supplier code and its own room names. As a result, the same hotel repeats in the list and the same room appears under different names. Hotel mapping links each hotel to a single HM ID, and room mapping links each room to a single HM room ID.
Supplier codes change over time: a hotel closes, is renamed or two records merge. If your system is tied to the supplier code, every change requires a manual fix. If it is tied to the HM ID, the code change is remapped in the background and the identity stays the same on your side.
| Situation | Effect on the HM ID |
|---|---|
| Supplier issues a new code | The new code is linked to the same HM ID |
| Hotel closes | The HM ID’s status becomes closed, the ID is not reused |
| Two HM IDs for the same hotel merge | The removed ID’s status becomes merged; merged_into points to the surviving ID |
You can track changes through the daily delta dump or through the GET /v1/suppliers/peakpoint-global/codes/{code} call; a detailed history of code changes is planned as a separate product. In the example below, the hotel name and codes are fictional. For the general workflow, see the what is hotel mapping guide.
A supplier code can change when a hotel closes, is renamed or when two records merge. An HM ID is never given to a different hotel; the new code is rescored and linked to the same hotel.
In wholesaler data, coordinates sometimes fall on the city center or a general point in the area. That is why distance alone does not decide; it is scored together with name, address and phone.
In names such as "Standard Room Land View - Non Refundable", the refund condition must be separated from the room type. Otherwise the same room appears in the list as two different rooms.
{
"supplier": "peakpoint-global",
"supplier_code": "PPG-0049812",
"supplier_name": "Lara Palm Htl",
"supplier_city": "Antalya",
"supplier_room": "Standard Room Land View - Non Refundable",
"match": {
"hm_id": "HM-1052207",
"name": "Lara Palm Hotel",
"destination_id": "TR-07-MURATPASA-LARA",
"room_id": "HM-1052207-R01",
"room": { "type": "room", "class": "standard", "view": "land" },
"confidence": 0.991,
"decision": "auto_match"
}
} 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.
Send name, address and coordinates; get back an HM ID and confidence score. No supplier code needed.
The HM ID's status becomes "closed" and the ID is never given to another hotel. If it turns out the same hotel was opened under two separate HM IDs, the records are merged; the removed ID's status becomes "merged", the merged_into field points to the surviving ID, and existing links in your system do not break.
In room mapping, refund conditions and campaign wording are separated from the room type. This way, refundable and non-refundable prices for the same room can be compared under the same HM room ID.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.