> ## Documentation Index
> Fetch the complete documentation index at: https://docs.business.plvr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Scenario: VIP Tickets and Add-ons

> Offer a small number of premium tickets and sell extras such as parking or merchandise alongside them.

**Goal:** Sell a limited number of VIP tickets at a premium, and offer extras (parking, merchandise) that buyers can add.

## The example

| Item | Quantity | Price | Notes |
| - | - | - | - |
| General Admission | 400 | \$30 | Main ticket |
| VIP | 50 | \$90 | Limited |
| Parking Pass (add-on) | 80 | \$10 | Linked to General Admission and VIP |
| Event T-shirt (add-on) | 100 | \$25 | Linked to VIP only |

## Part 1: Limit your VIP tickets

**1. Set a small Total Quantity**

In [Ticket Management](/tickets/ticket-management), edit the VIP ticket and set **Total Quantity** to 50. Scarcity is built in: when 50 are sold, VIP is sold out.

**2. Limit how many one person can buy**

Set **Limit Qty per Order** and **Limit Qty per User** (for example 4 and 4) so VIP tickets spread across more buyers.

**3. Use a description**

Add a **Description** (up to 200 characters) explaining what VIP includes.

**4. Schedule when it opens**

Choose a **Sales Start Date** later than General Admission if you want VIP to appear as a second wave, or keep it **Inactive** until you announce it.

## Part 2: Create add-ons

**1. Open the Add-ons tab**

In Ticket Management, select the **Add-ons** tab, then **Create Add-on**.

**2. Name it and pick the session**

Choose the **Session**, enter the **Add-on Name** (for example "Parking Pass"), set **Status**, and add a **Description** that explains it to attendees.

**3. Choose who can buy it**

Under **Linked to**, select the tickets it can be purchased with. Parking: General Admission and VIP. T-shirt: VIP only.

**4. Pick the inventory**

**Own inventory** gives the add-on its own quantity (80 parking spaces). **Sync from ticket** uses another ticket type's inventory, so each add-on sold reduces that ticket's availability. Choose Own inventory for physical extras like parking and merchandise.

**5. Set the price and limits**

Enter **Total Quantity**, **Face Value**, and optional sales dates and per-order or per-user limits. Then save.

> [!NOTE]
>
> Add-ons are not tickets: they cannot be added to a release chain, and the inventory source cannot be changed after creating them.

## Track the results

The [Ticket Report](/tickets/ticket-report) lists add-ons with an **Add-on** label and shows an **Add-ons Sold** card when the event has add-ons.

## Related

* [Ticketing Concepts](/tickets/concepts)
* [Ticket Management reference](/tickets/ticket-management)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.