> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/events-engine-overview/setup-manage-tickets.md). # How to Set Up & Manage Event Tickets Tickets are configured per event after you set the event's registration type to **Digital tickets**. Each event can have multiple ticket types (e.g., *Member*, *Non-Member*, *VIP*) with different prices, capacities, sale windows, and audience visibility. Linking inventory across tiers ensures all tickets draw from one shared capacity pool. ### Before you begin (Prerequisites) * **Event Setup**: The event must already be created with **Digital tickets** as the registration type. See: [How to Set Up an Event](/products/control-panel-overview/events-engine-overview/create-event.md). * **Payment processor**: A payment processor must be active for ticketed events. See: [Stripe — Operator Manual](/products/integrations-overview/setup-stripe.md) or [GoCardless — Operator Manual](/products/integrations-overview/setup-gocardless.md). ### Set up ticket types #### 1. Open the ticket editor 1. Navigate to [**SELL > Manage Events**](https://control.peoplevine.com/events). > **Note (Pro Dash):** Navigate to **SELL > EVENTS > Manage Events**. 2. Click on the event to open its dashboard. 3. Click **MANAGE TICKETS**. #### 2. Configure the first (main) ticket type This sets the **total event capacity** that other ticket types can link back to. Fill in the **Add Tickets** form: * **Ticket Type** — e.g., *General Admission*, *Member*, *VIP*. * **Price Per Ticket** — set to `0` for free tickets. * **Total Inventory** — total capacity for the event (this is the main pool). * **Additional Ticket Information** — optional text field for extra details about this ticket type. * **Date On Sale** / **Date Off Sale** — the sale window. * **Minimum Purchase Quantity** / **Maximum Purchase Quantity** — per-order limits (e.g., min 1, max 4 per order). * **Visibility** — who can see and buy this ticket. Defaults to *Anyone (Public)*; pick a membership program to restrict. * **Link Inventory** — leave on *Select Ticket to Link Inventory To* (default — no linking) for the first ticket; this ticket *is* the main pool. Click **ADD TICKETS** at the bottom. #### 3. Add additional ticket tiers For tier pricing (e.g., a discounted *Member* tier and a higher *Non-Member* tier sharing the same capacity): 1. After saving the first ticket, the page reloads with **Existing Tickets** at the top and the **Add Tickets** form below. Fill it in again for the next tier. 2. Configure Ticket Type, Price Per Ticket, Total Inventory, sale window, min/max purchase, and visibility. 3. **Link Inventory** — select the **main ticket** from the dropdown so this tier draws from the same total capacity. Always link non-primary tickets back to the main ticket. 4. Click **ADD TICKETS**. Repeat for every tier. Common patterns: | Scenario | Ticket types | Visibility | | --------------------------------- | ---------------------------------------------------- | ------------------------------------------------ | | Members only, free | *Member* | Restrict to membership programs | | Members only, multi-tier | *Standard*, *VIP* | Each restricted to its program | | Members + public, member discount | *Member* (lower price) + *Non-Member* (higher price) | Member tier restricted; Non-Member tier *Anyone* | | VIP comp + paid public | *VIP* @ $0 + *General Admission* @ $X | VIP restricted to VIP program; GA *Anyone* | For the visibility scenarios in detail, see: [How to Set Up an Event for Members and Public Registration](/products/control-panel-overview/events-engine-overview/setup-public-event.md) and [How to Set Up a Member-Only Event](/products/control-panel-overview/events-engine-overview/setup-member-only-event.md). #### 4. Use a Ticket Template (optional, for repeat events) If you run events with the same ticket structure repeatedly, build a **Ticket Template** once and copy it onto new events: 1. From any event's dashboard, click **MANAGE TICKET TEMPLATE**. 2. Add ticket types as you would on a regular event (title, price, availability, permissions, colors). 3. On any new event with no tickets configured yet, click **MANAGE TICKETS > COPY IN TICKET TEMPLATE**. The template's tickets are copied with linking, limits, and styling intact. > **Note**: The **Copy In Ticket Template** option is only available on events that have **no tickets yet**. Once you've added a ticket manually, you cannot copy a template over the top. ### Manage ticket inventory after sales begin #### Can I update ticket inventory once an event goes on sale? Yes — but be careful. **Capacity changes ADD to the existing pool, they do not replace it.** > **Warning**: If you start with **20** tickets, sell **10**, and adjust the *Total available* back to **20**, you end up with **30** total (10 sold + 20 newly added). To keep the total at 20, you would need to leave the field at the **net new capacity you want to add** — in this case, `0`. To change inventory mid-sale: 1. Open the event dashboard and click **MANAGE TICKETS**. 2. In **Existing Tickets**, click **EDIT** next to the ticket type. 3. Adjust **Total Inventory** by the **delta you want to add** — not the new desired total. 4. Click **UPDATE EVENT** at the bottom of the form. 5. Verify the new pool by checking the event dashboard's **Awaiting + Checked-In + Sold** count. #### Adjust tier prices, sale windows, or visibility These can be changed at any point and take effect immediately: * **Price** — adjustments apply to new purchases. * **Start / stop selling dates** — useful for time-gated tiers (e.g., *Early Bird* until a date). * **Visibility / membership program restrictions** — adding or removing programs changes who sees this tier going forward. ### Member Portal display behaviour Once tickets are on sale and the event is **Approved**, members see one of these states on the event card on the portal: | State | What members see | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Tickets available, normal inventory | *Tickets Available* | | Future on-sale date | *Tickets go on sale \[date]* — set by the **Start selling date** | | 9 or fewer remaining | *X tickets left* counter (can be turned off platform-wide via *Show Remaining Ticket Quantity* — see [Admin Settings Managed by Peoplevine](/products/portal-overview/portal-admin-settings.md)) | | Sold out | *Sold Out*, or **Join Waitlist** if a waitlist is configured. See: [How to Manage an Event Waitlist](/products/control-panel-overview/events-engine-overview/manage-waitlist.md) | ### Best Practice * **Always link non-primary tickets back to the main ticket.** Otherwise each tier has its own siloed pool and you can over-sell the venue. * **Set the sale window deliberately.** Use **Start selling date** for early-bird tiers and to prevent members from registering before promotion goes out. * **Calculate inventory deltas, not totals.** When mid-sale changes are needed, write down what's already sold and what new total you want, then enter the **difference** into *Total available*. * **Use ticket templates for recurring formats.** A weekly trivia night or a monthly social with the same tier structure is a strong fit. * **Test member vs non-member visibility** with two test accounts before promoting the event. ### What Happens Next * **On the member side**: Eligible members see the appropriate ticket tier on the event card. Purchase routes them through checkout (Stripe or GoCardless) and generates a serialized digital ticket. The QR code is available in the member portal (Account > Wallet > Tickets). * **On the admin side**: Sales appear in the event dashboard (Total Revenue + Awaiting count) and as transactions in [**SELL > View Transactions**](https://control.peoplevine.com/transactions). * **Next step**: [How to Manage Event Registrations](/products/control-panel-overview/events-engine-overview/manage-registrations.md) · [How to Manage an Event Waitlist](/products/control-panel-overview/events-engine-overview/manage-waitlist.md) · [How to Cancel and Refund a Member's Tickets](/products/control-panel-overview/events-engine-overview/cancel-refund-tickets.md). *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/control-panel-overview/events-engine-overview/setup-manage-tickets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.