In a typical scenario, a PMS uses the "Rate and Availability"
API to set inventory, rates and restrictions for a property. The updates are
pushed to Su and data received are communicated with connected channels for the
property. These updates are commonly known as ‘Day Level’ updates. ‘Day Level’
updates are common for all distribution channels. This approach ensures
uniformity and consistency across all distribution channels.
While day-level updates are common and ensure consistency
across channels, there are cases where a property may want to offer different
availability, rates, and close out restriction on specific channels. In such scenarios,
the "Inventory Control" API comes into play.
The "Inventory Control" API allows a Property
Management System (PMS) to have more granular control over inventory, rates,
and close out restriction for each individual channel. This means that the property can
tailor its offerings to different channels based on their specific requirements
or target markets.
You want to set specific availability and rates for three channels, Go-MMT, Expedia and Booking.com.
You can update all 3 channels in a single request. The API allows the property management system (PMS) to apply updates collectively to the three platform. It is however essential to consider the impact of subsequent updates.
When changes are made subsequently, the new updates will overwrite the previous updates. This means that any new data sent through the API request will replace the existing data. As a result, the most recent updates will take precedence, and any previous changes will be discarded.
Here is how it works in more detail:
1. Initial Update: The PMS sends an API request to update rates and availability for multiple channels. Let's say this initial update includes changes to rates and availability for the next two weeks.
2. Subsequent Update: A few days later, the PMS sends another API request with updated rates and availability for the next month. This new update will overwrite the rates and availability previously set for the next two weeks.
3. Overwriting of Data: Once the subsequent update is processed, the rates and availability set in the initial update are no longer in effect. Su will now have the latest information from the most recent API request.
Due
to the overwriting behavior, it is essential to be cautious and accurate when
making updates through the API.