A Discount Policy You Can Explain to a Guest

If you can't explain a discount in one sentence, you'll end up arguing about it in a message thread at eleven at night.

Last updated: October 1, 2026

Most discount problems aren't about money. They're about the fact that no rule was ever written down, so every request becomes a fresh negotiation and every answer has to be invented in the moment. A policy you can state in one sentence, with its exceptions named in advance, ends that. It doesn't matter what the number is. It matters that you can say what it is, when it applies, and where the guest can read it.

Key Takeaways

• One sentence, or it isn't a policy. If the rule needs a paragraph, it's a negotiation with a longer memory.
• Name the exceptions in advance. Unnamed exceptions become the argument, because both sides invent them at the same time.
• Three types cover most cases. Longer stays, filling specific gaps, and returning guests do different jobs.
• Write it where a guest reads it. A rule that only exists in your head gets tested on every request.
• Decide once how you'll answer a request that falls outside. The answer is a sentence, not a decision.

The test: one sentence, no exceptions you can't name

Before anything else, try to state your discount policy out loud in one sentence. Not a list, not a table, not a range. One sentence.

If you can, you have a policy. If you find yourself adding "unless", "depending on" or "except in peak season", you've found the part that will cause the argument later. That's useful information, and it's better found now than at eleven at night.

The test works because of what it measures. A rule you can say in one sentence is a rule you can repeat identically in a message, apply to a booking you didn't expect, and hand to a co-host. A rule that only lives in your judgement gets re-derived every time, slightly differently, and the guest on the other end can feel it.

Then name the exceptions. Every policy has them, and hiding them doesn't remove them; it just means they get argued about case by case. Write them into the same sentence, or keep them as a short, fixed list beside it. Peak dates, a minimum stay that has to be met, a booking that's already discounted — whatever yours are, they should be answerable without hesitation.

One more discipline: separate the discount from the reason. "A reduction for a longer stay" is a rule. "A reduction because the guest asked nicely" isn't one, however reasonable it feels in the moment.

Three discount types, and what each one is really for

Almost every discount a host offers falls into one of three groups, and they exist for different reasons. Mixing them is where policies get muddy.

Length of stay. This rewards the thing that actually lowers your cost per booking: fewer arrivals, fewer messages, fewer turnovers for the same number of nights. The rate you set is yours to choose, and so is the threshold. What matters is that both are fixed and stated, so the answer to "what about a longer stay" is the same every time it's asked.

Filling a specific gap. A gap in your calendar is worth less than a night inside a full week, and a discount aimed at one narrow window is a decision about that window rather than a permanent price cut. The trap is leaving it switched on. A gap-filling rule that never expires becomes your new base rate, and you've paid for it with no extra nights sold.

Returning guests. This one buys something different: a guest who already knows the flat and needs no onboarding. It's a relationship discount, so it belongs tied to the guest rather than to a season, and it's the type most likely to be requested and least likely to be worth giving away to somebody who has never stayed.

Notice what's missing: none of the three is "because the request was persistent". If a discount isn't doing one of these jobs, it's not a policy, it's a one-off, and one-offs are fine as long as you know that's what you're doing.

It's worth saying that a public, two-tier price is easier to explain than a hidden one. LOCALSBNB's own pricing is a two-tier public figure, billed annually or monthly per room, and the reason that's easy to communicate is that there's nothing to uncover. A discount policy benefits from the same property: whatever your rule is, a guest should be able to read it before they ask.

Writing the rule down where the guest can see it

A discount that only exists in your head gets tested on every request. A discount written where a guest can read it answers most of those requests before they arrive.

Put it in the listing itself, in plain words, near the pricing detail a guest is already reading. Not in a footnote, not in a house manual that arrives after booking, not in your reply template. If the rule matters at the moment of deciding, it belongs at the moment of deciding.

Keep the wording short and literal. "Stays of a week or more are priced lower" is a rule a guest can act on. "Discounts available for longer stays" is an invitation to ask, and asking is exactly what you were trying to reduce.

Then make sure the channels agree. Your calendar shows the source price and the source status for each connected channel, so a discount expressed as a rate rule can be compared against what each channel is actually offering. If your rule lives in the listing text but the rate on a channel doesn't match it, a guest will find the contradiction and quote it back to you.

And keep one version of the wording. A discount described three ways across four channels isn't a policy, it's three policies, and the guest will reasonably pick the most generous one.

Handling the request that falls outside the policy

Somebody will ask for something your rule doesn't cover. What matters isn't the answer; it's that deciding it doesn't take an hour of internal negotiation.

Have a default. It can be a polite no, it can be a small named concession, and it can be a referral to the published rule — all three work. What doesn't work is deciding from scratch each time, because that's how a single exception becomes an expectation.

Answer with the rule, not with your feelings about the request. "Stays of a week or more are priced lower, and that's already applied to these dates" closes the topic. "I'd love to, but money is tight this month" opens it, and invites a counter-offer.

If you do say yes, say yes once and in writing. An exception granted by message becomes part of the record, and a guest who got one last time will ask again. That's not a reason to refuse; it's a reason to note the exception, so this year's answer matches last year's.

And when the same request arrives for the third time, treat it as information. Three identical requests mean your published rule isn't answering the question people actually have, and the fix is to rewrite the rule rather than to keep negotiating around it. localsbnb.com keeps each listing's rates and availability in one calendar with the source price and source status visible per connected channel, which is what lets you check that a stated rule and the live rate still agree.

FAQ

Do I need a discount policy at all?

Only if guests ask for reductions. Once they do, a written rule is cheaper than deciding each case on its own, because it removes the negotiation rather than winning it. If nobody asks, you have the simplest policy there is.

Should I put the exact figure in the listing?

Put the rule and its threshold in plain words, and keep the figures consistent everywhere they appear. What guests need is to know whether they qualify and how to find out, rather than a private arrangement they have to request.

What if a guest asks for a discount I've never offered?

Answer with the published rule and stop there. If you choose to make an exception, make it once, in writing, and note it — so the next request gets the same answer rather than a new negotiation.

A discount policy is a sentence, a short list of named exceptions, and a place a guest can read both. Get those three right and the eleven-at-night message thread mostly stops happening. localsbnb.com shows your rates alongside each connected channel's source price and source status, so the rule you publish and the price a guest sees can be checked against each other at a glance.

---

This article is general guidance for hosts rather than tax or legal advice. Rules on pricing, fees and how they must be displayed differ by country and by platform, and they change over time; check the current requirements of your local authority and the current terms of each platform you sell on.