Automate hotel rates.
Keep the final say.
Hotel dynamic pricing software for independent hotels. Choose a pickup-sensitive Zone engine or a seasonal Pricing Matrix, set the guardrails, and send approved rates through your supported channel-manager connection.
Run fully automated, stay advisory, or mix the two by date. Every saved rate shows the rule, the inputs and whether it was automatic, accepted, overridden or manual. The optional competitor floor requires Competitor Rate Intelligence.
Automate the repeatable work without hiding the decision.
Built for independent hotels moving from spreadsheets or manual channel updates to controlled pricing automation.
Let the selected engine save and send rates inside your guardrails, while high-stakes dates remain one manual decision away.
Open the audit trail to see the rule, user, timestamp and whether the suggested rate was accepted or overridden.
Approve the hotel rate once and send it through the supported channel-manager connection, with success or failure logged.
Pickup-sensitive. Lead-time-aware. Defended.
The Zone engine is the primary pricing model — and the one most properties should run on. It does not store an absolute price; it stores a delta from your most recent saved rate. Every recalculation asks one question: relative to yesterday's snapshot, how did occupancy move, and where should the price land as a result? Then it applies the multiplier for the current zone, the direction (up or down), and the lead-time band — and keeps the result between the floor and the ceiling you set.
The fit: properties operating in dynamic markets with sharp pickup curves. Up and down moves use different multipliers (anti-yo-yo asymmetry), and close-in dates can react harder than far-out dates. If Competitor Rate Intelligence is active, an optional competitor floor can keep the result above the observed public-market minimum × your configured ratio.
- Two rule shapes — proportional (continuous, smooth response) or threshold (stepped, only on zone-crossings)
- Lead-time multipliers — close-in (0–7 days) reacts harder than far-out (31+ days), configurable buckets
- Up / down asymmetry — raise quickly when pickup accelerates, lower cautiously when it slows
- Floor + ceiling — every price kept inside a band around the day's baseline (defaults: 70% / 150%)
- Optional competitor floor — requires Competitor Rate Intelligence and uses the observed public-market minimum × your ratio
- Auditable — every move is a new rate row, with the full reasoning attached
When a publishable rate table beats reactivity.
Some properties don't want dynamic. Resort calendars with a published high/low rate. Group contracts with parity rules. Brand-mandated table-style strategies. For these, the Matrix engine carries a four-level rule structure: Pricing Group → Rule → Rate Level → Price. A pricing group covers a period (season, holiday, date range). A rule sits inside the group, scoped to a room type. A rate level defines an occupancy band — Low, Medium, High, Peak.
At any moment, the platform reads the day's actual occupancy, finds the right rate level, picks the right price for that day-of-week, and shows it on the Pricing Map. The rule is visible. The math is simple. The override is one click. Switch between Matrix and Zone with a single setting — the rest of the platform (calendar, channel push, audit log, closed-period rules) doesn't change.
- Nights-based — recommendation triggers on absolute room-night counts
- Occupancy-based — recommendation triggers on % occupancy
- Event override — holidays + special events get their own pricing group
- Switch to Zone any time — the calendar, channel push and audit log carry over unchanged
Both engines share everything except the math.
Whichever engine your hotel runs on, the rest of the platform behaves identically. The Pricing Map view — the day-class calendar where you see each day's rate-level state at a glance — the channel-manager push, the audit log, the closed-period rules, the auto-pricing switch, the override workflow — all shared. The decision you make today is logged the same way regardless of which engine generated the suggestion.
- Shared Pricing Map — the day-class calendar view works identically on both engines
- Shared channel push — Free Sale / Corporate / Cancellation Strict groups, audit-trailed
- Shared auto-pricing — let the engine save automatically, override per day, or run it manually
- Shared closed-period rules — events, manual-strategy windows, booking stops respected by both
- Delta from yesterday's rate
- Continuous or threshold response
- Lead-time-aware multipliers
- Competitor-floor defended
- Absolute prices in a table
- Triggers on occupancy band
- Stepped — one rate per band
- For published seasonal calendars
Full auto-pricing — or advisory only.
The engine computes the rate; you decide what happens next. Turn auto-pricing on and it prices each day by your rules, then sends saved rates through the supported channel-manager connection — you step in only to override a day or a zone when judgement beats the formula. Leave it off and the engine is advisory: it shows the recommended rate on the Pricing Map, and nothing changes until you accept it.
It isn't all-or-nothing. Auto-price the routine days, keep the final call on the high-stakes ones — and the audit log records exactly which was which: priced automatically, accepted by a person, overridden inside the rule, or set fully by hand. Routine work can run automatically without hiding the decision path.
- Auto-pricing on — the engine prices by your rules and sends through the supported channel-manager connection; override any day or zone
- Advisory — the engine recommends on the Pricing Map; nothing changes until you accept it
- Mix the two — automate the routine dates, keep the final call on the ones that matter
- Logged the same way either way — Automatic · Accepted · Overridden · Manual
One day. One rate level. One screen.
The Pricing Map is the calendar view of your pricing strategy — shared by both engines. Every day in the month carries a single rate-level state (Low / Medium / High / Peak), visible at a glance and color-coded. The platform recommends one based on the active engine; you accept or override. Automatically saved or accepted changes are sent through the supported channel-manager connection, and the delivery result is logged.
- Basic — one global pricing group, day-class chosen from the same rate levels
- Group-based — multiple seasonal groups, each with its own rate-level set
- Time Machine — see the Pricing Map three weeks ago, with the projected day-class
- Engine-independent — the same screen works whether Matrix or Zone is active
One pricing decision. Every supported channel-manager route.
When you accept a rate, Peaqplus sends it through the supported channel-manager connection. Your existing distribution setup determines which connected channels receive it. Channel groups ("Free Sale," "Corporate," "Cancellation Strict") let one decision affect several mapped routes while another group stays unchanged.
Every send is logged — the exact rate, the mapped route, success or failure, the date and the user behind the change.
- Rate per room type, per rate type, per day
- Stay restrictions: minimum stay, no-arrival, no-departure, closed
- Channel pool open/close — one click controls which OTAs sell which days
- Optional: inventory updates (off by default; opt-in)
Every rate, traceable to a decision.
On every saved rate, Peaqplus logs how the decision was made. Four states, color-coded.
Auto-pricing accepted the rule's suggestion. No human in the loop — because the rule was set up to handle this case.
A human looked at the suggestion and accepted it as-is.
A human picked a different rate that was still inside the rule's options.
A human chose a rate outside the rule entirely. Maximum override.
When the owner asks "why did we drop weekend rates in March?", the answer is one click away. When you re-tune the matrix at year-end, you can see how often the rules fired clean vs. how often they got overridden — and why. The override pattern is the data; the data tunes the matrix.
Clone last year's strategy. Validate every gap.
At year-end, clone any pricing group to a new date range — last year's High Season becomes this year's High Season, in one click. Adjust where needed. Save.
The coverage validator checks every day of the year. Two pricing groups overlapping? Flagged. A holiday-event uncovered? Flagged. A weekend with no day-of-week rate set? Flagged. The errors are visible before you publish, not after.
Add Pricing to BI Core for €49/month per property.
Pricing & Rate Management is also included in Growth, which starts at €236/month for properties with up to 49 rooms. The à la carte module is €49/month on top of BI Core. Its one-time €135 setup includes 1 hour of team training. Prices are net of VAT; yearly billing receives a 10% discount.
Compare bundles and à la carte pricing →What hotel teams ask before they automate rates.
Clear answers on automation, channel-manager delivery, competitor data and pricing.
Hotel dynamic pricing software recommends or automatically updates room rates as demand signals change. Peaqplus uses explicit rules, guardrails and an audit trail, so your team can see what changed, why it changed and whether the decision was automatic or manual.
Yes. With auto-pricing enabled, Peaqplus can save the engine result and send it through a supported channel-manager connection. In advisory mode, it only shows the recommendation and makes no rate change until a user accepts it. You can use both modes on different dates.
Yes. The optional competitor floor in Zone Pricing requires Competitor Rate Intelligence. Without that module, Zone Pricing still works from your own occupancy, pickup, lead-time rules, floor and ceiling.
Pricing & Rate Management is €49/month per property on top of BI Core, or included in Growth from €236/month for properties with up to 49 rooms. Its one-time €135 setup includes 1 hour of team training. Prices are net of VAT; yearly billing receives a 10% discount.
See both engines in action.
In our 45–60 minute walkthrough, we run Peaqplus on our live demo environment — a simulated property with data that moves day to day — set up a sample pricing group on the Matrix engine, then switch into Zone mode and walk through a delta-based recalculation: same calendar, same channel push, same audit trail. You see which engine fits how you actually run.
The demo is free and needs no PMS access. Pricing setup is a one-time €135 and includes 1 hour of team training.