See every pricing date.
Act from one calendar.

Scan pickup, occupancy, forecast and the active pricing result together; filter the period and focus on exceptions instead of opening every date.

Open the rate history to review the saved price, decision mode and what happened in bookings afterwards — without treating correlation as proof of cause.

Stage rates and supported restrictions in the Pricing Cart, check the old and new values, then send the approved batch through the supported connection.

One date, with the context needed to decide.

Pricing work often starts with a date and then spreads across the PMS, forecast, market data and distribution tools. Pricing Calendar puts the available signals beside the rate decision, one row per date.

Review the active engine result, accept it, override it or leave the date unchanged. Approved changes collect in the Pricing Cart and are sent only through a supported, configured channel-manager connection.

The pricing decision first. Optional signals when available.

The core row shows the date, on-the-books position, pickup, committed forecast, current rate and the active engine result. Event markers come from the Event Calendar, which is included in BI Core.

Booking-engine search data needs a supported booking-engine connection. Alert badges require Ping. Competitor rates require Competitor Rate Intelligence. The row shows only the context available for your hotel, so an optional signal is never presented as a core entitlement.

Review the decision and what followed.

Open a check-in date and look back 30, 60 or 90 days. The history view places saved rates, incoming room nights and ADR on the same timeline, while rate-change markers show when the team or engine acted.

The chart helps the team ask a better question: after we changed the rate, how did pickup develop? It preserves the sequence for review, but it does not claim that the rate change alone caused the booking outcome.

The auto-pricing engine accepted the suggestion and saved it. 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. The rule fired clean.

A human picked a different price that was still inside the rule's options. Partial override.

A human chose a price outside the rule entirely. Maximum override — flagged as a tuning signal.

Update a date range without losing the review step.

When the same decision applies to several weekends or a wider date range, filter and select the relevant rows instead of editing each date separately.

The wizard narrows the room-type and rate-type pairs, applies the chosen rates or supported restrictions, then places the batch in the cart. An “Accept all suggested prices” action covers the simple case while preserving the final review.

Check the batch before it reaches distribution.

Manual changes collect in a cart drawer instead of being sent immediately. Review the old and new values, remove individual entries, then approve the batch when it matches the intended strategy.

The save writes the supported actions to the audit trail and sends them through the configured channel-manager connection. Availability of inventory, channel-pool and restriction actions depends on that connection.

On-the-books position and change over time from the hotel’s dated snapshot history.

The forecast version the team has committed for that date.

The latest saved rate beside the result of the active Zone or Matrix engine.

Event Calendar context is included in BI Core; triggered alert badges require Ping.

Search context appears when a supported booking-engine data connection is active.

Observed public-market rates appear when Competitor Rate Intelligence is active.

A hotel rate calendar is a date-by-date workspace for reviewing current and recommended room rates alongside the context behind them. In Peaqplus, Pricing Calendar also lets the team approve, override, batch and review pricing decisions from the same workflow.

No. Pricing Calendar is included with Pricing & Rate Management. Add Pricing to BI Core for €49/month per property, or use it as part of Growth, which starts at €236/month for properties with up to 49 rooms.

Core pricing and BI context includes the current rate, active engine result, occupancy, pickup and committed forecast. Event markers come from the Event Calendar in BI Core. Booking-engine demand needs a supported data connection, alert badges require Ping, and competitor rates require Competitor Rate Intelligence.

It can send approved or automatically saved rates through a supported, configured channel-manager connection. Your existing distribution mapping determines which connected routes receive the change, and the delivery result is logged.

Yes. Manual and bulk changes collect in the Pricing Cart, where the team can compare old and new values, remove individual entries and approve the batch. Available inventory, restriction and channel-pool actions depend on the configured connection.