Adicionar e atualizar inventário
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Use elementos <Result> em uma
mensagem de transação para
definir ou atualizar os preços dos quartos e definir o inventário disponível. Esses elementos
fazem referência a dados predefinidos para descrições de quartos e pacotes de quartos usando
metadados definidos em uma mensagem de transação separada. A atualização do
inventário depende do tipo de
modo de entrega e da
frequência preferida.
O exemplo a seguir mostra um elemento <Result> que define os inventários
e os preços de dois quartos:
<?xml version="1.0" encoding="UTF-8"?>
<Transaction timestamp="2023-04-24T16:20:00-04:00" id="42">
<Result>
<Property>060773</Property>
<RoomID>RoomType101</RoomID>
<Checkin>2023-04-10</Checkin>
<Nights>2</Nights>
<Baserate currency="USD">278.33</Baserate>
<Tax currency="USD">25.12</Tax>
<OtherFees currency="USD">2.00</OtherFees>
<AllowablePointsOfSale>
<PointOfSale id="site1"/>
</AllowablePointsOfSale>
</Result>
<Result>
<Property>052213</Property>
<RoomID>RoomType101</RoomID>
<Checkin>2023-04-17</Checkin>
<Nights>2</Nights>
<Baserate currency="USD">299.98</Baserate>
<Tax currency="USD">26.42</Tax>
<OtherFees currency="USD">2.00</OtherFees>
<AllowablePointsOfSale>
<PointOfSale id="otto"/>
<PointOfSale id="simon"/>
</AllowablePointsOfSale>
</Result>
</Transaction>
O exemplo acima não contém informações sobre o ambiente, como
descrição, URL e legenda da imagem, nome do ambiente ou capacidade. Essas informações podem ser enviadas em uma mensagem de transação inicial ao Google e, em seguida, podem ser referenciadas pelo RoomID em todas as atualizações de preço e inventário subsequentes.
Para mais detalhes, consulte Definir metadados de sala e pacote.
Além de definir preços para itinerários, você também pode usar o elemento <Result> para:
Todos os direitos reservados. Java é uma marca registrada da Oracle e/ou suas afiliadas.
Última atualização 2025-07-25 UTC.
[null,null,["Última atualização 2025-07-25 UTC."],[[["\u003cp\u003eUse \u003ccode\u003e<Result>\u003c/code\u003e elements within Transaction messages to manage room prices and inventory availability.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003e<Result>\u003c/code\u003e elements reference room and Room Bundle metadata defined in separate Transaction messages.\u003c/p\u003e\n"],["\u003cp\u003eInventory updates are influenced by the chosen delivery mode and update frequency.\u003c/p\u003e\n"],["\u003cp\u003eRoom and Room Bundle descriptive information (like descriptions, images, and capacity) is sent separately and referenced by RoomID.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003e<Result>\u003c/code\u003e elements can also be used to remove inventory and define Room Bundles.\u003c/p\u003e\n"]]],[],null,["# Add and Update Inventory\n\nYou should use [`\u003cResult\u003e`](../xml-reference/transaction-messages#Result) elements in a\n[Transaction message](/hotels/hotel-prices/dev-guide/transaction-overview) to\nset or update room prices and define available inventory. These elements\nreference a predefined data for descriptions of rooms and Room Bundles using\nmetadata that you define in a separate Transaction message. Updating your\ninventory depends upon the type of\n[delivery mode](/hotels/hotel-prices/dev-guide/delivery-mode) and your\npreferred frequency.\n\nThe following example shows a `\u003cResult\u003e` element that defines the inventories\nand prices for two rooms: \n\n \u003c?xml version=\"1.0\" encoding=\"UTF-8\"?\u003e\n \u003cTransaction timestamp=\"2023-04-24T16:20:00-04:00\" id=\"42\"\u003e\n \u003cResult\u003e\n \u003cProperty\u003e060773\u003c/Property\u003e\n \u003cRoomID\u003eRoomType101\u003c/RoomID\u003e\n \u003cCheckin\u003e2023-04-10\u003c/Checkin\u003e\n \u003cNights\u003e2\u003c/Nights\u003e\n \u003cBaserate currency=\"USD\"\u003e278.33\u003c/Baserate\u003e\n \u003cTax currency=\"USD\"\u003e25.12\u003c/Tax\u003e\n \u003cOtherFees currency=\"USD\"\u003e2.00\u003c/OtherFees\u003e\n \u003cAllowablePointsOfSale\u003e\n \u003cPointOfSale id=\"site1\"/\u003e\n \u003c/AllowablePointsOfSale\u003e\n \u003c/Result\u003e\n \u003cResult\u003e\n \u003cProperty\u003e052213\u003c/Property\u003e\n \u003cRoomID\u003eRoomType101\u003c/RoomID\u003e\n \u003cCheckin\u003e2023-04-17\u003c/Checkin\u003e\n \u003cNights\u003e2\u003c/Nights\u003e\n \u003cBaserate currency=\"USD\"\u003e299.98\u003c/Baserate\u003e\n \u003cTax currency=\"USD\"\u003e26.42\u003c/Tax\u003e\n \u003cOtherFees currency=\"USD\"\u003e2.00\u003c/OtherFees\u003e\n \u003cAllowablePointsOfSale\u003e\n \u003cPointOfSale id=\"otto\"/\u003e\n \u003cPointOfSale id=\"simon\"/\u003e\n \u003c/AllowablePointsOfSale\u003e\n \u003c/Result\u003e\n \u003c/Transaction\u003e\n\nThe example above doesn't contain information about the room, such as a\ndescription, a picture URL and caption, the room's name, or its capacity. Such\ninformation can be sent in an initial Transaction message to Google, and can\nthen be referenced by RoomID in all subsequent pricing and inventory updates.\nFor more details, see [Define room and package\nmetadata](/hotels/hotel-prices/dev-guide/room-bundles#metadata).\n\nIn addition to defining prices for itineraries, you can also use the `\u003cResult\u003e`\nelement to do the following:\n\n- Remove a room or itinerary from inventory. [Learn\n more](/hotels/hotel-prices/dev-guide/removing-inventory)\n\n- Specify additional room types as Room Bundles. [Learn\n more](/hotels/hotel-prices/dev-guide/room-bundles)"]]
