> ## Documentation Index > Fetch the complete documentation index at: https://docs.riservahq.com/llms.txt > Use this file to discover all available pages before exploring further. # Experiences and one-off events In Riserva, a one-off event is an experience with a single-date schedule. There is **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. | What differs | Recurring experience | Event | | - | - | - | | Schedule | Weekly: days of the week, a first and last seating time, and how often seatings start | Pinned to a **single date** | | Seatings | Many, on a repeating pattern | One | | Added with | **Add weekly schedule** | **Add event date** | That's the whole distinction. Everything else works identically: capacity, pricing, add-ons, policies and the booking widget. *** ## Adding a schedule Schedules live in the **Schedule** card on an experience's page. It has two buttons. **Add weekly schedule** asks for: | Field | Meaning | | - | - | | **Venue** | Which room this schedule runs in | | **Days** | The weekdays it runs | | **First slot** / **Last slot** | The first and last *seating*, not opening and closing | | **Slot every (min)** | How often a new seating starts | | **Capacity override** | Optional — a different per-slot capacity for these hours (Manual capacity and Open experiences only) | **Add event date** asks for: | Field | Meaning | | - | - | | **Venue** | Where it happens | | **Event date** | The single date | | **Time** | The one seating | | **Tickets** | Optional cap for this event, overriding the experience default | *** ## Several schedules on one experience One experience can carry several schedules; that 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. They 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 The **Experiences** page is split into three zones: events, recurring experiences, and venues with nothing to book. **Events** sit at the top, one row per date. Each row has a calendar chip and a sold-vs-capacity figure ("12 / 40 tickets"). An **Upcoming / Past** toggle defaults to Upcoming. A **Today** badge shows where it applies, and **Sold out** once every ticket is gone. **Recurring experiences** sit below. Each has a plain-language schedule line ("Thu–Sun · 11:00 AM–4:00 PM", plus "+1 more" when it has further schedules), a thumbnail and the price on the right. Filters for venue and status sit above them. **Venues with nothing to book** is a nudge when a room you've built has no experience scheduled in it. An event on the Venue floor map or Whole venue shows just "12 guests booked". It has no fill bar and no Sold out. Its tables or room, not a ticket number, decide when it's full. 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, there is nothing left to book. Guests no longer see it in your store's **Experiences list**. Staff no longer see its card on the POS **Book reservation** tile. Its reservations, and its row under **Past**, stay. *** ## Changing an event's date after tickets sell Once guests hold tickets for an event date, Riserva won't move that date, its time or its venue under them. A reservation keeps the date and time it was sold for. Move the reservations first, then change the date. 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. 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 one refunds under your policy. Then archive the experience or delete the date. Archiving alone stops new sales but leaves every reservation in place. **Save** in **Edit event date** refuses a change to a sold date. Under the field you changed, it says "3 reservations hold this date — move them from the reservation list first". Depending on what you changed, it may instead say "… hold this time — …" or "… 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. Lowering it under the sold count shows "8 tickets are sold — the count can't go below 8". *** ## Putting experiences in your order You choose which experience guests see first, because they read the first card first. With two or more experiences that aren't archived, the Experiences page header has a **Reorder** button. 1. Press **Reorder**. **Reorder experiences** opens, with one numbered row per experience: its thumbnail and name, and a **Draft** badge on drafts. 2. Drag a row by its handle, or use its up and down arrows. 3. Press **Save order**. You see "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 Tags group experiences so a storefront list can show just one group. Every experience's page has an **Organization** card in the right-hand rail with a **Tags** field. Use tags such as "kids", "napa" or "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. One click reuses one, so 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). It can also show 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](/getting-started/add-the-booking-widget). *** ## Duration, turn time and what a seating occupies A seating occupies its duration plus its turn time. Two fields on the **Schedule** card set them: * **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. It's why overlapping seatings on a per-table experience behave sensibly without you doing arithmetic. *** ## Blackout periods A blackout period closes dates to new reservations, such as a holiday, a private buyout or the harvest crush. Set them in **Settings → Venues & floor maps → Blackout periods**. Add a period with a name and a date range. Then 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](/getting-started/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. The list is grouped by venue when more than one is involved. *** **What things mean on this screen:** [What things mean: Experiences](/reference/experiences) ## Related * [Create your first experience](/getting-started/create-your-first-experience) * [Capacity strategies explained](/core-concepts/capacity-strategies) * [Publish an experience](/getting-started/publish-an-experience) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.