Your pricing strategy, written by you
Sentinel AI runs if-then rules that you write: triggers, conditions and actions, with a simulation mode before going live and a log of every change. Your logic, not a black box that decides without explaining.
What the pricing rules engine is
A pricing rule is a conditional instruction you write: if X happens, do Y. You define the trigger (occupancy, pickup, meaning the net bookings coming in for a date, a competitor price, a calendar event, the time of day), the conditions that scope it (day of week, date range, season, room type) and the action (raise or lower a percentage, set a rate, or notify you only). The engine evaluates them every day across your calendar and runs them within your price limits.
In a black-box RMS, the “rules” are parameters of the vendor algorithm: you turn knobs and trust. Here the rule is your own logic: readable, simulatable and auditable. Your strategy stops living in one person’s head or a spreadsheet and becomes logic that runs on its own, while remaining yours.
Your strategy, turned into executable logic
Triggers, conditions and actions you write yourself, inside R2 OS.
Readable rules, in business language
An if-then canvas where you draft your strategy in hotel terms: occupancy, dates, competitors, not code. “If occupancy drops below 50% at 7 p.m. and it is a weekend, lower 10%, never below $1,200”. Anyone on your team can read the rule and understand exactly what it does.
- Triggers, conditions and actions in plain sentences
- Start with 2 or 3 simple rules and refine later
Triggers from your real business
Fire on projected occupancy, recent pickup, a competitor price, lead time, day of week or a calendar event. And scope every rule by date range, season or room type: a low-season Tuesday promotion never touches your conference weekend.
- Every trigger is data your hotel already generates
- Conditions limit where and when each rule applies
No rule jumps your limits
Your price floors and ceilings, per season and per category, are the boundary no rule can cross. The worst week of the year does not define what your hotel is worth, and a demand peak never publishes an absurd rate that costs you reviews. The rule proposes; the limit always wins.
- Floor and ceiling per season and room type
- A badly written rule cannot do damage outside the frame
Simulate before going live
Run any rule in simulation mode: it is evaluated against your real calendar and shows you the prices it would have produced, day by day, without touching a single published rate. You see the full effect of your logic before switching it on. Zero surprises in production.
- The rule is evaluated but not applied until you decide
- Compare the current price against what the rule would propose
Every change with its why
Every execution is logged: which rule fired, which condition was met, what price it produced and when. If several rules apply to the same day, an explicit priority order decides which wins and the log shows it. When ownership asks why a rate changed, the answer is one click away.
- A log of every firing, end to end
- Explicit priorities when two rules collide
Measure what your rules produce
Sentinel AI live analytics, occupancy, ADR (your real average rate) and RevPAR (revenue per available room), show you how the business behaves with your rules on. Adjust the one that is not working, switch off one or all of them at any moment and go back to manual without friction.
- Rules and results on the same screen, no spreadsheets
- Switch them off individually or all at once, whenever you want
In other systems, the “rules” are parameters of the vendor algorithm. In Sentinel AI the rule is yours: you write it, simulate it, switch it on and can read exactly why every price changed.
Your rules vs. the black box and the spreadsheet
Why logic written by you beats a closed algorithm and a spreadsheet.
| SENTINEL AI | Black-box RMS | Spreadsheet | |
|---|---|---|---|
| You write the strategy, not the vendor | |||
| Runs on its own, every day | |||
| You can read why every price changed | |||
| Simulation mode before touching real rates | |||
| Every change lands in an auditable log | |||
| The strategy survives team turnover |
Frequently asked questions
What is a pricing rules engine?
How is it different from an RMS with an automatic algorithm?
Do I need to be a professional revenue manager to use it?
What happens if two rules collide on the same day?
Can I test a rule without affecting my real prices?
Do rules replace demand forecasting?
PUT YOUR REVENUE TO WORK
Book a demo and see how Sentinel AI suggests the price of every night from your own data.