This article provides step-by-step troubleshooting for when rates, availability, or inventory changes made in RMS are not reflecting on a connected Online Travel Agent (OTA) channel.
Overview
The RMS Channel Manager automatically pushes rate and availability updates to connected channels when certain changes are made in RMS. However, some changes require a manual resync, and other issues, such as incorrect mapping, configuration errors, or channel-side caching, can prevent updates from appearing on the OTA.
This guide walks through the diagnostic steps in order, from the most common causes to escalation.
Step 1 - Verify Channel Mapping
Incorrect or incomplete mapping is the most common reason updates fail to reach a channel. If an RMS Category or Rate Type is not mapped to the corresponding channel room and rate code, updates will not be sent.
In the side menu of RMS, go to Setup > Online Bookings > Channel Management.
- Select the channel connection and click Edit.
- Review the Room/Rate Mapping section.
- Confirm each RMS Category and Rate Type is correctly mapped to the corresponding channel room and rate codes.
- Use the Channel Category Comparison Report to compare mappings across all channels.
Step 1b — Check “Disable Rate Updates” (Sabre, Hoseasons & AxisRooms only)
For the Sabre SynXis HTNG, Hoseasons OneConnect (Awaze) and AxisRooms connections, a Disable Rate Updates checkbox is available on each mapping row. When this is ticked, RMS will not send rate updates for that room/rate even though availability, restrictions and reservations continue to sync. This is a common cause of rates appearing to be “stuck” on these channels while everything else updates correctly.
In the side menu of RMS, go to Setup > Online Bookings > Channel Management.
- Select the Sabre SynXis HTNG, Hoseasons (OneConnect) or AxisRooms connection and click Edit.
- In the Room/Rate Mapping section, review the Disable Rate Updates column for the affected room/rate.
- If rates should be sent from RMS, untick Disable Rate Updates and Save.
- Perform a Manual OTA Resync for the affected date range, category and rate type.
Step 2 - Check for Stop Sells or Restrictions
A Stop Sell applied to a Category, Rate Type, or Channel will close availability for the affected dates, preventing bookings from being made on the connected OTA.
- Go to Charts > Rate Manager.
- Set the Display to Stop Sell.
- Expand the relevant Category and Channel rows.
- Check if a Stop Sell is active for the affected dates.
- If a Stop Sell is applied unintentionally, untick the checkbox to release it.
Step 3 - Confirm the Category is Available Online
If a Category is set to Inactive or has "Available to RMS Online" disabled, connected channels will not receive updates for that Category.
- Go to Setup > Category/Area.
- Select the affected Category.
- Confirm the Category is Active.
- Confirm Available to RMS Online is enabled.
Step 4 - Review the Channel Log
The Channel Log records all updates sent to and received from connected channels. Reviewing the log can reveal errors or failed updates that explain why changes are not reaching the OTA.
- Go to Setup > Online Bookings > Channel Management.
- Select the channel connection and click Edit.
- Navigate to the Channel Log section.
- Review recent entries for errors or failed updates.
- Note any error messages for troubleshooting or to provide to RMS Support.
Step 5 - Perform a Manual OTA Resync
If the mapping is correct and no restrictions are blocking the update, a Manual OTA Resync will push current rates and availability to the channel.
- Go to Setup > Online Bookings > Channel Management.
- Select the channel connection and click Edit.
- Navigate to Room/Rate Mapping and select Manual OTA Resync.
- Select the Date Range, Category, and Rate Type to resync.
- Click Apply.
Step 6 - Check the Channel Extranet
After performing a resync, verify the data has arrived on the channel side.
- Log in to the channel's extranet portal (e.g., Booking.com, Expedia, Airbnb).
- Verify the rates and availability match what is set in RMS.
- If the extranet shows the correct data but the guest-facing pages do not, contact the channel directly as this is a caching issue on their side.
Comments
0 comments
Please sign in to leave a comment.