When transmitting inventories, rates or stay restrictions, a third party software needs to notify for which room types, which rate plan or which sellable product (room type + rate plan).
Within the OTA protocol, several XML atttributes, to identify a room type, have relatively similar naming. Because of this, throughout different implementations, the different attributes have been mixed up.
Default room type identification
By default, Hotel-Spider uses the "InvCode" attribute for identifying the room type for which the update is received.
Re-use of existing developments
Should the third party software client already be able to transmit the same OTA messages but uses a different attribute to identify the room type it is trying to update, contact our support team. Our interfaces can be configured to take into account the XML attribute used to in the third party's existing implementation.
The same logic applies for the identification of the rate plans a third party software client is trying to update.
Default rate plan identification
By default, Hotel-Spider uses the "RatePlanCode" attribute for identifying the rate plan for which the update is received.
Re-use of existing developments
Should the third party software client already be able to transmit the same OTA messages but uses a different attribute to identify the rate plan it is trying to update, contact our support team. Our interfaces can be configured to take into account the XML attribute used to in the third party's existing implementation.