Rate handling is one of the fundamental systems in MEWS and a logic that runs through many systems. In my opinion, MEWS implements this quite well with variable pricing, rate restrictions and products including product rules. The technical support of rates in third-party systems is also quite good, as it is a widely used logic.

Since we have been with MEWS for a few months now and have completed the first turn of the year, I have a few points to mention on this topic:
 

• The way in which MEWS regulates special occupancy (single person and additional people) in rates is not particularly flexible (why are only absolute value adjustments possible and not relative ones). I therefore assume that many people use rates or products for these scenarios to be more flexible.
  
  It would be extremely helpful if you could create rate restrictions and product rules based on the number of people in a room.
   
• Yielding is a fantastic logic, but unfortunately you can only adjust the base price (which is often enough). At the turn of the year, however, we would also have to adjust the prices for special occupancy (single person and additional people) and age categories, which is not possible with the current variable pricing system. We then created a new rate for the new year, but since Mews only allows one rate within a reservation, this also caused problems.
  
  It would make sense if you have yielding/variable pricing for special occupancy (single person and additional people) and age categories inside a rate. Just let us change the whole rate price structure for individual days instead of just the base price and also give us relative (percent) adjustments.
   
• The number of age categories in Mews is limited to 5, which is why we had to simplify our pricing structures as we switched to mews. However, since our tourist tax is applied according to age, and this does not correspond to our age categories, it is difficult for us to handle (rn we have a tourist tax product that costs nothing for various age categories).
  
  With the current logic, it would be great if you could create more age categories (in our case, 6 would currently be enough, but initially we would probably have needed like 8 or so).
   

• As already mentioned above, it is extremely inconvenient that you can only enter one rate per reservation. I guess several subsystems would benefit if that would be possible as well. This topic has been raised several times, e.g. when you have to move rooms during your stay, but also in other scenarios (like the year switch).
  
  It would be fantastic if you could set rates in reservations on a daily basis. It would also be extremely useful if there was a system for room changes which also handles the mailings that are sent correct (i could imagine just a “directly connected reservation” relation field for that).

Even on writing this i know that there are some points here that are not that easily solved or have wide effects on different parts of the system. Some things may be pretty fundamental problems where someone could imagine different/new systems that could replace existing ones.

Nevertheless i hope that this gives some insight/inspiration and maybe others have similar problems or would profit from these changes in different scenarios.