What to Do When a Short-Term Rental Reservation Cancels

A reservation cancellation arrives and there are usually two bad responses: ignore it and assume the PMS handles everything, or spend two hours repricing every channel before dealing with anything downstream. Neither works well.

The cancellation is already done. What matters now is a short, sequenced response that gets the calendar, the team, and the books all updated before the open window starts costing time.

The first four hours: operational cleanup

Your PMS updated the booking status and reopened the dates. That part is automatic. What doesn't update automatically is anything that was scheduled off the back of that booking.

Check for queued guest messages. If you use automated messaging, a pre-arrival sequence probably fired or is about to fire. Most PMS platforms cancel those when a booking cancels, but it's worth confirming that nothing is sitting in a pending outbox. A "Your door code is ready" message going to a guest who isn't coming is confusing on their end and embarrassing on yours.

Cancel any vendor commitments. Pool heat-ups, cleaning slots, inspection appointments. If a cleaner is booked for checkout day, they need to hear from you before they show up. A cleaner who turns up to an empty calendar slot isn't a small thing. In markets where reliable cleaning crews are limited, burning that crew's time is a relationship cost.

If you work with a team, flag the cancellation in your shared inbox so nobody wastes time composing a response to what looks like an open guest thread. Teams that run multiple properties will occasionally draft a reply to the previous guest's thread out of habit. A quick note saves everyone 10 minutes of confusion.

Pricing the open window

The more useful question before repricing isn't "what price should I set?" It's "how quickly do I need to decide?"

A window that opened 90 days from now has some runway. You can watch demand for a week before adjusting. A window that opens 10 days out is a different problem. Every day it sits at standard pricing with no signal on demand is a day the window gets smaller.

For an opening filling in the next two weeks, a 10 to 15% reduction from your standard rate is a reasonable first move. You can raise it back if demand comes in fast. OTA search algorithms reward fresh listing updates, so repricing immediately has a secondary benefit beyond the number itself.

If you have repeat guests who might want those specific dates, a brief personal note about the opening can work. Not a mass email. One or two people whose stays you remember and whose travel patterns might fit. The direct booking post covers building that relationship over time.

Whether to reduce the minimum stay

This is worth thinking through before acting.

The cancelled booking was probably 3 to 7 nights. If your standard minimum is 3 nights, the same window will attract similar bookings at the right price. But if your minimum is 4 nights and the opening is 5, dropping to 3 might draw in a broader audience.

Before reducing the minimum, account for the turnover cost. If a 2-night booking fills the first part of the window and a 3-night booking fills the second, you're doing two cleanings where one would have done it. In properties with high cleaning fees or tight schedules, two short bookings can net less than one longer one at a slight discount.

The gap nights post covers minimum-stay math in more detail, for cases where the open window is smaller and the economics are tighter.

What happens to the money

This is where many operators take a shortcut that causes problems later.

If you'd counted the cancelled reservation in your projected revenue (and most operators do, once a booking is confirmed), the cancellation creates a gap between what you projected and what will land in your bank account.

What the guest gets refunded depends on when they cancelled and what policy they booked under. A flexible cancellation a month out usually means a full refund, which means nothing reaches you. A strict cancellation a week before arrival might mean you keep some portion. The OTA handles the refund mechanics correctly. Your internal records need to catch up.

Log the cancellation as a revenue reversal when it happens, not at month-end. A reservation that cancels on August 10th and gets reconciled on August 31st creates 20 days of confusion in your projected vs. actual revenue, which matters if anyone is tracking the portfolio week by week.

If the booking had add-ons tied to it (pool heat, early check-in), check whether those have separate refund timelines. A Stripe charge for pool heat that settled before the booking cancelled may have its own refund process through a different channel. The bookkeeping post covers the per-reservation ledger structure for keeping all of this in one place.

How cancellations distort your metrics

A cancellation mid-month makes your occupancy number look wrong in both directions unless you're careful about how you track it.

The number that gets distorted more often is RevPAR: revenue per available night. RevPAR stays clean when you record the revenue collected rather than the booking value at time of confirmation. A cancelled booking with no payout to you should land in your numbers as zero, not as the original booking amount held in "pending."

Two separate figures worth tracking over time: booked nights at the start of each month, and nights occupied at month-end. The gap between them is your cancellation rate in nights. An operator with a consistent 10% gap needs to think about policy settings differently than one with a 2% gap. Both might show similar month-end occupancy if cancelled windows get refilled, but the operational burden is substantially different. The KPI post covers how to track occupancy and RevPAR in a way that surfaces these patterns over time.

The policy question

After a few cancellations, the temptation is to tighten the policy. A strict cancellation policy means more of the original payment stays with you when a guest backs out. It also means guests on the fence choose a more flexible listing instead. The tradeoff is real, and it varies by market, price point, and how heavily your calendar depends on bookings placed months in advance.

Markets with strong last-minute demand (beach towns, ski towns with reliable conditions) can afford a stricter policy because a cancellation creates a fillable window. Markets where most bookings happen 60 to 90 days out, and where last-minute demand is thin, are more exposed to the cost of a cancellation. The policy that makes sense in one market is the wrong call in the other.

Revisit the policy after 6 to 12 months, not after each individual cancellation. A single bad cancellation is noise. A pattern of cancellations at a specific lead time is a signal worth responding to.

One decision worth making before the next one

Most operators handle cancellations reactively. Each one is a small scramble, a few notifications, a manual repricing, a note in the ledger.

After a few cycles, it's worth writing down the actual response sequence. Not a lengthy procedure document. A checklist: who gets notified, what gets cancelled or adjusted in the first four hours, what gets changed in the listing, and how the financial record gets updated. A two-page document with four questions answered in advance turns the next cancellation from a 90-minute scramble into a 20-minute task.

For teams managing multiple properties, a shared version of that checklist matters more. A cancellation that falls through the cracks because the operator who usually handles it was out is a bigger problem than one that gets a slower-than-ideal response.