---
title: "What you sell"
description: "Slots, tickets, events, season passes, vouchers and closures: how to define what customers can book."
---

> Documentation Index
> Fetch the complete documentation index at: http://localhost:4321/llms.txt
> Use this file to discover all available pages before exploring further.

# What you sell

> **Administrators only**
>
> This part of the portal is only visible to people with the **Administrator** role. If you can't see it in your menu, ask an administrator. See [Roles and permissions](/reference/roles-and-permissions).

These screens live under **Operations** in the menu. They decide what your customers see on the booking site.

- **Slots** — The repeating times you run, and how many bookings you allow per day. [Read](/selling/slots)
- **Tickets** — What customers buy: a name, a price, and the slots it can be booked on. [Read](/selling/tickets)
- **Events** — A ticket for one specific date, such as a night ride or race. [Read](/selling/events)
- **Season passes** — Customers pay once and ride free on chosen tickets for 1 to 12 months. [Read](/selling/passes)
- **Vouchers** — Discount codes, as an amount or a percentage. [Read](/selling/vouchers)
- **Closures** — Days you're closed, hidden from the booking calendar. [Read](/selling/closures)

## The two things that put a session on sale

> **Remember this and the rest is easy**
>
> A **slot** says *when* you run. A **ticket** says *what can be bought*. A day only appears for customers once an **enabled ticket is attached to the slot** that creates it.

If customers can't see a session you expect, the cause is nearly always one of: no enabled ticket on that slot, the slot is inactive, there's a [closure](/selling/closures) on that date, or it's beyond the number of calendar months you show. See [Troubleshooting](/reference/troubleshooting).

Source: http://localhost:4321/selling/index.mdx