Hotel mapping is the work of recognising that listings from different suppliers are the same property — and that their differently named rooms are the same room type — so a booking site shows each hotel once with comparable prices. TripGic maps properties and room types across 2M+ hotel properties from bed-banks, online travel suppliers and direct chains including Marriott, Hilton, IHG and Accor, and removes the duplicates before results reach your website, app or agent portal.
The problem mapping solves
Connect three hotel suppliers and the same property can arrive three times: once with an abbreviated name, once with a translated name and once with a slightly different address. Rooms are worse — one supplier sells a “Deluxe King”, another a “King Room Deluxe”, a third a “Superior Double, King Bed”. Without mapping, travellers scroll past duplicates, agents compare the wrong rooms, and you cannot reliably sell the cheapest valid offer.
| Without mapping | With mapping |
|---|---|
| The same hotel appears several times with different spellings | One listing per hotel |
| Room names from different suppliers cannot be compared | Room types aligned across suppliers |
| Agents match offers by hand | Comparable rates side by side |
| Cheapest valid offer is easy to miss | Best offer selectable automatically |
Property mapping and room mapping
Mapping happens at two levels. Property mapping links each supplier’s hotel record to one master property. Room mapping aligns each supplier’s room descriptions to a common room type, so “Deluxe King” and “King Room Deluxe” are compared as the same product. Deduplication then collapses the result set to one hotel with every supplier’s rate behind it. TripGic does both before results are returned, so your front end works with clean, comparable data.
Suppliers covered
| Source | Examples |
|---|---|
| Bed-banks and wholesalers | Hotelbeds (certified partner), RateHawk (certified partner), TBO, WebBeds |
| Online travel suppliers | Agoda, Expedia Group |
| Direct hotel chains | Marriott, Hilton, IHG and Accor |
| Your own contracts | Directly contracted hotels loaded alongside supplier inventory and mapped with it |
Why it matters for margin
Once rooms are comparable, you can sell the cheapest valid offer for the same room instead of whichever supplier happened to load first. After booking, Drop Catch uses the same comparison to watch confirmed refundable bookings and flag when the identical room becomes cheaper — see the price-drop rebooking case study.
Where hotel mapping runs
- Through the hotel booking API, for your own website or app.
- Inside ReservationHub, for B2C storefronts and B2B sub-agent portals.
- Inside Drop Catch, for post-booking rate monitoring.
Comparing sourcing models? See GDS vs bed-bank vs direct contracting.
Frequently asked questions
What is hotel mapping?
Hotel mapping matches listings of the same property from different suppliers to one master hotel, and aligns their room descriptions to common room types, so each hotel appears once with comparable rates.
Does TripGic deduplicate hotels across suppliers?
Yes. TripGic maps properties and room types across its 2M+ hotel properties and removes duplicates, so each hotel appears once with every supplier’s rate behind it.
Which hotel suppliers are mapped?
Bed-banks and wholesalers such as Hotelbeds, RateHawk, TBO and WebBeds, online suppliers such as Agoda and Expedia Group, direct chains including Marriott, Hilton, IHG and Accor, and your own directly contracted hotels.
Is room mapping included in the hotel booking API?
Yes. Property and room mapping run before results are returned by the hotel booking API, and the same mapped content is used in ReservationHub and Drop Catch.
Can my own hotel contracts be mapped too?
Yes. Directly contracted hotels are loaded alongside supplier inventory and sold in the same search.
Related pages
- Hotel booking API →
- TripGic →
- Drop Catch →
- Hotelbeds integration →
- RateHawk integration →
- What is a bed-bank? →
See your hotel suppliers mapped into one clean, deduplicated search.
