When you map room rates in Mews Channel Manager, what you see on the mapping tab depends on the channel you are setting up. Most channels let Mews read their room rates automatically. A small number do not. And in some cases, you have not yet created the rates on the channel extranet, so there is nothing to map to at all. This article explains the three scenarios so you know what to expect when you open the mapping tab.
For step-by-step guidance on the mapping itself, see the help article How to map room rates to a channel in Mews Channel Manager.
In this article, you can learn about:
Understanding room rate mapping scenarios in Mews Channel Manager
How to tell which scenario applies to you
When you open the room rates mapping tab:
-
If the channel column is empty, and you have already created rates on the channel extranet, refresh the tab. If the channel column is empty because you have not yet created rates on the extranet, you are in Scenario 1.
-
If the channel column shows a list of channel room rates and Mews has suggested best-guess matches next to your Mews rates, you are in Scenario 2.
-
If the channel column has fields where you type in the channel room rate names yourself, rather than a pre-populated list, you are in Scenario 3.
Scenario 1: Rates not yet on the channel extranet
Your Mews room rates cannot map to anything if there is nothing to map them to. Before Mews can read a channel's rates, or before you can type them in manually, they must exist on the channel extranet.
What you see: an empty channel column, or a message telling you no rates are available on the channel.
What to do:
-
Open the channel extranet in a separate tab and log in.
-
Create the room rates you want to sell on the channel.
-
Return to Mews and select Refresh from [channel] to re-read the channel's rates.
-
Continue with Scenario 2 or Scenario 3, depending on the channel.
Scenario 2: Channel supports automatic reading of rates
Most channels support automatic reading of their room rates through a reconciliation API. Mews reads the channel's rates, offers a best-guess match against your Mews rates, and shows you the list to review.
What you see: the channel's room rates in the channel column, with suggested matches drawn to your Mews rates.
What to do:
-
Review each suggested match.
-
Accept the correct ones.
-
Change the ones that are wrong by picking a different Mews room category and rate.
-
Map any remaining unmapped channel rates manually.
This is the standard mapping flow. For detailed step-by-step guidance, including how to use the filters, search, and refresh, see How to map room rates to a channel.
Scenario 3: Channel does not support automatic reading of rates
A small number of channels do not expose their room rates through a reconciliation API. In this case, Mews cannot read the channel's rates for you, so you enter them manually.
What you see: instead of a pre-populated list of channel rates, you see empty fields where you type the channel's room rate names in yourself.
What to do:
-
Open the channel extranet in a separate tab and copy the exact rate names.
-
Return to Mews and type each rate name into the corresponding field, matching it to the Mews rate you want to link it to.
-
Repeat for every channel room rate.
Note: Manual mapping is the slowest and most error-prone scenario. Copy the rate names exactly, character for character. A typo means bookings from that rate cannot land on the correct Mews room, so double-check what you have entered before saving.
What to do next
Once you know which scenario applies to your channel:
-
If you are in Scenario 1, create your rates on the channel extranet first, then return to Mews.
-
If you are in Scenario 2 or Scenario 3, follow the step-by-step in How to map room rates to a channel using the interaction pattern for your scenario.
-
Once your rates are mapped, move to the final step of the setup, enabling the channel. See How to enable a channel.
Knowing which scenario applies to your channel means you go into the mapping step with the right expectations, and you spend your time on the actual mapping rather than trying to figure out why the screen looks different from what you expected.
Help article