Downgrades not syncing properly with OTAs linked with the direct interfaces
Customer X has booked room category #1. If I manually upgrade him (drag and drop) to a higher category, say #2, then the OTA's availabilities will be updated to reflect this upgrade. Then, If I manually downgrade X in his original requested category the OTA'a availabilities will be once more updated and revert to their original state. However, if X is downgraded not by manual drag and drop but by being "bumped" into his original category through the dragging and dropping of another customer Y onto X's room, then the new availabilities resulting from this bumped downgrade will not be sent to the OTAs, resulting in a wrongful state of synchronicity that may eventually lead to an overbooking. It doesn't make sense for Mews to sync the Downgrade when it's manual but not when it is provoked by a bump.
Yorgo Xudous
shared this idea