Events is a controlled-rollout workspace. When the feature is enabled for the selected business, its records remain tenant-bound and role-controlled. An offering describes what is sold; occurrences describe when attendance happens; ticket options connect normal CentriPOS products of type event_ticket to one or more occurrences.

Before you beginConfirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.

Step by step

  1. Open Events → Overview and confirm the business and timezone shown in the operating-context bar. If the Events navigation is absent, the scheduled-offerings entitlement or rollout is not enabled for this business.
  2. Choose New offering. Select the operating pattern that best describes the program: one-off event, camp, class or after-school series, conference, appointment-style offering, or another merchant-defined event kind. The pattern organizes the setup; it does not create a separate database or payment system.
  3. Enter a stable public slug, name, short summary, full formatted description, delivery format, status, and visibility. Public appears in eligible published feeds, Unlisted requires the direct published link, and Private stays out of public discovery.
  4. Set the offering timezone before creating occurrences. Enter the venue and structured location, online meeting URL for online or hybrid attendance, support email and phone, registration opening and closing times, and optional age boundaries.
  5. Add a primary image with meaningful alt text, then use Assets for approved images, documents, attachments, maps, video links, or downloads. Choose Public only for files any visitor may receive. Choose Attendees only for files intended for an authorized registration portal. Forms, waiver evidence, medical details, private notes, and ticket credentials are never publication assets.
  6. Configure portal settings for the purchaser and participant experience. Decide which registration summary, calendar link, ticket, instructions, and public attachments an authorized household can see. Portal settings do not override contact authorization or make sensitive registration answers public.
  7. Create one or more occurrences in the builder. Use one occurrence for a one-off event, daypart occurrences for a camp, normalized room-and-track sessions for a conference, or an IANA-timezone recurrence rule for a class or after-school series. A recurring occurrence is the authoring series; CentriPOS materializes each actual date as a durable instance before date-specific enrollment, admission, or calendar evidence.
  8. Create ticket options only after the required event_ticket products exist. Connect each ticket option to its applicable occurrences and capacity pools, then set its sale window, order minimum and maximum, seats per ticket, eligibility, portal behavior, and display order.
  9. Review the offering from Overview before publishing: content, timezone, occurrences, exceptions, ticket products and prices, shared capacity, registration window, assets, feed placement, portal exposure, and calendar projection must agree.
  10. Publish only after a complete internal registration test. A Published offering can enter selected public feeds and downstream integrations; Draft and Scheduled records remain staff-controlled, and Cancelled or Archived records must not be advertised as bookable.
  11. After launch, use Registrations, Check-in, Waitlist, Event reports, Publishing, Configuration, and Master calendar as connected views of the same records. Configuration authors versioned forms and waivers, participant add-ons, people and roles, rooms, tracks, and audience-scoped assets. Do not create duplicate products or contacts to compensate for a filter or status problem.
  12. For a recurring schedule, use Manage exceptions to cancel, reschedule, or modify one generated date while preserving its original series identity. Use staged reconcile-series for a broad series rewrite; do not shift already materialized dates by a fixed UTC offset across daylight-saving boundaries.
  13. Create a reusable venue before assigning a physical location. Store its structured address, country code, map provider/place identity or approved map URL, coordinates when authorized, public contact details, arrival instructions, accessibility summary, and valid IANA timezone. An occurrence can deliberately override the offering venue for one room, day, or campus.
  14. For native private event files, managers upload at most 25 MiB into the protected event-assets store. Native files use Attendees or Staff visibility only. Authorized attendees receive a branded five-minute download URL; public and integration payloads never receive a bucket name, object path, Supabase hostname, or project URL.

Screen and contract reference

Control or areaWhat it means
EventsEntitlement- and role-controlled workspace for offerings, calendar, registration, attendance, reporting, and publication.
OfferingFull-content program or event definition shared by its dates, tickets, registrations, assets, publication, and portal settings.
Event kindMerchant-defined classification such as camp, conference, class, after-school program, appointment, or one-off event.
Delivery formatIn person, online, or hybrid.
VisibilityPublic, unlisted, or private discovery boundary.
OccurrenceAuthored attendance block or recurrence series with schedule, location, status, and enrollment policy.
Occurrence instanceDurable concrete date under an occurrence, preserving original_start_at when its effective time changes.
event_ticket productNormal CentriPOS product type used for a sellable ticket or registration choice.
Ticket optionOffering-specific configuration that links one event_ticket product to occurrences and capacity pools.
AssetsImages and approved public attachments associated with an offering or occurrence.
Portal settingsAuthorized customer-portal presentation rules; never a substitute for identity and privacy checks.
PublishMakes an eligible offering available to selected publication feeds and event integrations.
Controlled rolloutFeature and API operations remain unavailable unless the selected business has been explicitly enabled.
ConfigurationOffering-level manager for forms, waivers, add-ons, event people and roles, rooms, tracks, and assets.
Manage exceptionsStaff editor for one-date cancellation, reschedule, or modification beneath a recurring series.
Reusable venueStructured Place record shared across offerings, occurrence overrides, maps, metadata, calendar locations, layouts, and reporting.
Asset audiencePublic for anonymous feed delivery, Attendees for an authorized registration portal, or Staff/private when the file must not leave operations.
Native event assetManager-only protected upload, at most 25 MiB, stored outside anonymous publication and delivered through a short-lived branded capability URL.

Expected result

The selected business has one coherent offering whose content, occurrences, ticket products, capacity, registration window, publication, portal, and calendar settings pass a controlled internal registration before publication.

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.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.