Overview of Points of Sale

A Points of Sale (POS) file is an XML file that you upload to Google for processing by using the Hotel Ads Center.

The root element of the Points of Sale file is <PointsOfSale>. Each POS in the file is defined by a <PointOfSale> child element. You can have any number of <PointOfSale> child elements in a Points of Sale file. However, all points of sale refer to the same partner: you cannot use a single Points of Sale file to define points of sale for more than one partner.

The following example shows a Points of Sale file that defines two POSes:

<?xml version="1.0" encoding="UTF-8"?>
<PointsOfSale>
  <PointOfSale id="TravelAgency">
    <DisplayNames display_text="TravelAgency.com" display_language="en"/>
    <DisplayNames display_text="TravelAgency.com.fr" display_language="fr"/>
    <Match status="yes" language="en"/>
    <Match status="yes" language="fr"/>
    <Match status="yes" country="US"/>
    <Match status="yes" country="FR"/>
    <Match status="yes" currency="USD"/>
    <Match status="yes" currency="EUR"/>
    <URL>http://partner.com/landing?hid=(PARTNER-HOTEL-ID)&amp;checkin=(CHECKINYEAR)-(CHECKINMONTH)-(CHECKINDAY)&amp;checkout=(CHECKOUTYEAR)-  (CHECKOUTMONTH)-(CHECKOUTDAY)&amp;language=(USER-LANGUAGE)</URL>
  </PointOfSale>
  <PointOfSale id="Others">
    <DisplayNames display_text="TravelAgency en espanol" display_language="es"/>
    <Match status="yes" language="es"/> 
    <Match status="yes" country="US"/>
    <Match status="yes" currency="USD"/>
    <URL>http://partner-espanol.com/landing?hotelID=(PARTNER-HOTEL-ID)</URL>
  </PointOfSale>
</PointsOfSale>

In this example, English or French speaking end-users in the US or France would match the first POS. This POS has two display names (TravelAgency.com and TravelAgency.com.fr). These two sites support English and French for languages, and US dollars and Euros for currencies. The generated URL that is passed to the POS includes details about the transaction, such as the check-in and check-out dates, hotel ID, and user language.

A Spanish-speaking end-user in the US would match the second POS. However, this POS supports only one display name, one language, and one currency. The generated URL also only sends the hotel ID to the POS. This most likely results in a less-smooth experience for the end-user.

For more developer-focused information, see Points of Sale File Syntax.