> ## Documentation Index
> Fetch the complete documentation index at: https://help.taack.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Tickets and pricing

> Create ticket types, set prices and currencies, configure fees, and organize ticket groups.

Tickets are how patrons access your event. Read on for how to create ticket types, set prices, choose who pays processing fees, and organize tickets into groups.

## Create a ticket type

<Steps>
  <Step title="Open the Tickets tab">
    From your event hub, select the **Tickets** tab and click **Create ticket**.
  </Step>

  <Step title="Choose free or paid">
    * **Free tickets** — no processing fees for you or the patron
    * **Paid tickets** — priced in TTD, JMD, or USD
  </Step>

  <Step title="Set the price and currency">
    Choose your currency:

    | Currency | Notes                                                            |
    | -------- | ---------------------------------------------------------------- |
    | **TTD**  | Trinidad and Tobago dollars                                      |
    | **JMD**  | Jamaican dollars — patrons also see a TTD equivalent at checkout |
    | **USD**  | US dollars                                                       |

    <Info>
      The first ticket you create locks the event to that currency. All other ticket types on the same event must use the same currency. Barbados is a valid event location, but BBD is not a pricing currency — choose TTD, JMD, or USD for Barbados events.
    </Info>
  </Step>

  <Step title="Choose a fee structure">
    For paid tickets, the question **How do you want to manage ticket fees?** appears. The processing fee is **7% + \$1.80 TTD per order**, charged once per order regardless of ticket count.

    | Option           | Who pays                                                              |
    | ---------------- | --------------------------------------------------------------------- |
    | **Absorb fees**  | You — patrons pay the listed price; the fee comes out of your revenue |
    | **Split 50/50**  | Both — you and the patron each cover half                             |
    | **Pass on fees** | Patron — they pay the listed price plus the full fee at checkout      |

    The fee summary shows **You Receive**, **Patron Fee**, and **Host Fee** so you can see the exact split before saving.
  </Step>

  <Step title="Set quantity and sale window">
    * **Quantity** — total tickets available for this type
    * **Sale schedule** — when sales open and close
    * **Ticket limits** — minimum and maximum tickets a single patron can buy per order
  </Step>

  <Step title="Configure optional settings">
    * **Hide when sold out** — remove the ticket from the page once quantity reaches zero
    * **Request only** — require organizer approval before the sale is confirmed (works with or without event-level approval)
    * **Payment plan** — let patrons pay a deposit at checkout and the rest on a schedule. See [Payment plans](/organizers/payment-plans) for setup and policies.
  </Step>
</Steps>

## Duplicate a ticket

If you need a similar ticket type with a different price or quantity, use **Duplicate ticket** from the ticket row menu. This copies all settings so you only need to adjust what's different.

## Ticket groups

For events with multiple days, sections, or tiers, use ticket groups to organize how tickets appear on the event page.

Each group has a **name** (for example, "Day 1" or "VIP Section"), an optional date label, and an optional subtitle.

Enable grouping from the **Tickets** tab, create your groups, then assign ticket types to each group. You can enable or disable groups without deleting tickets.

## What patrons see

On the ticket selection page, patrons choose quantities for each available ticket type. They see:

* The ticket name and price
* Sold-out status when applicable
* A lock icon and "Requires approval to purchase" message on request-only tickets
* "Max limit reached" if they hit the per-patron cap

If your team has selling enabled, patrons may also choose which team member referred them — useful for tracking attributed sales.

## Tips for pricing

<Tip>
  Start with one or two ticket types and add more as demand becomes clear. Early bird and general admission tiers are a common pattern.
</Tip>

<Tip>
  If you're unsure about fees, **Absorb fees** gives patrons the cleanest checkout experience — they pay exactly the price shown on the page.
</Tip>

## Next steps

* [Payment plans](/organizers/payment-plans) — let patrons split higher-priced tickets into scheduled payments
* [Publish and share your event](/organizers/publish-and-share) once tickets are ready
* [Manage ticket requests](/organizers/manage-requests) if approval is enabled