Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Static hotel data from TBO.com is processed on hotelmapping.org as a ready connector. Hotel codes, room names, board information and city codes are standardized and linked to a permanent HM ID; TBO.com records merge into the same hotel card as your other suppliers.
TBO.com is a B2B travel distribution platform that offers hotels and other travel products to travel agencies. It originated in India and is widely used in Middle Eastern and Asian markets. This page covers hotel data only.
TBO.com inventory can overlap with other bedbanks. Without mapping, the same hotel appears in your list as separate cards and price comparison breaks. Hotel mapping gathers these records under a single HM ID. You can find the details of the concept in the what is hotel mapping guide.
| Topic | Approach |
|---|---|
| City-level destination | Drill down to the resort area from coordinates |
| Abbreviated room name | Type, class, view and bed labels |
| Different board spellings | Translation to the standard board code |
| Duplicate record at the same supplier | Conflict queue and human review |
Static data is received through the ready connector, stored in its raw form and versioned. Names and addresses are normalized, and each record is scored against 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 the zone hierarchy is built on the destination mapping page, and room abbreviations in the room type abbreviations guide.
Destination information can arrive at city level; resort areas such as Side, Belek or Kemer may be listed only under Antalya. The area must be re-derived from coordinates and address.
Room names can mix abbreviations such as DBL, TWN, SV and LV with different spelling habits. The same room arrives with different abbreviations at different suppliers.
On platforms that collect inventory from different sources, the same hotel can appear with more than one record within the supplier itself. These records go through a conflict check.
{
"supplier": "tbo",
"code": "1402783",
"supplier_name": "Side Olive Bay Hotel",
"supplier_city": "Antalya",
"hm_id": "HM-1073418",
"destination_id": "TR-07-MANAVGAT-SIDE",
"confidence": 0.976,
"rooms": [
{
"supplier_room": "DBL SV BALCONY",
"hm_room_id": "HM-1073418-R02",
"type": "room",
"bed": "double",
"max_occupancy": 2,
"view": "sea",
"features": ["balcony"]
}
]
} 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.
Links supplier destination codes to a country → province → district → resort area hierarchy and to IATA codes.
The area is derived from the coordinates and address selected from supplier records (coordinate validation planned) and placed in the country → province → district → resort area hierarchy. Uncertain records go to expert review.
No. hotelmapping.org works with hotel data only. Tour, activity and transfer data are outside the scope of this service.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.