Event editor

The event editor lets you load every detail of a show on a single screen and publish it when it’s ready. While in draft only you and your team can see it. The moment you publish, it appears on the public page, the sitemap and the /discover search.

Create an event

Tap Events → New event and fill in the basics:

• Banner (recommended 1600×900 px / 16:9). JPG, PNG, WebP or AVIF, max 5 MB. Used on the event page, on the share preview and in the /discover listing.
• Title and description in the active language. You can add translations for any supported locale later.
• Venue (free text — Foro X · Mexico City, etc.).
• Start and end + explicit timezone.
• Currency for the event (USD, MXN, COP, ARS, CLP, PEN, EUR…).
• Service fee (%) optional — added on top of the price the buyer pays and routed to your Stripe account.

The event is created as a draft — it’s not visible to the public yet.

Add ticket types

A draft cannot be published until it has at least one ticket type. Open the event and from the Ticket types section tap + Add ticket type.

Each type carries:

• Kind — entry (general admission), combo (entry + extra like a drink), seat (seat) or consumption (consumption charge).
• Name and description (optional), translated per locale.
• Price in the event currency. 0 = free ticket.
• Total capacity — how many units you can sell.
• Hide from public — optional, for guest list tiers or promos you don’t want on the public page. Existing QR codes still work even if you hide the type.

Tap Save and it shows up in the list, with its sold / capacity progress bar.

Ticket form on mobile

The editor is fully mobile: price / capacity inputs open the native numeric keyboard (inputMode="decimal" and "numeric"), forms stack vertically and primary buttons expand to full width.

Edit, hide or delete a type

Each card has three actions:

• Edit — opens an inline form with the current values. You can change price, capacity, translations and visibility. The kind is immutable after creation: changing it would break already-issued QRs.
• Hide / Show — visibility toggle for the public page. Useful to pause sales of a tier without losing the capacity or invalidating already-issued QRs.
• Delete — if the type has no sales yet, it’s removed. If you’ve already sold at least one ticket, we hide it instead (existing QRs remain valid). The UI warns you before confirming.

Lowering capacity

You can lower the capacity of a type, but never below what’s already sold. The API rejects that change with 422 and the UI shows the current sold so you can pick a valid number.

Sold and available

Each row in the list shows:

• Sold: N / capacity — paid and issued tickets against total capacity.
• Available: N — what’s left (capacity - sold).
• Green progress bar while stock remains; turns red when it reaches 0.
• Sold out badge when sold === capacity.
• Hidden badge when paused.

For full financials (revenue, channel attribution, list of orders with buyer info) use the Sales page.

Translations

Above the form there’s a locale picker Spanish · English. Switching tabs saves the active locale’s copy and loads (or creates) the new one. Translatable fields: title, description, venue, and name / description for each ticket type.

If you publish without translating a locale, the public page falls back to the event’s defaultLocale.

Publish and unpublish

• Publish (status: draft → live) — requires active Stripe Connect AND at least one visible ticket type. If either is missing the button stays disabled with a tooltip telling you what’s missing.
• Move to draft (status: live → draft) — removes the event from /discover and the sitemap. Public URLs stop working. Existing orders and issued QRs remain valid.

Event statuses

Status	In /discover	In sitemap	Accepts orders	How to reach
draft	No	No	No	Initial state
live	Yes	Yes	Yes	Tap “Publish”
draft (2)	No	No	No	Tap “Move to draft” on a live event
ended	No	No	No	Automatic when the end date passes
cancelled	Yes (badge)	Yes	No	You mark it manually

Coming soon

• Sale windows per type (validityFrom / validityTo) for early bird and late release — the schema already supports them, the form doesn’t expose them yet.
• Per-event discount codes.
• Recurring dates / series of shows.
• Seated venues (venue map).
• Clone ticket type.