Passes

A Pass is one thing you sell for one Event: a name, a price, a sale window, and a capacity. It is the only thing a buyer can put in an Order, so your ticket catalogue is simply the list of Passes on the Event.

An Early Bird, a VIP tier, a student rate, and a Sunday-only entry are four Passes. None of them is a special product type — they differ only in configuration.

• Belongs to

  Exactly one Event

  A tier, phase, rate, or time slot is a separate Pass

• Price

  An offer price in the Organization's currency

  An optional list price adds a strike-through

• Sale window

  Optional start and end

  The end may never pass the Event end

• Capacity

  Its own limit, or none

  Event and session limits are ceilings above it

• Sells to

  Individual, team, or both

  Set as the Pass's participation policy

• On sale

  Window decides, not a switch

  Switching it off reports it as cancelled

What a Pass carriesCopy Anchor Link

• a name of up to 120 characters and a description of up to 2,000
• an offer price and an optional list price, both in the Organization's currency
• an optional sale window
• an optional capacity, and whether capacity counts entries or people
• a minimum and maximum quantity per Order, from 1 to 50
• an entry kind (individual, team, or mixed) and a pricing basis
• an approval requirement
• access to all Event sessions, or to a selected few

You shape all of that except the currency, which comes from the Organization. A Pass can never be sold in a currency of its own.

Tiers are just PassesCopy Anchor Link

Because each is a separate Pass, each has its own window, capacity, and quantity limits. Two Passes on the same Event never share a price or a limit.

Attendance follows the EventCopy Anchor Link

A Pass does not choose between in-person and online. The Event does, and its Passes inherit that:

The Registration records the one mode the buyer picked. It never changes afterwards; changing it means cancelling and registering again.

Sale state is derivedCopy Anchor Link

A Pass is on sale because of its dates, not because someone flipped a switch. Three of the four states are read from the sale window every time the Pass is loaded.

stateDiagram-v2
  state "On sale" as OnSale
  [*] --> Scheduled
  Scheduled --> OnSale : start time passes
  OnSale --> Ended : end time passes
  Scheduled --> Cancelled : switched off
  OnSale --> Cancelled : switched off
  Cancelled --> Scheduled : switched back on early
  Cancelled --> OnSale : switched back on

A Pass with no window at all is on sale from the moment it exists. That is the common case: a single price that sells until capacity runs out.

Switching a Pass off removes it from the public Event page and reports it as cancelled. Switching it back on returns it to whichever of the other three states its dates produce. Bulk actions can switch many Passes at once.

What changes after publishingCopy Anchor Link

Once the Event is published, a Pass is mostly frozen. The rule is simple: anything that changes what a buyer pays or gets is a commercial change and is refused.

The refusal is an error, not a silent no-op. Buyers have already seen the old terms, and a confirmed Order must stay explainable. Decide prices before you publish: afterwards, a different price needs a different Event.

A Pass can only be deleted while its Event is a draft. After publication the only exit is switching it off.

Paid Passes need a verified payoutCopy Anchor Link

An Event with any priced Pass cannot be published until the Organization has an approved KYC profile and a verified settlement account. Free Events skip that check.

The check runs at publish time only. A free Event publishes without it, so if you add a priced Pass after publishing, nothing re-runs the check today — set up payouts before you plan to charge.

Failure paths you will meetCopy Anchor Link

RelatedCopy Anchor Link

• Pricing — offer, list, and the platform fee
• Coupons — the code-driven discount
• Availability — capacity, holds, and selling out
• Registrations — what a buyer's entry looks like