Actions Min Rate Violations

To see the Min rate violations , please click on Actions as shown in the screenshot below.

Whenever there are price violations, our system will mark them under Min rate Violation in Actions as shown in the screenshot below.


When you click on the right-hand side arrow next to "Min Rate Violation," you will be redirected to the corresponding page for more information.

On the Min Rate violation page, you can view the number of prices that got restricted while updating for each date due to the minimum rate rule. Click on "View Details" to access additional information.

If you have resolved the issues and successfully updated the prices for any entries, click on "Mark as Solved."

If you haven't marked the actions as solved, the system will automatically remove the validations after 7 days from the creation date, assuming they have been resolved.


image

After clicking on "Mark as Solved," the system will display a warning asking for confirmation before deleting the specific item. By clicking on "Delete Forever," you can proceed with deleting the entry.

image

Alternatively, you can click on the button to "View details," which will direct you to the detailed page. On this page, you can find the product's name (room and rate plan) for which the updates got restricted. You can also identify whether the update source was Manual or XML, along with the date of the update. The parameter and price that were updated are displayed as well. Additionally, you can see the current Minimum rate value set in the system for the respective product. If you haven't taken any actions to update the correct prices, you can click on "Open Calendar" to proceed with the updates.

image

If you don't want to take any actions or believe that the necessary actions have already been taken, you can click on "Mark as Solved." Additionally, you have the option to mark all of them as solved simultaneously by using the "Mark all as Solved" button located at the top right-hand side.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.