The host problem
A cancellation reopens dates. The host has to reprice, but the original booking may have happened weeks or months earlier. The old price belongs to the old lead-time window.
The host needs a sequence, not a mood.
The number, concept, or decision
Repricing after a cancellation starts with BLT.
BLT equals Check-in Date minus Booking Date. After a cancellation, use the days remaining between the cancellation date and the original check-in date to understand the new demand pool.
Keep cancellation metrics separate from live KPI metrics. Do not merge canceled revenue into live accommodation revenue. Do not count canceled nights as booked nights. Track cancellation recovery in its own ledger.
Then move through four windows.
At 60+ days, treat the reopened inventory like forward inventory. Do not cut automatically. Match current comparable open inventory, check event context, and preserve rate unless the calendar shows rejection.
At 30 to 60 days, hold if demand signals remain neutral. If the cancellation created an awkward gap, adjust minimum stay before cutting rate.
At 15 to 30 days, check pickup slope. This window often gives the best chance to balance night recovery and revenue quality. Make targeted changes to weak day types first.
At 0 to 14 days, prioritize absorption on exposed midweek, orphan, and shoulder nights. Protect strong weekends unless the weekend itself shows rejection.
What this helps you decide
This sequence helps you decide whether to hold, cut, reshape, or wait after a cancellation.
It also helps you decide whether recovery should focus first on nights or revenue. Late-cycle orphan gaps often need night recovery. Event-supported windows may still support revenue recovery.
Example
A four-night reservation cancels 38 days before check-in. The reopened block runs Wednesday through Sunday.
The host checks lead time first. At 38 days, the block sits in the 30 to 60 day regime. That does not call for panic.
The host checks gap shape next. Wednesday may weaken the booking shape, but Thursday through Sunday could still pull a four-night stay. The host keeps Friday and Saturday near the prior event-adjusted rate, prices Thursday as a shoulder-night lever, and keeps Wednesday lower to make the full stay work.
At 21 days, if no replacement booking arrives, the host reviews again. The host may loosen minimum stay or lower Wednesday and Thursday first. Friday and Saturday receive cuts only if weekend demand shows rejection.
What most hosts get wrong
Most hosts reprice every canceled night as if all reopened dates carry the same risk. They do not.
A reopened Saturday at 35 days may still support rate. A reopened Wednesday at 6 days may need absorption. A reopened Thursday attached to a weekend may need shape logic more than a price cut.
The second mistake is using the canceled booking’s ANR as the new target without checking whether the current lead-time window still supports it.
What to do this week
Create a cancellation repricing note with four rows: 60+ days, 30 to 60 days, 15 to 30 days, and 0 to 14 days.
For each row, write the default move: hold, watch, reshape, or absorb.
Then add one exception for event windows: do not cut automatically when event demand still exists.
Use this note the next time a cancellation reopens inventory.
Where this fits in the STR Signals framework
This page sits between the cancellation concept and reopened-inventory strategy. It teaches the repricing order. Reopened-inventory strategy then handles gap shape, adjacency, and minimum-stay mechanics.