Rate fences and restrictions — beyond the BAR

In lesson 7 we introduced rate fences — legitimate ways to sell the same room at different price points alongside the rate-parity rule. In lesson 11 (Length of stay) we opened the MLOS, CTA, CTD restrictions. In lesson 13 (BAR and the rate structure) we saw Hotel Peaqplus City’s 22 rate plans.

Now we cover the master-level handling: how do we combine these tools at a concrete daily level? When do we deploy each? How do we avoid the over-complication trap?

Rate fences and restrictions are a fine-tuning system — the more control levers we have, the more precisely we can dial in the balance between demand and capacity. But they’re equally dangerous — an overly complex system is opaque, and the mistakes are noticed late.

Rate fences vs. restrictions — the two categories

A couple of clarifications:

• Rate fences = guest-condition price differences. Who are you? (registered user, business traveller, group member). The 6 main rate fences introduced in lesson 7.
• Restrictions = booking-condition limits. What are you booking? (how many nights, when you arrive, when you depart).

The two concepts overlap but rest on different logic. A mature RM applies both in parallel.

The 6 main rate fences — now the strategic use

In lesson 7 we looked at what these fences are. Now at when and why we deploy them.

1. Member rate — growing the direct channel

Strategic goal: steering guests from the OTAs to your own website. In lesson 22 we saw: raising the direct share by +5 pp is a ~EUR 15,000 annual commission saving.

When to activate: always. The member rate is a continuous campaign — not seasonal. Hotel Peaqplus City runs the member rate 365 days a year and actively encourages user registration (email campaigns, social media, a loyalty program).

2. Non-refundable rate — reducing cancellation risk

We covered it in detail in lesson 23: the non-refundable rate cuts the cancellation rate from 18% to 5%, in exchange for a 15-20% discount.

When to activate: on high-cancellation-risk periods — Saturday nights, long-booking-window dates (60+ days out), and seasons with many competitors in the market (the guest hesitates a lot).

When to switch off: on event-peak days (a festival, a Coldplay concert), where demand is high anyway. Here the non-refundable rate only lowers the ADR for high-paying guests. Not needed.

3. Advance purchase rate — accelerating pace

Strategic goal: speeding up the pickup during the booking window. A 21- or 45-day advance purchase rate uses a discount to encourage booking ahead.

When to activate: for days where the pace is slow early in the booking window — e.g. low-season weekdays where you stand at only 15% 60 days out.

When to switch off: if the pace is naturally fast (an event peak, a high-demand season). Here the discount is just needless ADR erosion.

4. Package rate — raising ADR and TRevPAR

Strategic goal: in lesson 4 (RevPAR vs. TRevPAR) we saw — we target the higher-TRevPAR segments. Packages are bundled pricing, which feels like more transparent value to the guest.

When to activate: on seasonal peaks (Valentine’s Day, Advent, birthday season), targeted at the occasion-guest segment.

When to switch off: only when capacity has genuinely sold out. A package always brings a higher ADR and TRevPAR than plain BAR.

5. Mobile-only rate — a Booking ranking bonus

Strategic goal: in lesson 7 we saw — Booking.com gives a ranking bonus to hotels running mobile deals.

When to activate: on low-pace periods, where the mobile-booking segment can make quick decisions (impulsive leisure travellers).

When to switch off: on event-peak days. The Booking ranking bonus is worthless if you’re full anyway.

6. Corporate / negotiated rate — the contractual relationship

Strategic goal: securing stable corporate volume. In lesson 8 we saw: the corporate segment is low price-sensitivity, short booking window, predictable volume.

When to switch off: on high-pickup peak days. If transient pickup is already high for a given Saturday, the corporate rate can be closed out (the corporate guest doesn’t book, or pays BAR).

Restrictions — capacity steering

Now the restrictions category. These are booking-condition limits that block certain booking patterns on a given day.

MLOS (Minimum Length of Stay)

What it does: accepts only the specified minimum nights or longer. E.g. MLOS = 3 → only 3+ night bookings can come in.

When to use:

• On event-peak days (a festival, New Year’s Eve, a Coldplay concert), where the one-to-two-night “skimmers” pay the high ADR but don’t help fill the surrounding low-season days. MLOS forces them to take more nights or go elsewhere.
• On holiday-peak weeks (Advent, Easter), where the guest stays longer anyway, and MLOS only filters out the cancellation noise from marginal short stays.

When NOT to use:

• On general weekdays — here MLOS causes lost bookings. A corporate one-night booker won’t stay 2 nights just to fit.
• On low-pace dates — here we accept every booking, no MLOS.

CTA (Closed to Arrival)

What it does: on the given day we accept no arrivals — only guests already in house.

When to use: to combine the event-peak days with the surrounding days. E.g. CTA on the festival Friday = the guest can’t arrive Friday; instead they arrive Thursday or Wednesday and are already in house on Friday. This also sells the adjacent days (Thursday, Wednesday).

When NOT to use: a standalone day’s MLOS is often better. CTA is a strong hand — used wrong, you let go of demand.

CTD (Closed to Departure)

What it does: on the given day we accept no departures. The guest can’t go home that day, only afterward.

When to use: less often than MLOS and CTA. A typical case: CTD on a conference’s Tuesday = the guest can’t go home on Tuesday, only Wednesday or later. This preserves the coherence of conference bookings — the hotel doesn’t want guests to “skip” the rest of the week mid-conference.

Combining the 3 restrictions

The three restrictions work together in capacity steering:

A mature RM sets these at the daily level — the Peaqplus Pricing Engine module pushes the restrictions too through the Channel Manager to all channels.

The effect of restrictions by segment

Restrictions don’t affect segments equally:

• Transient business: MLOS and CTA dramatically reduce the business pickup, because corporate travel is short and inflexible. A 2-night MLOS = the corporate traveller goes to another hotel.
• Transient leisure: MLOS is less sensitive — the leisure guest stays longer anyway.
• Transient occasion: MLOS is natural in the segment — a honeymoon is 3-5 nights anyway.
• Group: restrictions generally don’t apply to them — the group contract overrides the standard restrictions.

A mature RM designs the restrictions so the desired segment mix emerges. E.g. on an event-peak day MLOS = 3 → only the higher-paying, longer-staying guests get in; the corporate one-night “skimmers” are automatically squeezed out.

The over-complication trap

Restrictions and rate fences are powerful tools, but dangerous. The downsides of an over-complicated system:

1. Channel Manager sync problems

Every restriction rule goes through all 8-15 channels. A CHM mapping error = the restriction doesn’t take effect on one channel, and different guests get in than planned. In lesson 6 (CHM) we saw: the monthly audit is critical.

2. Guest dissatisfaction

A guest who wants to book one night but MLOS = 2 gets an annoying error message on the OTA. The brand experience leaves a bad impression.

3. The RM team’s habit trap

A mature RM team develops fixed restriction patterns — e.g. “always MLOS = 2 on Saturday nights.” On a given day that can be wrong if the pace is slow. But the team sets it automatically, because “we always do it this way.” The flexibility is lost.

4. Forecast noise

If restrictions are active too long, the historical pace curve gets distorted — next year the same day gives a bad forecast (because the past pace was already constrained).

A good RM minimizes the number of restriction rules — applies only the genuinely necessary ones, and reviews them regularly.

The Peaqplus Pricing Engine — restriction automation

The Peaqplus Pricing Engine module handles both the rate fences and the restrictions:

• Daily BAR, member rate, non-refundable, advance purchase pricing — per the rate structure introduced in lesson 13.
• Daily-level MLOS, CTA, CTD setting — the Pricing Engine gives a suggestion based on the calibrated forecast model, and the RM reviews and activates it.
• Through the Channel Manager, automatic distribution to every channel.
• Anomaly flagging — if an active restriction dramatically reduces pickup, Peaqplus flags it (maybe we’re being too strict).

A concrete daily situation: the Peaqplus Pricing Engine suggests that for the November 18 (Coldplay) Saturday night, MLOS = 2, BAR = EUR 148, and the non-refundable rate closed out. Daniel sets it on the screen in 3 clicks, and the change goes live on every channel within 15 minutes.

In lessons 35-36 (Dynamic pricing) we cover how Peaqplus computes the suggestions — those at the advanced level in more detail.

Key takeaways

• Rate fences = guest conditions (member, non-refundable, package, mobile, corporate). Restrictions = booking conditions (MLOS, CTA, CTD). The two work in parallel.
• The 6 main rate fences serve different strategic goals — member rate (grow direct), non-refundable (cut cancellation), advance purchase (accelerate pace), package (TRevPAR), mobile-only (Booking ranking), corporate (contractual).
• MLOS, CTA, CTD restrictions are capacity-steering tools — on event-peak days, for conference coherence, for booking-pattern steering.
• Restrictions don’t affect segments equally — corporate “skimmers” are easily squeezed out, the leisure occasion is naturally 3+ nights.
• Over-complication is dangerous — CHM sync errors, guest dissatisfaction, forecast noise. A mature RM minimizes the number of rules.