# Publishing (/docs/live-events/publishing)



An event starts life as a **Draft**. Nothing about it is public: the storefront link returns
"not found", no tickets can be held, and you are free to change anything. **Publishing** flips it
to **Published**, which is what makes the public page at `resyevents.com/e/{slug}` resolve and
what allows buyers to start holding and paying for tickets.

Publish from the event detail page: the green **Publish** button sits in the header while the
event is a draft. Once it succeeds, the button is replaced by a green banner with the public link
and a **Copy link** button.

The Publish Checklist [#the-publish-checklist]

Publishing is not just a status flip. Resytech runs a set of checks first so that nothing
half-configured can go on sale. The checks run in order and stop at the first failure, so fixing
one problem can reveal the next.

| Check                   | What it wants                                                                                                                        | If it fails                                                                                                           |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
| **Still a draft**       | The event has not already been published or cancelled.                                                                               | You are told it is already published, or that only a draft can be published.                                          |
| **Event has not ended** | The event's end time is still in the future.                                                                                         | Blocked. Move the dates on the **Details** tab if the event is being repeated.                                        |
| **Something to sell**   | At least one ticket type that is **active** and has a capacity above zero.                                                           | "Add at least one active ticket type before publishing." Add or reactivate a tier on the **Tickets & Add-ons** tab.   |
| **Refund policy**       | A refund policy is chosen on the **Pricing** tab. If you picked "Refundable until a cutoff", the cutoff hours must be filled in too. | Blocked with a prompt to choose the policy (or set the cutoff).                                                       |
| **Payouts ready**       | Your organization's Stripe Connect onboarding is complete and charges are enabled.                                                   | A red banner appears with a **Finish payout setup** link. See [Fees and Payouts](/docs/live-events/fees-and-payouts). |
| **Listing fee paid**    | Flat-listing-fee events only: a successful listing-fee payment that covers the event's **current** capacity.                         | The listing-fee payment window opens automatically so you can pay (or top up) and retry.                              |

Most failures appear as a short message at the top of the screen. Two of them get more help:

* **Payouts not ready** stays on screen as a banner, because the fix lives on another page and a
  passing message cannot carry a link.
* **Listing fee unpaid** or **capacity outgrew the fee you paid** opens the **Listing Fee**
  payment window immediately, since paying is the fix.

Ticket types that do not count [#ticket-types-that-do-not-count]

Only ticket types that are marked active *and* have a capacity greater than zero satisfy the
"something to sell" check. A tier you deactivated, or one left at a capacity of zero, is invisible
to the check. Add-ons never satisfy it either: an event needs tickets, not just extras.

Refund cutoff [#refund-cutoff]

Choosing **All sales final** is enough on its own. Choosing **Refundable until a cutoff** also
requires the number of hours before the event start at which refunds close. That value is what
[Orders and Refunds](/docs/live-events/orders-and-refunds) enforces later when a buyer or your
staff requests a refund.

What Happens at the Moment You Publish [#what-happens-at-the-moment-you-publish]

* The event's status becomes **Published** and its public page goes live.
* On the **per-ticket fee** model, the platform fee per ticket is **frozen onto the event** at its
  current value. Later changes to fee configuration never re-price an event that is already
  selling.
* On the **flat listing fee** model, no per-ticket fee is charged at all, because the fee was paid
  up front.

What Stays Editable, and What Is Frozen [#what-stays-editable-and-what-is-frozen]

Publishing does not lock the event down. Most of it stays editable so you can fix a typo, swap a
poster, or open more capacity while tickets are selling.

**Still editable after publish**

* Name, description, poster, and gallery images
* Venue details, dates, doors-open time, and the sales window
* Storefront theme
* Tax rate, refund policy, and refund cutoff
* Ticket types and add-ons: prices, per-order limits, active state, and capacity

Capacity has one floor: a ticket type or add-on total can never be dropped below what has already
been sold or is actively held in someone's cart.

**Permanently frozen once published**

| Frozen                     | Why                                                                                                                                                                                                                                                                                                 |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **The public link**        | The slug is generated from the event name and city while the event is a draft, and stops changing at publish. Renaming a live event changes the page's title but not its address, so links already shared keep working.                                                                             |
| **The monetization model** | Per-ticket fee versus flat listing fee, and the "pass fees to buyer" toggle, are locked. Buyers who already paid did so under specific terms, and changing the model would re-price the event underneath them. The Pricing tab shows the model as read-only text with the frozen per-ticket amount. |
| **The time zone**          | Once tickets exist, a later venue edit no longer re-copies the venue's time zone onto the event, so displayed show times never shift under a ticket holder.                                                                                                                                         |

If you need a different link or a different fee model, create a new event rather than trying to
change a published one.

There Is No "Unpublish" [#there-is-no-unpublish]

A published event cannot be pulled back to draft. Tickets have been issued against it, so the
only way off the storefront is to **Cancel Event**, which voids every ticket and stops sales
immediately. That flow, including the choice between voiding tickets only or refunding every paid
order, is covered in [Orders and Refunds](/docs/live-events/orders-and-refunds).

If you just want to stop selling without cancelling, close the sales window instead: set the
sales end time on the **Details** tab. The page stays up, the tickets stay valid, and buying stops.

Related [#related]

* [Creating Events](/docs/live-events/creating-events)
* [Ticket Types and Add-Ons](/docs/live-events/tickets-and-add-ons)
* [Fees and Payouts](/docs/live-events/fees-and-payouts)
* [The Storefront](/docs/live-events/storefront)
* [Orders and Refunds](/docs/live-events/orders-and-refunds)
