Hotel mapping connects records that describe the same property. GIATA’s MultiCodes documentation gives a concrete example: supplier property codes are matched to a shared GIATA-ID. This lets a platform relate offers from different sources to one hotel identity. Source: GIATA: how MultiCodes identifies hotels

A travel example

Imagine two suppliers use different codes and slightly different names for the same property. A proposed mapping process would check identifying details before linking them. A similar name alone should not be your acceptance test, particularly when a chain has several properties in one city.

Keep the offer comparison separate

After confirming the property match, compare room type, occupancy, meal basis and booking conditions. Our recommendation is to treat those as separate checks: identifying the hotel does not establish that two offers are equivalent.

What to ask a provider

Ask how uncertain matches are reviewed, how changes are maintained and how an incorrect match can be reported. Test a property with a similar name nearby and one whose supplier description has changed. Record the expected match so the result can be checked by someone who did not build the integration.

Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.