{"id":2031,"date":"2025-10-01T14:04:16","date_gmt":"2025-10-01T14:04:16","guid":{"rendered":"https:\/\/faqs.travelsoftservices.com\/?post_type=manual_documentation&p=2031"},"modified":"2025-10-01T14:17:16","modified_gmt":"2025-10-01T14:17:16","slug":"hotel-mapping","status":"publish","type":"manual_documentation","link":"https:\/\/faqs.travelsoftservices.com\/en\/documentation\/consolidated-services\/hotel-mapping\/","title":{"rendered":"Hotel Mapping"},"content":{"rendered":"\n

What to do when there is a mapping error and how to avoid them (GIATA)<\/strong><\/strong><\/strong><\/h4>\n\n\n\n
What is a Mapping Error and How Do We Handle It?<\/strong><\/h5>\n\n\n\n

A mapping error<\/em> occurs when an accommodation is incorrectly linked \u2014 for example, the same hotel appears multiple times, data from different hotels gets mixed up, or a property is not properly associated with its correct GIATA ID<\/strong>.
Examples include differences like:<\/p>\n\n\n\n

\n

\u201cHotel ABC Downtown\u201d vs. \u201cHotel ABC Main Street\u201d<\/em><\/p>\n<\/blockquote>\n\n\n\n

GIATA<\/strong> provides the mapping service, and errors can happen due to the dynamic nature of the data: changes in hotel names, IDs, room types, descriptions, and more. Given the volume of updates processed daily, occasional mistakes are inevitable.<\/p>\n\n\n\n

\n

Please note: According to our agreement, we are covered by a disclaimer clause<\/strong> with the operator, meaning we cannot be held liable for mapping errors<\/strong>, just as GIATA itself assumes no responsibility.<\/p>\n<\/blockquote>\n\n\n\n

What Do We Do When a Mapping Error Occurs?<\/strong><\/h5>\n\n\n\n
    \n
  1. Monitoring<\/strong>: Our team actively monitors reservations to detect inconsistencies.<\/li>\n\n\n\n
  2. Validation<\/strong>: When a potential mapping error is spotted, we contact GIATA<\/strong> to confirm whether it\u2019s an error or simply a case of a hotel listed under a different name.<\/li>\n\n\n\n
  3. Operator Communication<\/strong>: Once verified, we inform the Operator<\/strong> so they can take appropriate action:\n
      \n
    • If the booking is refundable<\/strong>, they may cancel the incorrect reservation and rebook the correct property.<\/li>\n\n\n\n
    • If the booking is non-refundable<\/strong>, cancellation may incur charges, and we will follow the operator\u2019s decision.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
      How Can You Help Avoid Mapping Errors?<\/strong><\/h5>\n\n\n\n

      To minimize these rare cases, we suggest:<\/p>\n\n\n\n

        \n
      • Always review the hotel names<\/strong> within the Hotels\/Accommodations tab<\/strong> of the reservation.<\/li>\n\n\n\n
      • Check for discrepancies across the three hotel name columns<\/strong>:\n
          \n
        1. Voucher Name<\/strong>: What appears on the client\u2019s voucher.<\/li>\n\n\n\n
        2. Supplier Name<\/strong>: The name provided by the accommodation supplier.<\/li>\n\n\n\n
        3. Traces Name<\/strong> (if filled)<\/em>: The hotel name returned by the supplier in traces\/logs.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n\n\n\n

          Example of error:<\/p>\n\n\n\n

          \"\"<\/figure>\n\n\n\n

          <\/p>\n","protected":false},"author":1,"featured_media":0,"parent":152,"menu_order":3,"template":"","manualdocumentationcategory":[2],"manual_doc_tag":[],"class_list":["post-2031","manual_documentation","type-manual_documentation","status-publish","hentry","manualdocumentationcategory-faqs-travelsoft"],"_links":{"self":[{"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manual_documentation\/2031","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manual_documentation"}],"about":[{"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/types\/manual_documentation"}],"author":[{"embeddable":true,"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manual_documentation\/2031\/revisions"}],"predecessor-version":[{"id":2033,"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manual_documentation\/2031\/revisions\/2033"}],"up":[{"embeddable":true,"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manual_documentation\/152"}],"wp:attachment":[{"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/media?parent=2031"}],"wp:term":[{"taxonomy":"manualdocumentationcategory","embeddable":true,"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manualdocumentationcategory?post=2031"},{"taxonomy":"manual_doc_tag","embeddable":true,"href":"https:\/\/faqs.travelsoftservices.com\/en\/wp-json\/wp\/v2\/manual_doc_tag?post=2031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}