Skip to main content
Riserva has one thing you create, not two. A ticketed harvest dinner is an experience; so is a tasting you run every weekend. The difference is the schedule.
  • A recurring experience has a weekly schedule: days of the week, a first and last seating time, and how often seatings start.
  • An event has a schedule pinned to a single date, with one seating.
That’s the whole distinction. Everything else — capacity, pricing, add-ons, policies, the booking widget — works identically.

​
Adding a schedule

Open an experience and find the Schedule card. Two buttons: Add weekly schedule asks for: Add event date asks for:

​
Several schedules on one experience

This is the point of separating them. One “Estate Tasting” can have:
  • Thu–Sun, 11:00–16:00, every 30 minutes, at the tasting bar
  • Saturdays only, 14:00–16:00, hourly, in the barrel room at a higher capacity
And one “Harvest Dinner” can have three event dates — which show up as three separate rows, because that’s how you manage them: each one sells its own tickets and each one can sell out on its own.

​
How they look in the experiences list

Experiences is split into zones:
  • Events at the top, one row per date, with a calendar chip and a sold-vs-capacity figure (“12 / 40 tickets”). There’s an Upcoming / Past toggle, defaulting to Upcoming, a Today badge where it applies, and Sold out once every ticket is gone. An event on the Venue floor map or Whole venue shows just “12 guests booked” — no fill bar, no Sold out — because its tables or room, not a ticket number, decide when it’s full.
  • Recurring experiences below, with a plain-language schedule line (“Thu–Sun · 11:00 AM–4:00 PM”, plus “+1 more” when it has further schedules), a thumbnail, filters for venue and status, and the price on the right.
  • Venues with nothing to book — a nudge when a room you’ve built has no experience scheduled in it.
Once an event’s date is behind you, it moves to the Past view with a faded date chip. In the experience’s own Schedule card, that date row carries a Past badge. When every date an experience has is behind you, guests no longer see it in your store’s Experiences list, and staff no longer see its card on the POS Book reservation tile — there is nothing left to book. Its reservations, and its row under Past, stay.

​
Changing an event’s date after tickets sell

A reservation keeps the date and time it was sold for. So once guests hold tickets for an event date, Riserva won’t move that date, its time or its venue under them: Save in Edit event date says, under the field you changed, “3 reservations hold this date — move them from the reservation list first” (or ”… hold this time — …”, ”… hold this date at this venue — …”). Deleting the date is refused with the same sentence under its row. Tickets saves on its own, but never below what is sold: “8 tickets are sold — the count can’t go below 8”. To move an event that has sold:
  1. Add event date with the new date, on the same experience.
  2. From Reservations, open each reservation for the old date and move it to the new one with Edit reservation (guests are emailed the new date).
  3. Back on the experience, edit or delete the old date — it saves once no reservation is left on it.
To cancel an event, cancel its reservations one at a time from the reservation list (each refunds under your policy), then archive the experience or delete the date. Archiving alone stops new sales but leaves every reservation in place.

​
Putting experiences in your order

Guests read the first card first, so you choose which that is. With two or more experiences that aren’t archived, the Experiences page header has a Reorder button. It opens Reorder experiences: one numbered row per experience, with its thumbnail and name (a Draft badge on drafts). Drag a row by its handle, or use its up and down arrows, then press Save order (“Order saved”). Cancel leaves the order as it was. That one order is used in three places:
  • the Experiences list block on your store,
  • the cards on the Book reservation tile in Shopify POS,
  • the Recurring experiences list on this page. (Events keep their date order here.)
Until you reorder, everything is alphabetical. A new experience lands after the last one you ordered, so open Reorder again to move it up.

​
Tags: grouping experiences

Every experience’s page has an Organization card in the right-hand rail with a Tags field — “kids”, “napa”, “outdoor”, whatever groups your program. Type a tag and press Enter; it becomes a chip you can remove with its ×. Under the field, Also used: lists tags already on your other experiences, so one click reuses one and spellings stay consistent. Capitals don’t matter: “Napa” and “napa” are the same tag. Tags are for your storefront: an Experiences list block can show only the experiences carrying one tag (its Only experiences tagged setting), and only one location (Only this location). That is how you give each property, or a family-visits page, its own list. See Add the booking widget.

​
Duration, turn time and what a seating occupies

Two fields on the Schedule card:
  • Duration (min) — how long the reservation occupies the space.
  • Buffer / turn (min) — reset time after each reservation: clearing, wiping down, re-pouring.
A 90-minute lunch with a 15-minute turn occupies a table for 105 minutes. That’s what Riserva blocks when deciding whether the next party fits, and it’s why overlapping seatings on a per-table experience behave sensibly without you doing arithmetic.

​
Blackout periods

Close dates to new reservations from Settings → Venues & floor maps → Blackout periods — a holiday, a private buyout, the harvest crush. Add a period with a name and a date range, and choose what it covers: everything, whole venues, or specific experiences at a venue. Existing reservations stand; a blackout only stops new ones. See Locations and venues for the full flow.

​
What guests see

A guest sees an experience, its photo, its description, and the times that are actually open. They never see the schedule rules behind it — two schedules covering the same day simply produce one combined list of times, grouped by venue when more than one is involved.
What things mean on this screen: What things mean: Experiences