> ## 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.

# Orders

> Every purchase from the event page — tickets, add-ons, bundles, even free ones — arrives as an order you can track from the console.

Every checkout on your event page goes through an **order** — including free tickets, which simply settle as an order of 0. Tickets, add-ons and bundles all travel the same road: the visitor places an order, confirms it, and the confirmation creates their registration(s). The **Orders** page in the event navigation is where you watch that traffic.

<Note>
  The Orders page is for **viewing and tracking**. Buyers create and confirm orders themselves on the event page; the one action you can take from the console is cancelling an order.
</Note>

## The life of an order

<Steps>
  <Step title="Placed — Awaiting confirmation">
    The visitor picks their items and submits. The order **holds its places for 15 minutes**: while it is pending, those seats count against the ticket type's capacity so nobody else can take them.
  </Step>

  <Step title="Confirmed — Completed">
    The visitor confirms and the order settles — a free order settles at confirmation with an amount of 0, the same flow a paid order will use later. Fulfilment turns the order into its registration(s), and the attendee appears in your attendee list.
  </Step>

  <Step title="Or: Expired / Cancelled">
    An order not confirmed within 15 minutes **expires** and releases its held places automatically. The buyer — or you, from the console — can also **cancel** a pending order, which releases the hold immediately.
  </Step>
</Steps>

## The order number

Every order has an **order number** — the buyer's credential. They use it to confirm or cancel their own order; treat it like a claim ticket. The console shows it in the **Order** column so you can match a buyer's question to their order.

## What the page shows

Each row lists the order number, buyer, items, total (— **Free** today), expiry for pending orders, and when it was placed, with its status: **Awaiting confirmation**, **Completed**, **Expired** or **Cancelled**. From a completed order you can jump straight to the resulting **attendee**.

## Rules to know

* **Even free events run on orders.** "Register" on the event page places a 0-amount order and settles it — so your Orders page is a complete record of public registrations. Registrations you key in yourself on the [Attendees](/en/events/attendees) page skip orders entirely.
* **A pending order holds capacity.** If a ticket looks sold out but your attendee count says otherwise, unexpired pending orders are likely holding places — they release within 15 minutes.
* **Repeat submissions never double-book.** Someone already registered who checks out again is simply acknowledged as already registered — no second seat, no error message. This holds even if they used a since-spent code or the ticket has since closed.
* **Expiry is automatic and exact** — 15 minutes from placement, no action needed from you.
* **Amounts are 0 today.** The order pipeline is live but every total is Free; payment collection arrives with paid ticketing later.

## Related

<CardGroup cols={2}>
  <Card title="Ticket types" icon="tickets" href="/en/ticketing/ticket-types">
    Capacity that pending orders hold against.
  </Card>

  <Card title="Attendees" icon="users" href="/en/events/attendees">
    Where a completed order's registrations land.
  </Card>

  <Card title="Bundles" icon="package" href="/en/ticketing/bundles">
    One order can carry a whole box of items.
  </Card>

  <Card title="Refund policies" icon="undo-2" href="/en/ticketing/refund-policies">
    The promise attached to what an order bought.
  </Card>
</CardGroup>