Rate Fences Without Crossing Parity Rules

A rate fence is a condition, not a discount. Get that backwards and the most effective tool in revenue management becomes a parity complaint.

Last updated: September 25, 2026

A rate fence is a condition on who can buy a night, not a reduction in what the night costs. Get those two confused and the sharpest tool in revenue management turns into a parity complaint. This guide sets out the four things a fence can restrict. It shows where a fence slides into a discount, and why disputes begin exactly there. Then it gives three combinations that usually stay on the right side of the line, and walks how to withdraw a fence without stranding the bookings it made.

One boundary up front, because it governs everything below. Parity rules — what a platform requires you to keep equal, across which channels, with what exceptions — are set by each platform's own current terms, and they differ by platform and market. Nothing here describes a rule. It describes the shape of the distinction, and the terms are yours to read.

Key Takeaways

• A fence changes eligibility, not price. It decides who may buy, not what they pay.
• Four things it can restrict. Length of stay, booking window, channel, and cancellation terms.
• The line is the identical stay. Same dates, same unit, same conditions, lower price — that's a discount.
• Three combinations hold up. Minimum stays, booking windows and cancellation tiers, used as products.
• Withdraw it slowly. A fence removed at once strands the bookings it already made.

What a fence actually restricts: length of stay, booking window, channel or cancellation

A fence works by making a rate unavailable to someone who'd otherwise buy it. Nothing about that requires a lower number anywhere. Four levers do the work, and each one is a condition attached to a rate plan rather than a change to the rate itself.

Length of stay. A two-night minimum on Friday and Saturday, a seven-night tier for the monthly guest, a three-night rule over a public holiday. The nightly figure doesn't move. What moves is which bookings are possible at all.

Booking window. How far ahead or how close to arrival a rate can be bought. A rate open only to bookings made within days of arrival, or only to ones made well ahead, is a different product from the same rate with no window — and you don't have to cut the price to say so.

Channel. Availability or a plan offered on one channel and not another. This lever most often turns into a parity problem, and it's the one to check against each platform's current terms.

Cancellation terms. A non-refundable rate and a flexible one are different products at different prices, the way a refundable ticket and a restricted one are. Whether a channel lets you carry both, and how it displays them, is set by that channel's terms rather than by convention.

The test for whether something is a fence is short. Take the guest who qualifies and the one who doesn't, and ask if they're being sold the same thing. If they're sold different products, you have a fence. If they're sold the same product at two prices, you have a discount wearing a fence's clothes.

Where a fence crosses into a discount, and why that is where parity disputes start

The slide happens when a condition stops being a real condition.

Suppose you attach a rate to "bookings made through your own site". If everyone can book there, the condition isn't restricting anyone — it's a route to a lower price that any guest can take. Meanwhile the same night is listed higher elsewhere. Same dates, same unit, same conditions, two prices, separated only by where the guest clicked. That's not a fence. That's a price difference, and it's precisely what parity rules exist to catch.

The same slide happens with conditions that are trivially satisfiable. A "members" rate anyone can join in ten seconds. A promo code published beside the listing. A length-of-stay discount so shallow it doesn't change behaviour — it doesn't create a different product, it just lowers the number.

Why disputes start here rather than anywhere else: parity is checked by comparison, not by intention. Nobody reads your rate plan and asks what you meant. A channel compares the price of an identical stay across what it can see, and a difference is a difference regardless of the condition attached to it. If the condition doesn't produce a genuinely different product, the comparison finds a gap, and you're the one who has to explain it.

So before you add a fence, write one sentence on what the guest must do or give up to qualify. If you can't write it, or the answer is "nothing", you've built a discount.

There's a second failure mode worth naming. Discounts stack with fences in ways that widen the gap beyond what you intended: a length-of-stay discount on a plan that also carries a channel adjustment produces a number you didn't design. Compute the effective price for the shortest stay the plan allows, and compare it across channels before assuming the fence does what you think.

The three combinations that work without being advertised as a cheaper rate

Three combinations tend to hold up, because in each case the guest is buying something genuinely different rather than the same thing for less.

Minimum stay plus day of week. A two-night minimum on Friday and Saturday, with one-night stays open Sunday to Tuesday. Nothing about the nightly figure changes. You've changed which bookings exist, and the guest who books two nights is buying two nights — a different product from the one-night guest, not a discount on it. It's also the cheapest fence you have.

Booking window as inventory. A rate open only inside a short window before arrival, or only to bookings made far ahead. Same unit, same nightly figure, different availability. The guest booking two days out and the one booking three months out are buying at different moments under different terms, which is a real distinction in every travel market. Keep the nightly figure identical and let the window do the work.

Cancellation tiers. A stricter cancellation policy attached to its own rate is a separate product, and it's the one guests understand best, because every airline sells it. Whether a given channel lets you carry more than one policy, and how it shows them side by side, is set by that channel's current terms. Check before you build it. A tier the channel can't display becomes an unexplained price gap.

What all three have in common: what changes is the product or the availability, not the number. You can describe each in one sentence without mentioning a lower price — a decent working test. If the sentence needs "cheaper", you're over the line.

And the practical check afterwards: look at what the channels actually show. The source price and source status for every connected channel sit on one calendar at localsbnb.com, which is where an unintended gap between two channels becomes visible before a guest or a channel notices it first.

How to withdraw a fence without stranding the bookings it already produced

Fences are easier to put up than to take down, and the damage lands on bookings that already exist.

Grandfather what's sold. A booking taken under a two-night minimum keeps its terms when the minimum comes off. Removing a restriction shouldn't rewrite a reservation — check the bookings in the affected window before you change anything, and confirm none of them depend on the rule you're about to delete.

Retire the plan, don't edit it into something else. If a fence lives on its own rate plan, close that plan to new bookings and leave it for the stays already on it. Editing the plan under existing reservations is how a guest arrives to find their rate quietly changed.

Sequence the channels. Pull the fence from one channel, confirm what it displays, then move to the next. Doing four at once means four chances to produce a gap you didn't intend, and no clean way to tell which change caused it.

Watch the orphan. A plan whose only distinguishing feature was the fence becomes an undifferentiated second plan once it goes. Either delete it or give it a purpose, because two identical plans on one unit is how the next decision gets made against the wrong one.

Then measure. Occupancy, ADR and RevPAR on the affected nights, before and after, over a comparable window. A fence carrying weight shows up as a change in which nights sell, not only in what they fetch. If nothing moved, it wasn't doing anything, and you've learned that too.

FAQ

Is a minimum stay a discount?

No, and that's the cleanest example in this whole area. It changes which bookings can exist without changing what any of them costs. A weekly discount on the same plan is a different thing entirely — that one does move the number, and it's the one that needs checking against your floor.

Can I offer a lower rate on my own site than on the channels?

Whether you can, and what counts as your own site for that purpose, is set by each platform's current terms and by local law in some markets. Read the terms for every channel you sell on before you do it, because they don't all say the same thing.

What should I do if a channel tells me I've broken parity?

Find the comparison first: which identical stay was priced differently across what it can see, and whether your condition produced a genuinely different product. Being able to show the condition is the whole defence; saying you didn't mean it isn't one.

A fence is a condition, and the moment it stops being one it becomes a price gap a channel can find without knowing anything about your intentions. Describe what the guest must do or give up, keep the nightly figure out of it, and check what each channel displays rather than what you meant to send. Two identical plans on one unit is the failure that follows a badly withdrawn fence — and the calendar at localsbnb.com is where both turn up.

---

Parity requirements, channel terms and local rules differ by platform, market and date, and change over time; read every one from that platform's own current terms. This article is general guidance for hosts and isn't legal or platform policy advice.