> ## 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. # Ticket Management > Reference for editing tickets and bundles, turning them on or off, creating add-ons, and automating tiers with release chains. Use **Ticket Management** to control what attendees can buy. The page has two tabs: **Tickets** and **Add-ons**. ## Find a ticket Above the table you can filter by: * **Ticket Status** (or **Add-on Status** on the Add-ons tab): **Active**, **Inactive**, or **Ended**. Add-ons offer **Active** and **Inactive**. * **Session**: shown only when the event has more than one session. * **Search**: by ticket name or bundle name (by add-on name on the Add-ons tab). Tickets are grouped by session. Each session has a table with **Ticket Type**, **Price**, **Total**, **Sold**, **Available**, and **Status**. ## Turn a ticket on or off Use the status dropdown in the **Status** column: * **Active**: the ticket is on sale and visible to buyers. * **Inactive**: the ticket is hidden from buyers. * **Ended**: shown automatically once the ticket's sale end time has passed. You cannot change the status of an ended ticket. If an active ticket's sale start date is still in the future, a note under the status shows how many days until sales start. ## Edit a ticket or bundle Select the pencil icon at the end of a row to open the **Edit Ticket** panel. For a bundle, the panel is called **Edit Bundle** and lists the included tickets. | Field | Notes | | - | - | | **Session** | Shown for reference and cannot be changed. | | **Name** | Required. Locked once any tickets have been sold. | | **Status** | **Active** (visible to buyer) or **Inactive**. | | **Description** | Up to 200 characters. | | **Total Quantity** | Required. Must be a positive whole number and cannot be lower than the number already sold. For bundles this field is **Max Bundle Sales**, a cap on bundle sales that is still controlled by the underlying ticket inventory. | | **Price** | Required. Locked once any tickets have been sold. Whole numbers only for currencies without decimals, otherwise up to two decimal places. | | **Sales Start Date / Sales End Date** | Required. Choose a date, then an hour and minute for each. | | **Limit Qty per Order** | Optional. A whole number from 1 to 10. | | **Limit Qty per User** | Optional. A whole number from 1 to 20. | Select **How Fees Work** under the price to see what the buyer pays and what you receive. It breaks the price down into the ticket price, service fee, VAT, and the amount you receive. Select **Save** to apply your changes, or **Cancel** to close the panel. > [!WARNING] > > Name and price cannot be changed after the first ticket is sold. Set them carefully before you open sales. ## Release chains Each session has a **Release Chains** panel above its ticket table. It is folded closed by default. The header shows a summary such as "2 chains ยท 1 auto-releasing". A release chain lets you sell tiers one after another, for example Early Bird, then General Admission, then Final Release. When the current tier is nearly sold out, the next tier is activated automatically. For a full worked example, see [Selling General Admission in tiers](/tickets/scenario-ga-tiers). ### When the next tier opens Inside the open panel, a line states the percentage at which the next tier opens, for example "The next tier opens when 98% of the current tier is sold." Each tier shows a progress bar with a tick at that point. The next tier opens at that percentage, not necessarily at the very last ticket. **1. Create a chain** Open the **Release Chains** panel and select **New chain**. Enter a name (1 to 100 characters, for example "GA") and select **Create**. A new chain starts paused. **2. Add tickets in order** In the chain card, use **+ Add existing ticket** to add tickets. Drag tiers to reorder them, or use the remove button on a tier to take it out. A ticket can only be in one chain. Add-ons and bundles cannot be added. **3. Turn on Auto-release** Switch **Auto-release** on. While it is off, the chain is paused ("Paused - tiers won't activate automatically") and later tiers will not activate by themselves. ### What each tier shows | Message | Meaning | | - | - | | **On sale** | This tier is currently selling. | | Activates automatically when 'X' sells out | Waiting for its turn. | | Sold out - next tier opened | This tier is done and the next one has opened. If held tickets return, you may see how many are back on sale. | | Paused - won't activate until auto-release is on | The chain is paused. | | Inactive and won't auto-activate | A later tier is already on sale. Activate it manually or remove it. | | Its sales end time has passed | It can't sell when its turn comes. Update its end time or remove it. | | Sold out / Ended - the chain skips it | The chain moves past it. | In the ticket table, chained tickets show a badge such as "GA - 2/3", and tickets opened automatically note which tier's sell-out opened them. When every tier has been used, the chain shows **Exhausted**. ### Other chain controls * **Activity log** (history icon in the panel header): a record of sell-outs, automatic activations, chains finishing, and auto-release being turned on or paused. A number on the icon shows recent entries. * **Copy to...**: copy a chain to other sessions of the same event. Tiers are matched to tickets by name and you review the matches before copying. Copied chains start paused. This button only appears when the event has more than one session. * **Delete** (trash icon): removes the chain. Tickets keep their current status and the activity log is kept. > [!NOTE] > > Every ticket in a chain needs a sales end time that has not passed, and the end times must be consistent in chain order. If the portal flags a schedule problem on the chain card, fix the tier's end time or remove it from the chain, then turn Auto-release on again. ## Add-ons Add-ons are extras buyers can purchase alongside tickets, such as parking or merchandise. Open the **Add-ons** tab and select **Create Add-on**. | Field | Notes | | - | - | | **Session** | Required. | | **Add-on Name** | Required. | | **Status** | Required. Active or Inactive. | | **Description** | Optional. | | **Linked to** | Required. The tickets an add-on can be purchased with. | | **Inventory Source** | Required. **Own inventory** gives the add-on its own quantity. **Sync from ticket** uses another ticket type's inventory, so each add-on sale reduces that ticket's availability. | | **Source Ticket Type** | Shown for **Sync from ticket**. Pick the ticket whose inventory is used. | | **Total Quantity** or **Add-on Sales Limit** | Required. With **Own inventory** this is the quantity. With **Sync from ticket** it caps add-on sales while using the source ticket's inventory. | | **Face Value** | Required. A positive whole number. | | **Sales Start Date / Sales End Date** | Optional for add-ons. | | **Limit Qty per Order / Limit Qty per User** | Optional. Positive whole numbers. | The Add-ons table shows **Add-on Name**, **Price**, **Total**, **Sold**, **Available**, and **Status**. Use the edit icon on a row to change an add-on. When editing, the inventory source is locked. ## Guides and related pages > **[Ticketing Concepts](/tickets/concepts)** > > The building blocks explained. > **[General Admission in tiers](/tickets/scenario-ga-tiers)** > > Early Bird to Final Release. > **[Multi-day festival](/tickets/scenario-multi-day-festival)** > > One session per day. > **[Group packages](/tickets/scenario-bundles)** > > Bundles. > **[VIP and add-ons](/tickets/scenario-vip-addons)** > > Limited tickets with extras. > **[Discount campaigns](/tickets/scenario-promo-discounts)** > > Promo codes. > **[Comping guests](/tickets/scenario-comp-guests)** > > Free tickets for artists and press. > **[Ticket Report](/tickets/ticket-report)** > > See what sold. To give tickets away instead of selling them, see [Complimentary Tickets](/tickets/comp-tickets). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.