A ticket is a product type, but availability is event-specific. The catalog product supplies the price and receipt identity; the ticket option maps that product to attendance; capacity pools represent the seats or resources consumed. One ticket can consume several pools, and several tickets can compete for one pool.
Step by step
- Open Products & Catalog and create or review each sellable registration choice as product type event_ticket. Give the product a durable name, SKU, price, tax behavior, images, reporting category, and active status. For a separately published normal storefront sale, also enable Sell online, publish the product, give it a valid SEO slug, and publish the tenant storefront. Do not use a zero-dollar merchandise line as a substitute for paid admission.
- Return to Events → Offerings, open the offering, and choose Ticket options. Connect each option to exactly one active same-business event_ticket product. When the product and storefront are published and the registration definition is complete, the public feed returns checkout_status ready plus a branded purchase path into the normal CentriPOS storefront. Missing storefront, product, capacity, or registration prerequisites fail closed with a non-ready checkout status.
- Set the option code and customer-facing label. Configure Draft, Active, Paused, Sold out, or Archived status; sales opening and closing times; minimum and maximum per order; seats per ticket; eligibility rules; and sort order.
- Choose every occurrence the option admits. A conference pass may cover a large agenda; a morning camp ticket covers morning, an afternoon ticket covers afternoon, and a full-day ticket covers morning, the supervised lunch bridge, and afternoon. Early arrival and late pickup are separate entitlements unless the merchant deliberately includes them. Mark attendance-required occurrences explicitly.
- Create a capacity pool for each genuinely scarce resource: total campers, morning seats, afternoon seats, room occupancy, bus seats, robot kits, meal seats, or conference workshop capacity. Choose offering-wide capacity when all dates share one limit or occurrence capacity when each date is independent.
- Set capacity, optional overbook allowance, waitlist behavior, and Active, Paused, or Closed status. An overbook allowance expands the enforceable ceiling and should be used only with an explicit operating plan.
- Allocate each ticket option to every pool it consumes. Set units per seat when one attendee consumes more than one unit of a resource. A registration is accepted only when all linked pools can cover its seat count.
- For camp dayparts, avoid double counting. Morning consumes the morning pool, afternoon consumes the afternoon pool, and full day consumes both plus any lunch-specific pool. Early-arrival and late-pickup choices consume their own care pools. Add an overall camper, building, or staffing pool only when that shared physical limit really exists.
- Configure optional T-shirts, take-home robots, meals, parking, kits, or supplies as participant add-ons backed by ordinary published products and variants. Checkout creates real receipt lines and assigns the selected units to the attendee, preserving product revenue, tax, return, inventory, and unit reporting separately from admission.
- Run controlled tests before opening sales: one ticket, several ticket units, the last seat, an over-capacity request, an adult self-attendee, a youth attendee with guardian authority, a deferred group pass, required forms and waiver, a session choice, and an add-on variant. Each integer ticket unit must become one receipt-linked registration; pending payment keeps a finite hold, final payment confirms and issues credentials, and a void, return, refund, or quantity reduction reverses only its matching entitlements.
- Use Reports to compare ticket units, seats, capacity consumed, remaining capacity, registration revenue, discounts, refunds, and linked merchandise units. Ticket quantity, seat count, and capacity units can differ; choose the correct measure for each question.
- Use assignment_policy at_checkout for one-seat ticket units that collect an attendee during checkout. Use deferred_allowed only for multi-seat group passes; it reserves the documented seats and requires later explicit attendee, form, waiver, add-on, and session assignment instead of pretending one name represents the group.
- For a recurring occurrence-wide pool, CentriPOS measures attendee-selected session usage by the peak concrete occurrence instance, not by summing the entire series. This reuses the physical ceiling on each date without making a weekly class appear cumulatively sold out.
- Start repeated admission choices from a reusable ticket preset. Applying a preset copies a versioned snapshot of its label, assignment, quantity, price, capacity, inventory, admission, and sales-window defaults into the ticket option; later preset edits never silently rewrite an already published option.
- Use the visual purchase-rule builder for bounded groups, conditions, and actions such as eligibility, quantity, discount, access-code, or inventory behavior. Preview evaluation explains the rule graph for staff, but only the storefront quote can authorize the final purchaser, price, code reservation, capacity, and checkout state.
- For general admission, continue to use shared capacity pools. For a physical venue, publish one reusable seating layout with sections, rows, exact seats, accessibility attributes, companion relationships, and pricing zones; attach a versioned on-sale seating configuration to the offering, occurrence, or concrete instance, then map each ticket to permitted zones.
- A reserved seat moves through available, held, assigned, released, blocked, or maintenance state with append-only inventory evidence. Checkout holds are short-lived and bound to their quote intent; payment finalization converts the exact hold to a registration and ticket, while expiry, failure, cancellation, transfer, or refund uses the authoritative release lifecycle.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Product type: event_ticket | Catalog classification required for products linked to event ticket options. |
| Ticket option | Offering configuration around a sellable product, admission coverage, eligibility, order limits, and display order. |
| Seats per ticket | Number of attendee seats represented by one purchased ticket unit. |
| Occurrence assignment | Dated sessions that the ticket admits. |
| Capacity pool | Shared enforceable inventory of seats or another constrained resource. |
| Offering-wide pool | One limit shared across an entire offering. |
| Occurrence pool | Limit attached to one dated attendance block. |
| Units per seat | Capacity units consumed for each registered seat. |
| Overbook allowance | Explicit quantity permitted above base capacity. |
| Waitlist enabled | Allows demand to queue when linked capacity cannot cover confirmation. |
| Paused / Closed | Stops normal allocation without deleting historical registration data. |
| Merchandise product | Separate normal product for shirts, robots, meals, or supplies when unit, tax, inventory, or revenue reporting matters. |
| Public checkout status | ready means the published event ticket has a validated branded registration path; every other checkout status is fail-closed and omits a usable registration path. |
| Receipt entitlement adapter | One stable receipt-line/unit identity becomes one linked registration and, after qualifying finalization, one issued ticket. |
| checkout_status: ready | The event ticket, storefront, registration definition, sales window, and capacity passed the public fail-closed checks and a branded purchase path is available. |
| assignment_policy | at_checkout for one attendee per ticket unit; deferred_allowed for a multi-seat pass completed later. |
| Lunch bridge | Separate supervised occurrence included by a full-day camp option; not inferred from overlapping AM and PM times. |
| Participant add-on | Ordinary product or variant assigned to one attendee and retained as its own receipt line. |
| Recurring capacity peak | Highest selected-seat usage on one concrete instance; the series ceiling is not cumulatively consumed across dates. |
| Ticket preset | Reusable defaults copied into a versioned ticket-option snapshot rather than a live inheritance link. |
| Visual purchase rule | Bounded rule-set, group, condition, and action graph; management preview is explanatory and checkout evaluation is authoritative. |
| Physical seat lifecycle | Published venue layout → on-sale occurrence configuration → pricing-zone rule → temporary hold → ticket assignment → append-only inventory evidence. |
| Accessibility seat data | Structured wheelchair, transfer, companion, obstructed-view, and note attributes used for discovery and controlled seat selection. |
Expected result
Every active ticket option references an active event_ticket product, admits exactly the intended occurrences, consumes every required shared pool, rejects or waitlists excess demand, and reports price, units, seats, and merchandise separately.
Troubleshooting
- Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
- Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
- Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.
CentriPOS API explorer · API Center administration