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

# Add-ons

> Extras attendees pick up alongside a ticket — a breakfast voucher, a workshop seat — delivered as the perks the add-on grants.

An add-on is something an attendee takes **on top of** a ticket: a breakfast voucher, a workshop seat, a merch pack. Find them under **Add-ons** in the event navigation.

An add-on is deliberately simple: a name, a description — and its **perks**. What an add-on actually delivers is the perks bound to it, exactly as a ticket type delivers its perks. The add-on is the thing on the shelf; the perks are what ends up in the attendee's hands.

## Create and publish an add-on

<Steps>
  <Step title="Create it">
    Click **Create add-on** and name it. Like a ticket type, it is born a **draft** — invisible and without effect until published.
  </Step>

  <Step title="Bind its perks">
    On the add-on's page, choose the perks it grants under **Perks this add-on grants**. Create the perks first on the [Perks](/en/ticketing/perks) page — an add-on with no perks delivers nothing.
  </Step>

  <Step title="Publish">
    Click **Publish** and confirm. The add-on becomes available to add on top of a ticket at checkout.
  </Step>
</Steps>

## Lifecycle — same as ticket types

Add-ons share the ticket type's exact lifecycle: **draft → open ⇄ closed → archived**.

* A draft is invisible to the public.
* **Close sales** stops new purchases without hiding history; **Reopen** resumes.
* **Archive** retires it; add-ons are **never deleted**, and restoring an archived add-on lands on **Closed**, never Open.

See [Ticket types](/en/ticketing/ticket-types) for the full lifecycle rules — they apply here unchanged.

## Rules to know

* **The perks are the product.** Attach the add-on's value as perk bindings; if the workshop it admits to is a gated agenda session, gate that session on the same perk and the chain works end to end — see [Perks](/en/ticketing/perks).
* **An add-on rides on a ticket.** It is bought alongside a registration at checkout, not on its own.
* **Free today.** Add-ons carry no price yet; paid add-ons arrive with pricing later.
* **A refund policy can be applied** to an add-on, same as to a ticket type — see [Refund policies](/en/ticketing/refund-policies).
* **Add-ons can be bundled.** A [bundle](/en/ticketing/bundles) can package a ticket type together with add-ons as one purchase.
* Every operation on an add-on is recorded in its log, so you can always see who published, closed or archived it.

## Related

<CardGroup cols={2}>
  <Card title="Perks" icon="gift" href="/en/ticketing/perks">
    Define what the add-on grants.
  </Card>

  <Card title="Bundles" icon="package" href="/en/ticketing/bundles">
    Sell a ticket and add-ons as one box.
  </Card>
</CardGroup>