Airbnb 75/55 Discount Curve: When to Hold Rates and When to Cut

What a 75/55 Discount Curve Is

A discount curve is the planned relationship between time and price. As an unbooked arrival date gets closer, the operator decides whether to hold, test a smaller move, or permit a deeper move. The curve gives those decisions an order.

The 75/55 framework adds two boundaries. First, most calendar nights remain anchored near the target ADR. Second, the deepest part of the curve cannot cross the framework floor. The property cost floor may set an even higher boundary.

The curve is not a promise that lower prices create bookings, a demand forecast, or a substitute for listing quality, availability, minimum-stay settings, reviews, and guest fit. It is one control inside a larger pricing and listing system.

A simple curve has a hold zone, a test zone, and an action zone. The hold zone protects the target. The test zone permits small, evidence-based changes. The action zone permits stronger moves while keeping the effective floor intact.

The shape of the curve should reflect the date. It should not reflect the operator's panic.

Collect the Inputs Before You Draw the Curve

A curve built from generic advice can look precise and still be wrong. Start with the property and the actual dates.

Target ADR and effective floor

Use the 75/55 calculator to record target ADR, the 55% framework floor, the cost floor, and the higher effective floor. Without those values, a discount ladder has no defended anchor or stop line.

Observed booking pace

Review when this listing's nights have booked by date type, separating ordinary weekdays, ordinary weekends, event dates, holidays, and seasonal periods. Do not compress them into one average if their behavior differs.

Current guest choices

Search the live dates as a guest would. Compare relevant available listings, not properties that differ in quality, capacity, or location. Note price, restrictions, cancellation terms, and the offer visible to the guest.

Calendar restrictions

A price cut cannot repair a blocked date, a stay that fails the minimum-night rule, or a booking window that excludes the guest. Check availability before changing the rate.

Event and day context

Mark event dates and high-value dates before applying broad rules. A weak Tuesday and a concert Saturday should not inherit the same move merely because both are unbooked.

Change history

Read the last pricing changes and their observed results. A curve is easier to improve when you know which input moved and what happened next.

Build Three Zones: Hold, Test, and Act

The hold zone

The hold zone covers the broad part of the calendar where the target ADR remains the anchor. An empty date far enough out may be normal. Do not treat every blank square as evidence of a price error.

Hold does not mean ignore. Watch relevant comparable choices, event changes, restrictions, property evidence. The operator can raise or adjust a date when evidence supports it. The key is that aggressive discounting is not the default.

The test zone

The test zone begins when the property evidence justifies a closer look. A small move can test price sensitivity without erasing the anchor. Change one pricing variable when practical. Record the exact dates and expected result.

A test can also be a hold decision. If comparable choices are stronger but your listing has weak photos or a restrictive minimum stay, a price move may not be the best test.

The action zone

The action zone is the limited part of the calendar where deeper last-minute moves are allowed. The effective floor still controls. The curve can stop above it when the date has demand, an event, a weekend premium, or a strong booking pattern.

Do not define the action zone from a borrowed day count. Use the listing's observed booking pace and current evidence. A market where guests decide late may justify a different timing pattern than a market where weekend demand arrives earlier.

Protect the Effective Floor at Every Step

The 55% framework floor is calculated from target ADR. The cost floor is calculated from property economics. Use the higher number as the effective working floor.

Check the final price, not only the first discount. A nightly adjustment, length-of-stay discount, early-bird discount, last-minute discount, promotion, manual override can interact. The field labeled minimum may not be the final guest-facing boundary in every tool path.

Airbnb says rule-set pricing follows a set order. Nightly and weekend pricing is applied first. Stay-length discounts come next. Early-bird and last-minute discounts come after that. Airbnb also says a custom promotion is calculated after the rule-set price (Airbnb rule-set documentation).

That order creates a simple control question: what is the lowest final rate after all active rules? Calculate it before the date enters the action zone.

If the final rate falls below the effective floor, repair the rule stack. Do not lower the floor merely to make the settings pass.

If the cost floor is too high for current demand, the issue may be property economics or market fit. A deeper discount is not a repair when every additional booking loses money.

Separate Weekdays, Weekends, Events, and Gaps

A good curve is not one line across every date. Start with date classes.

Ordinary weekdays

Weekdays may face different guest demand and trip patterns than weekends. Review their own live comparable choices and booking pace. Do not assume they deserve the deepest cut.

Ordinary weekends

Weekends can have a different value to guests. Protect that value when the evidence supports it. A broad last minute rule should not erase a useful weekend premium without review.

Events and holidays

Mark these dates before broad automation. Confirm the event, guest demand, restrictions, available comparable choices. An event label alone does not prove a premium. It does justify separate review.

Orphan gaps

A short gap between bookings may require a different price and minimum-stay decision, diagnose the restriction first. If a two-night gap cannot be booked because the minimum stay is three nights, lowering price does nothing.

New or materially changed listings

A listing without stable property evidence needs a provisional curve and a tighter review loop. Do not fabricate confidence. The new-listing 75/55 guide explains the startup protocol.

Audit Airbnb Rule Sets and Custom Prices

Airbnb's Help Center says a rule set can override existing pricing and availability settings for the dates where it applies. It also documents the order in which several pricing rules are calculated (Airbnb rule-set documentation).

Airbnb's custom pricing page says a custom price for selected nights can override the default nightly price, Smart Pricing, weekend pricing, long-term pricing for those dates. These are platform facts. They do not define the 75/55 method (Airbnb Smart Pricing documentation).

Use an audit table for each date class:

1. Write the base or nightly rate.
2. Apply the relevant weekend or date rule.
3. Apply the relevant stay-length discount.
4. Apply early-bird or last-minute logic.
5. Apply any later promotion described by the platform.
6. Compare the result with the effective floor.
7. Open Airbnb and verify the actual date.

Do not rely on the arithmetic forever. Interfaces and product behavior can change. Read the current official page before a live configuration change. Then verify the result in the calendar.

If you use PriceLabs, read the PriceLabs translation guide. A fixed Date-Specific Override can be an exception to the usual minimum behavior. The tool needs its own precedence audit.

Two Illustrative Discount Curves

The examples below demonstrate the method. They are not universal settings, market data. Performance claims.

Example A: A normal weekend date

Assume a $240 target ADR and a $132 framework floor. The property cost floor is an illustrative $118. The effective floor is $132.

The operator's own records show that relevant weekend demand often appears later than the team once assumed. Far out, the rate holds at the $240 target. In the test zone, the operator permits a small move only if current comparable choices and the property's booking pace support it. In the action zone, the operator may move further but never below $132.

An event is announced for the weekend. The date leaves the ordinary-weekend curve and receives a separate review. The operator does not let the generic last minute rule erase the event evidence.

Example B: A weak midweek gap

Assume a $180 target ADR and a $99 framework floor. The cost floor is an illustrative $108. $108 is the effective floor.

The date sits between two bookings. The team first checks whether the minimum stay allows the gap to sell. It does. The live comparable choices are lower. The team runs a recorded price test. The result stays above $108.

The night remains empty. Before cutting again, the team checks visibility, title, photos, restrictions, and the guest offer. The diagnosis shows the listing is hidden by a check-in restriction on that date. The team repairs availability instead of forcing the rate to the floor.

Use a Hold-or-Cut Decision Tree

The tree protects the operator from using price as the answer to every symptom. A low-booking problem can begin in visibility, conversion, restrictions, market fit. Deeper discounting should be a tested response, not a reflex.

Turn the Curve Into a Calendar Control Table

A curve becomes useful when another operator can apply it without guessing. Write the logic as a small control table before you enter any settings. Each row should name a date class, the evidence that moves the date into a zone, the action allowed in that zone, the effective floor, and the person responsible for checking the final calendar price.

Keep the table descriptive. A row such as "ordinary weekday, weak pace, test zone" is easier to audit than a row called "discount 2." The descriptive label tells the reviewer what the rule was meant to solve. It also makes a mismatch visible when an event date accidentally inherits an ordinary weekday action.

Do not fill every cell with a new percentage. A control table is not a contest to create more rules. Its job is to show the smallest set of decisions that explain the calendar. If two rows always produce the same action and share the same evidence, combine them, if one row contains dates with clearly different demand conditions, split it.

Save the table beside the pricing change log. When the team debates a cut, start with the row and evidence instead of a memory of what happened last season. That practice makes disagreements useful. One person may challenge the date class, another the target ADR, another the restriction state. Each challenge points to a specific input that can be checked.

Check the Guest-Facing Total, Not Only the Nightly Number

The nightly rate is only one part of the choice a guest sees. Length-of-stay rules, cleaning charges, platform fees, taxes, and active promotions can change the total. A nightly rate that looks competitive inside the host calendar may produce a different position at checkout.

Use a repeatable guest search for the exact date class and stay length you are evaluating. Confirm that the listing is available. Note the displayed nightly rate. Inspect the total shown before booking. Do not sign in as a different account to create artificial engagement or manipulate results. The check is an observation of the offer, not an attempt to influence the marketplace.

Compare like with like. A two-night total should not be judged against a seven-night total. A listing with a different bedroom count, cancellation policy, parking offer, or location can still provide context, but it is not a direct substitute. Record the differences beside the numbers so the team does not turn a loose comparison into false precision.

If the final total is unexpected, trace each layer before changing the curve. Confirm the custom nightly price, rule set, promotion, length-of-stay discount, and any connected pricing tool. Airbnb explains that pricing controls can interact. The saved base setting alone is not proof of the guest-facing result (Airbnb rule-set documentation).

The 55% boundary applies to the framework's nightly-rate logic. It does not make every fee or total-price outcome acceptable. The operator still needs to judge whether the complete offer is clear, competitive, and economically viable.

Define Stop Rules Before the First Cut

A discount curve needs conditions for stopping as much as it needs conditions for moving. Without stop rules, an operator can keep lowering the rate because the previous cut did not produce an immediate booking. That sequence creates activity but little learning.

Stop a price test when the next move would cross the effective floor, the date's class has changed, a restriction is discovered, a new promotion changes the stack, or the observation window is too short to interpret. Stop also when the listing receives relevant attention but the guest offer appears to be the stronger problem. At that point, further price movement tests the wrong hypothesis.

A stop does not mean ignoring the night. It means holding the current safe state while the team gathers missing evidence. The next action may be a restriction repair, a listing-quality review, a comparable reset, or a new date-class decision. Record the reason and the next review point.

If a test causes an obviously wrong calendar result, use the saved rollback state, restore the known setting, read the final price again, and trace the conflict. A disciplined rollback is part of the curve, not an admission that the framework failed.

Review the Curve Without Chasing Every Empty Night

Use a fixed review cadence. The exact schedule depends on the operation. The principle is stable: inspect often enough to catch wrong rates, not so often that every empty date causes a new strategy.

At each review, compare expected state with observed state:

• Which dates moved into a new zone?
• Which dates booked, and at what visible nightly rate?
• Which dates received views but no booking?
• Which dates had restrictions or overrides?
• Which final prices approached the effective floor?
• Which event or comparable evidence changed?

Do not change several layers at once. If the curve moves, hold the listing photos, title, restriction logic steady when practical. If the listing changes, note that the curve test is now contaminated.

Archive the prior curve, then record the new curve, affected dates, owner, reason, and next review point. If the new result is obviously wrong, restore the last known good settings and diagnose.

A mature curve becomes simpler, not more ornate. It keeps the date classes and decisions that proved useful. It removes rules that add motion without improving control.

Discount Curve Mistakes to Avoid

Borrowing a universal lead-time ladder

A sample day count is not evidence for your listing. Use observed pace and date context.

Moving every date toward the same floor

Weekends, events, gaps, and ordinary weekdays can deserve different shapes.

Ignoring rule order

The final price may include several platform rules. Calculate and verify the complete stack.

Using the floor as a target

The floor is the boundary. The curve can and often should stop above it.

Changing several variables

A multi-variable change hides the cause of the result. Use bounded tests.

Cutting price before checking availability

A blocked date or incompatible minimum stay cannot be repaired with a cheaper rate.

Run the Curve Check in Plain Steps

Pick one date. Name its date class. Read its rate now. Read the target rate, find the rule floor, find the cost floor. Use the higher floor. Check that the date is open. Check that the stay can fit. Read each rule on that date. Check for an event note, look at close live choices. Write the main cause you want to test. Choose hold, test, or act. Make one small change. Save the old state first. Read the Airbnb rate. Check the full guest cost. Compare the result with the floor. Restore the old state if the result is wrong. Keep the safe state if the test is clean. Name the next review point. Do not add a new move just to feel busy.

Use the same steps for a gap. Start with stay rules. Use them for an event. Start with the event note. Use them for a weekend. Use the right set of live choices. The steps stay simple. The facts can still differ by date. That is the point of the curve.

Write a short curve note

Start the note with the date and its class, add the rate you found, add the target and both floors. List the live rules. State why the date is in its current zone. Name the one move you allow. State the line that will stop the move. End with the next check and the name of the person who owns it.

Keep the note close to the calendar. A new team member should be able to read it and tell why the rate held or moved. If the note needs a long code key, the curve may be too hard to run. Cut rules that do not change a real choice.

Know when the check is done

The check is done when the date has a class, a safe floor, a clear state, and a next step. It is not done when the team has made the rate as low as the tool will allow. A hold can be a sound result. A rule fix can be a sound result. A choice to wait for more facts can also be sound.