> ## 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. # Bundles > Package ticket types and add-ons into one purchase — the buyer receives each item's own registrations and perks. A bundle packages existing ticket types and add-ons into a single purchase — a "VIP duo pack", a "ticket + breakfast" combo. Find them under **Bundles** in the event navigation. The key idea: **a bundle is only the name on the box**. It grants nothing itself. When someone buys a bundle, they receive each item's *own* outcome — a registration for every ticket type in the box, and the perks of every ticket and add-on it contains. There is no "bundle perk" and no bundle-level registration. ## Compose and publish a bundle Click **Create bundle** and name it. Like a ticket type, it is born a **draft**. On the bundle's page, add contents with **Add a ticket type** and **Add an add-on**, each with a quantity — two General admission tickets and one breakfast voucher makes a duo-with-breakfast pack. A bundle needs at least one item to publish. Click **Publish** and confirm. The bundle becomes available as one purchase at checkout. ## What the buyer gets Buying a bundle walks through one [order](/en/ticketing/orders), and fulfilment unpacks the box: * Each **ticket type** item produces its own registration(s) — counted against that ticket type's capacity, exactly as if bought separately. * Each **add-on** item delivers its own perks. * Perks come from the items, never from the bundle. ## Lifecycle — same as ticket types Bundles share the standard lifecycle: **draft → open ⇄ closed → archived**. Drafts are invisible; **Close sales** / **Reopen** toggle availability; bundles are **never deleted**, only archived, and restoring lands on **Closed**, never Open. See [Ticket types](/en/ticketing/ticket-types) for the full rules. ## Rules to know * **The items' rules still apply.** A bundle cannot sell what its contents can't: if a ticket type inside is sold out or outside its sale window, the bundle purchase can't complete for that item. Size the contents' capacity with bundles in mind. * **Archived items are flagged** in the bundle's contents list ("— archived") so you notice a box pointing at a retired product. * **No nesting.** A bundle contains ticket types and add-ons — not other bundles. * **Free today.** A bundle carries no price of its own yet; bundle pricing arrives with paid ticketing. * **Refunds follow policy per sellable** — a bundle can cite a [refund policy](/en/ticketing/refund-policies) like any other sellable. Because the bundle grants nothing itself, you never have to keep it in sync: change a ticket type's perks or form and every bundle containing it follows automatically. ## Related The registrations a bundle's ticket items produce. The perk-carrying extras a bundle can contain.