A guest's plans change. They want an extra night, their flight moved, one of the four travellers dropped out, or they're bringing the dog after all. You can change any reservation Haven took that has a pricing record in place — a pending request, an approval the guest hasn't paid yet, a paid stay, or a manual booking you created in the manual-booking dialog — dates and guest counts alike. On a paid stay Haven settles the price difference with the guest automatically; on an unpaid one the guest simply pays the new total.
A stay converted from synced dates has no pricing record, so Modify reservation stays hidden. Convert to Direct does not show it. To split that stay, cancel it, then create a direct booking for each date range.
You no longer need to cancel and rebook to change a booking. That old workaround refunded the guest, released their dates to the open market, and made them pay again at whatever your rates are today. Modifying keeps the reservation, keeps its original pricing, and charges or refunds only the difference.
The new stay has to pass the same availability rules as a fresh booking: no overlap with another reservation, your minimum and maximum stay, occupancy, pets, and any check-in or check-out day rules. Advance notice and your booking window only apply to a date that actually moves, so a stay that starts tomorrow, or is already underway, can still be extended or shortened at the other end.
Everything else about the booking stays as it is. To change what the guest pays without changing the stay itself, use Issue refund (after payment) or Adjust price (before payment).
You can also just ask the assistant bar at the bottom of your dashboard or the reservation page — "Move Francesca's stay to the 12th", "Make the Garigue booking three adults", "Add a night to the Kirkwood request". It finds the reservation, shows a card with the old and new total and what happens to the difference, and changes nothing until you click Confirm change.
The guest gets a Reservation updated email with the new dates, party and total, and a line saying what happened to the money — charged to their card, refunded, or still to pay. The same note lands on the reservation thread, and goes out by text too if they've opted into stay texts.
Haven re-prices the stay against the booking's own frozen pricing, not your current settings. The nightly rates, discounts, fees, taxes and cancellation terms the guest agreed to at checkout all still apply. Raising your rates after a booking is confirmed can never retroactively re-price it.
The one exception is nights the booking never covered. An extra night at the end of a stay has no agreed price, so it's priced at your current calendar rate for that date — including any seasonal rate or price override you've since set. The price panel breaks this out per night so you can see exactly what an added night costs before you confirm.
Everything else recomputes off the frozen terms: taxes are recalculated on the new base using the tax rules captured at booking, per-night and per-guest fees re-multiply against the new stay length and party size, and pet fees apply at the rate on the booking.
A pending request or an approved-but-unpaid stay has no payment to settle, so a change is simpler: Haven re-quotes the stay on the terms the guest was given (new nights at today's calendar rate) and the guest pays the new total when they check out.
A booking you entered by hand can be changed too. Haven records the price difference on the reservation, but because it never charged the guest it moves no money — settle the difference with the guest yourself. Everything scheduled around the dates moves as it would for a paid stay.
| Situation | What happens |
|---|---|
| Price goes up and there's a card on file | The difference is charged to the saved card straight away and the change applies immediately |
| Price goes up and there's no usable card | The guest gets a payment link. The reservation does not change until they pay |
| Price goes down | The difference is refunded to the guest's original payment method, and your payout drops by the same amount |
| No price change (infants and children don't price on most listings) | The change applies immediately, no charge, no refund |
Most bookings have no saved card — Haven only keeps one when checkout asked for it, typically for a security deposit hold. So a change that costs the guest more will usually take the payment-link route rather than charging silently. A card that does exist can also decline or ask for 3-D Secure verification, which lands in the same place.
Any increase in price is added to your payout for that booking; any decrease comes out of it. If that booking's payout has already gone out, the difference settles separately rather than amending a payout that's already been released. See Scheduled Payouts.
When the guest needs to pay, Haven emails them the payment link and posts it on the reservation thread, and the reservation shows a Change waiting on the guest card with the pending dates, the party, and the amount owed. Until they pay:
You have two options on that card:
Modify reservation is hidden while a change is pending, so you can't stack a second change on top of one that's about to land. Discard the pending change first if you've changed your mind about what to offer.
On a confirmed stay, changing the dates moves everything scheduled around them:
Changing only the guest counts touches none of that, since the occupancy dates didn't move. Only the calendar and pricing pushes run.
The change isn't offered when:
A booking taken on Haven stays modifiable even when it's been pushed out to a connected PMS, and Haven moves the partner's copy for you where the PMS allows it:
| PMS | What Haven does after you change the dates |
|---|---|
| Guesty | Moves the reservation's dates and guest count automatically (including a pending request Guesty already holds). |
| OwnerRez, Hostfully | Moves the reservation's dates automatically. Neither takes a guest count through its API — if the party changed, you get a task to set it in the PMS. |
| Lodgify, Hospitable | No date-editing API. Haven updates the availability calendar and gives you a dashboard task (and an email) with a link to update the booking's dates by hand. |
If a push fails for any other reason, you get the same task rather than a silently wrong PMS. Vacated nights are released on every connected calendar, and the new nights are blocked.
A stay that's already in progress can still be modified — extending a guest who wants two more nights is the most common reason to use this at all.
The dialog checks the proposed stay the same way a new booking is checked, and tells you which rule it breaks before you can confirm:
The booking itself is excluded from the conflict check, so extending into your own dates works exactly as you'd expect.
Changes are host-initiated. A guest who wants different dates messages you, and you make the change. That keeps you in control of whether the dates work for your calendar and your cleaners, and stops guests re-pricing a stay themselves.
New to Haven?
Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.
Free to build · No credit card · Private until you publish