Skip to main content
Edit reservation is one screen where you stage every change together — party size, date, time, and even which experience it is — see the money consequence before you commit, and apply it all with one button. There are no per-field edit buttons scattered around. That’s deliberate: changing a party size and a date are usually one decision, and splitting them means the first change is applied against availability that the second is about to move. Available while a reservation is Pending payment, Confirmed or Checked in.

​
What you can change

Change the date, experience or party size and the Time list re-queries live availability — with this reservation’s own seats excluded, so it isn’t competing with itself. The times offered are for the party size you’ve staged: shrinking a party opens up tighter slots, and the whole edit applies at that final size. If nothing fits, the field says why — a few examples:
Estate Tasting doesn’t run on Fri, Aug 28, 2026 — its schedule has no times that day. Estate Tasting takes parties of 2 to 8 — a party of 10 is outside that range. Every time on Fri, Aug 28, 2026 is full for a party of 10 — try a smaller party or another date. Closed on Dec 25, 2026 — Christmas Day.
A new date or experience needs a time chosen before the edit can apply.

​
Overbooking on purpose

When a change doesn’t fit — the time is full, no table seats the party, or the party is outside the experience’s size range — Riserva says so in a warning and offers an override:
This change doesn’t fit ☐ Overbook — apply this change anyway
Tick the box and press Update reservation again. The change applies, the time slot shows over capacity in Host and availability, and the override is recorded on the reservation’s timeline (“capacity overridden”) so it’s always clear it was a decision, not an accident. Guests can never do this — it’s a staff-only control. A date the experience doesn’t run, or a closed day, can’t be overridden: the override is for capacity, not for inventing times.

​
The Summary panel

The right-hand panel lists exactly what will change:
Experience → Estate Tour Date → Saturday, August 15, 2026 Time → 2:00 PM · Barrel Room Party size → 6
and then one line about the money. It’s the whole point of the screen — the panel is built to say the same thing the system will actually do, so it can never promise a refund that doesn’t arrive.

​
What happens to the money, in plain words

​
You add guests to a paid reservation

Each added guest owes the experience’s price. The payment badge turns to Partially paid — some money is in, more is owed — with a line like “$225 due for guests added after payment”, and the timeline records it. Collect it with a payment link, on-site, or waive it.

​
You remove guests from a paid reservation

Removed guests first cancel out any unbilled balance — if three guests were added but never paid for and two then drop out, two of that balance simply disappears. Only after that do removed guests earn a refund of what was actually paid, worked out proportionally. The refund follows your cancellation policy. Removing seats is a partial cancellation, so the removed guests’ share is priced by the same schedule a cancellation would use — a same-day shrink under a “no refund within 24 hours” policy refunds nothing, and the withheld amount stays on the order (the timeline and the Payment card both record it). When the policy withholds something, the panel offers the choice explicitly:
  • Per the cancellation policy — the default, with a sentence explaining exactly what’s refundable and what stays.
  • In full, overriding the policy — refunds the whole share; the override is recorded on the timeline with who chose it.
  • Don’t refund — shrinks the party and keeps the payment; the timeline records “Refund of $75.00 skipped — payment kept on file”.
Afterwards the reservation page shows the party at its new size and the seats that remain as Paid — the badge does not change — with a Refunded row for what went back and, when the party had paid through more than one order, each order netted by the refund made on it (the guests added last are refunded first, from the order that paid for them). When the policy refunds everything anyway (plenty of notice), you just see the familiar checkbox, Refund to the original payment, ticked by default.

​
It’s a whole-venue buyout

Nothing happens. A buyout is one price for the room, so party size doesn’t change what’s owed. The panel says so before you commit:
A buyout is one price for the whole venue — changing the party size doesn’t change what’s owed.

​
You move the date or time (same experience)

No money changes. But table assignments clear and any open payment link is voided — whenever the date or the time changes, the panel says so before you commit:
Table assignments clear and any open payment link is voided.
Any scheduled charge re-anchors to the new time, and the guest gets the Reservation rescheduled email quoting both the old and the new slot. Moving a reservation flagged Booked after its time (paid after its visit had ended) clears the flag.

​
You change the experience

Riserva works out the difference between the new price for this party and everything already paid or owed.
  • More expensive → the difference is owed (the badge reads Partially paid when money was already collected).
  • Cheaper → any unbilled balance is cancelled first, then the remainder is refunded.
  • Nothing paid yet → it simply re-prices.
  • Moving to a free experience → everything paid comes back.
Riserva flags add-ons for you to handle by hand:
Add-ons belong to the previous experience — review or refund them.

​
Reason for edit

A short note, staff-only, that lands on the reservation’s timeline as a comment under your name.
Only visible to staff — it lands on the reservation’s timeline.
Use it. Six weeks later, “moved at guest’s request, wedding rescheduled” is the difference between a clean record and a mystery. A reason on its own, with no other change, is a valid edit.

​
If the change doesn’t fit

Riserva re-checks every change against real availability at apply time, and a change that doesn’t fit gets the warning banner and override described in Overbooking on purpose above. Occasionally a move succeeds and the resize doesn’t. Riserva tells you exactly that, rather than pretending the whole edit worked:
The date/experience change applied, but the party size didn’t: …

​
The order things happen in

Move first, then resize. The move claims the new slot; the resize is then validated against capacity where the reservation now sits. That’s the only order that gives a correct answer.
What things mean on this screen: What things mean: A reservation’s page and Edit reservation