A pricing strategy doesn’t only depend on having good recommendations – it also depends on executing them on time. That’s why BEONx offers a functionality that automates the sending of price and restriction recommendations directly from the RMS to the Channel Manager or PMS.
This sending can be done manually or by activating Autopilot mode, which automates the execution based on the recommendations generated by the system.
Additionally, to ensure greater control during sensitive periods (high demand, special events, new openings…), the system allows you to configure exception rules that fully or partially pause these sends based on the conditions determined by the hotel.
🚀 What is Autopilot?
Autopilot is a feature that allows recommendations to be sent automatically from the RMS without manual intervention. In other words, when the system generates new recommendations (prices, MLOS, closures…), they are automatically executed towards the distribution system (PMS or Channel Manager).
🟢 Benefits of using Autopilot
Greater operational efficiency: no need for daily review.
Faster response to demand changes.
Better alignment between strategy and execution.
Reduction of human error.
To activate Autopilot (or manual sends), simply go to Configuration > Pricing > Publish recommendations, provided that the hotel has sending enabled.
🛑 What if I don’t want them to be sent all the time? Exception Rules
There are moments when it may make sense to pause or limit recommendation sending:
Critical periods when each change is manually controlled.
Strategy testing or transition phases.
Situations where only certain spaces or rate plans should be paused.
The need to review certain conditions before execution (e.g., avoid prices that are too low).
To handle this, BEONx allows you to create customized sending rules from the same configuration screen.
⚙️ How do sending rules work?
From the bottom of the Configuration > Pricing > Publish recommendations screen, you can create rules by clicking “+ Create publishing rule”.
These rules allow you to stop sending in a granular way, combining multiple conditions:
🗓️ Dates
You can specify which dates the rule applies to:
A specific date
A date range
From a specific date onward (e.g. from April 9, 2025, sends will be paused from that date forward)
Days from a specific day (e.g. from day 30 forward: if today is June 17, 2025, sends will be paused from July 17, 2025, and so on)
Up to a specific number of future days (e.g. for the next 30 days: if today is June 17, 2025, sends will be paused until July 17, 2025, and so on. Dates outside this period will be sent)
📤 Sending source
You can choose which type of send to pause:
Autopilot (automatic sends)
Manual sends
Both
🏨 Spaces and Rate Plans
You can pause sending for the whole hotel or for specific spaces and rate plans. Example: Pause recommendations only for Suites during the October long weekend.
🌐 Sends by endpoint
If you work with two endpoints (e.g., a PMS and a Channel Manager), you can specify if the rule should pause sending only to one of them. This gives you even more granular control over which system receives recommendations.
Example: You can allow recommendations to continue to the Channel Manager, but pause sends to the PMS during a high-sensitivity period.
📈 Additional conditions
You can add conditions so that the send is only paused if certain criteria are met. Available measures:
Sent Price
Sent MLOS
Sales Closure (sales closure recommendation)
OTA Comparison (price or MLOS): sent price vs. current OTA price, or sent MLOS vs. current OTA MLOS
Then, you can define the mathematical condition:
| Measure | Condition | Value (example) | What it does |
|---|---|---|---|
| Sent price | Less than | 100 | Pauses if the sent price is < 100. I.e., prices from 0 to 99.99 are not sent. |
| Less than or equal to | 100 | Pauses if the sent price is ≤ 100. I.e., prices from 0 to 100 are not sent. | |
| Greater than | 100 | Pauses if the sent price is > 100. I.e., prices from 100.01 and above are not sent. | |
| Greater than or equal to | 100 | Pauses if the sent price is ≥ 100. I.e., prices from 100 and above are not sent. | |
| Equal to | 100 | Pauses if the sent price = 100. | |
| Different from | 100 | Pauses if the sent price ≠ 100. | |
| Sent MLOS | Less than | 2 | Pauses if the sent MLOS is < 2. I.e., MLOS 1 is not sent. |
| Less than or equal to | 2 | Pauses if the sent MLOS is ≤ 2. I.e., MLOS 1 and 2 are not sent. | |
| Greater than | 2 | Pauses if the sent MLOS is > 2. I.e., MLOS 3 and above are not sent. | |
| Greater than or equal to | 2 | Pauses if the sent MLOS is ≥ 2. I.e., MLOS 2 and above are not sent. | |
| Equal to | 2 | Pauses if the sent MLOS = 2. | |
| Different from | 2 | Pauses if the sent MLOS ≠ 2. | |
| Close/open recommendation | Open sales | - | Pauses if the system recommends to open sales. |
| Closed sales | - | Pauses if the system recommends to close sales. | |
| Sent price vs. current OTA price | Less than | 5 | Pauses if the sent price is < OTA price by at least 5 units. E.g., if OTA is 100 → pause if recommended price is < 95 (94,55 won’t be sent, 95 will be sent). |
| Less than or equal to | 5 | Pauses if the sent price is ≤ OTA price by at least 5 units. E.g., if OTA is 100 → pause if recommended price is ≤ 95 (94,55 and 95 won’t be sent but 95,01 will be sent). | |
| Greater than | 5 | Pauses if the sent price is > OTA price by at least 5 units. E.g., if OTA is 100 → pause if recommended price is > 105 (105,1 won’t be sent and 105 will be sent). | |
| Greater than or equal to | 5 | Pauses if the sent price is ≥ OTA price by at least 5 units. E.g., if OTA is 100 → pause if recommended price is ≥ 105 (105 and 106 won’t be sent but 104,99 will be sent). | |
| Equal to | - | Pauses if there’s no difference between sent and OTA price. | |
| Different from | - | Pauses if there’s any difference between sent and OTA price. | |
| Difference less than | 5 | Pauses if the price difference between the sent price and the OTA price is less than ±5 units. In other words, the price will only be sent if the absolute difference is equal or greater than 5 units. E.g., if OTA is 100 → it will not be sent if the sent price is between 95,01 and 104,99 (inclusive). That is, it will only be sent if the price is equal to or lower than 95 or equal to or higher than 105. | |
| Difference greater than | 5 | Pauses if the price difference is greater than ±5 units.That is, it will only be sent if the absolute difference is less or equal than 5 units. E.g., if OTA is 100 → it will not be sent if the sent price is > 105 (not included) or < 95 (not included). In other words, if the sent price is between 95 and 195 (inclusive), it will be sent, but prices ≤ 94,99 and ≥105,01 will not be sent. | |
| Sent MLOS vs. OTA MLOS | Less than | 2 | Pauses if sent MLOS is < OTA MLOS by at least 2 units. E.g., if OTA MLOS is 5 → pause if sent MLOS is < 3 (MLOS 1 and 2 won’t be sent but 3 or greater will be sent). |
| Less than or equal to | 2 | Pauses if sent MLOS is ≤ OTA MLOS by at least 2 units. E.g., if OTA MLOS is 5 → pause if sent MLOS is ≤ 3 (MLOS 2 and 3 won’t be sent but MLOS 4 and 5 will be sent). | |
| Greater than | 2 | Pauses if sent MLOS is > OTA MLOS by at least 2 units. E.g., if OTA MLOS is 3 → pause if sent MLOS is > 5 (MLOS 6 or bigger won’t be sent but MLOS 3, 4 or 5 will be sent). | |
| Greater than or equal to | 2 | Pauses if sent MLOS is ≥ OTA MLOS by at least 2 units. E.g., if OTA MLOS is 3 → pause if sent MLOS is ≥ 5 (MLOS 5 or greater won’t be sent but MLOS 3 or 4 will be sent). | |
| Equal to | - | Pauses if there’s no difference between sent and OTA MLOS. | |
| Different from | - | Pauses if there’s any difference between sent and OTA MLOS. | |
| Difference less than | 2 | Pauses if the difference between the sent MLOS and the OTA MLOS is less than ±2 units. That is, it will only be sent if the absolute difference is greater than 2 units. E.g., if OTA MLOS is 5 → it will not be sent if the sent MLOS is between 3 and 7 (inclusive). It will be sent if it is ≤ 2 or ≥ 8. | |
| Difference greater than | 2 | Pauses if the difference between sent MLOS and the OTA MLOS is greater than ±2 units. That is, it will only be sent if the absolute difference is less than 2 units. E.g., if OTA MLOS is 5 → it will not be sent if the sent MLOS is ≤ 3 or ≥ 7. It will be sent if it is between 4 and 6 (inclusive). |
🔔 Automatic Alerts
When creating the rule, you can enable an automatic alert to be notified in the Alerts module whenever a send is paused due to that condition.
This allows you to stay in control without manually reviewing each case.
❓ FAQs
| Questions | Suggested Answer |
|---|---|
| Why wasn’t a recommendation sent? | “There might be an active rule preventing the sending. Let’s check if there are any conditions applied for those dates, spaces, or prices.” |
| Can I stop sending for just one specific rate? | “Yes, you can select specific spaces and rate plans when creating the rule.” |
| What’s the difference between manual and automatic pause? | “You can pause only Autopilot if you want to validate before sending, or just manual sending if you prefer everything to be automated.” |
✅ Key Takeaways
Autopilot lets you automate sending and increase operational efficiency.
Sending rules offer total control over what, when, and how recommendations are executed.
You can combine date, send type, space, rate plan, and specific criteria.
The system provides automatic alerts for proactive management.
💡 A powerful feature to automate… without losing control.