# PeakPoint Global hotel mapping solutions

> URL: https://hotelmapping.org/en/integrations/peakpoint-global-hotel-mapping-solutions/ · Language: English

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.

## About the provider

PeakPoint Global is a wholesaler (bedbank) founded in Istanbul that supplies hotel inventory to tour operators, travel agencies and other B2B wholesalers.

## What data we map

- Hotel code (supplier code) → HM ID
- Hotel name, address, phone and coordinates
- Room names → HM room ID (e.g. HM-1052207-R01)
- Board codes → RO, BB, HB, FB, AI, UAI
- City and zone codes → country, province, district, resort area
- Closed hotels and merged duplicate records → HM ID status

## Challenges specific to this provider

- **Changing supplier codes:** 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.
- **Drifting coordinates:** 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.
- **Room names carrying rate conditions:** 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.

## Sample output

**Fictional PeakPoint Global record → HM ID and room ID**

```json
{
  "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"
  }
}
```

## Why should you map PeakPoint Global data?

For an agency that works with multiple [bedbanks](https://hotelmapping.org/en/glossary/bedbank/), PeakPoint Global records do not merge on their own with the same hotels at other suppliers. Each supplier uses its own [supplier code](https://hotelmapping.org/en/glossary/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](https://hotelmapping.org/en/products/hotel-mapping-solutions/) links each hotel to a single HM ID, and [room mapping](https://hotelmapping.org/en/products/room-mapping-solutions/) links each room to a single HM room ID.

## Even if the code changes, the identity does not

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](https://hotelmapping.org/en/guide/what-is-hotel-mapping/).

_Connection status and brand usage will be verified with the provider before launch._

## Frequently asked questions

### What happens if a hotel at PeakPoint Global closes?

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.

### What happens to the "Non Refundable" wording in a room name?

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.

## Related products

- [Hotel mapping solutions](https://hotelmapping.org/en/products/hotel-mapping-solutions/)
- [Room mapping solutions](https://hotelmapping.org/en/products/room-mapping-solutions/)
- [Find Match API solutions](https://hotelmapping.org/en/products/find-match-api-solutions/)
