If a discrepancy is detected between ZaK and an OTA, it may be due to a synchronization error. In these cases, technical support can analyze the situation and provide a solution.
However, before submitting a support request, a thorough verification between both systems is necessary, as many discrepancies are due to incorrect comparisons or outdated information.
How to perform a correct comparison?
To accurately verify the information, the comparison should always be made between:
The values displayed in the OTA's extranet internal calendar.
Public prices visible to customers should not be used, as they may include promotions, taxes, fees, and/or currency conversions; factors that modify the final displayed price and can generate discrepancies unrelated to synchronization errors.
Rate verification and Update status
It is essential to ensure that you are comparing the same rate in both systems. Additionally, it should be verified that there are no pending update errors for that OTA.
If any discrepancies exist, they must be resolved, and the information must be compared again after the update is resubmitted.
How to report a discrepancy?
If, after the previous checks, the discrepancy persists, it will be necessary to send the complete information for analysis. The request must include:
Property (if managing more than one)
OTA, including name and ID
Affected room
Affected rate
Dates on which the discrepancy was detected
Indication of whether the discrepancy corresponds to price, availability, and/or restrictions