Skip to main content
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.
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.

The life of an order

1

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

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

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.

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

Ticket types

Capacity that pending orders hold against.

Attendees

Where a completed order’s registrations land.

Bundles

One order can carry a whole box of items.

Refund policies

The promise attached to what an order bought.