Create and publish an add-on
1
Create it
Click Create add-on and name it. Like a ticket type, it is born a draft — invisible and without effect until published.
2
Bind its perks
On the add-on’s page, choose the perks it grants under Perks this add-on grants. Create the perks first on the Perks page — an add-on with no perks delivers nothing.
3
Publish
Click Publish and confirm. The add-on becomes available to add on top of a ticket at checkout.
Lifecycle — same as ticket types
Add-ons share the ticket type’s exact lifecycle: draft → open ⇄ closed → archived.- A draft is invisible to the public.
- Close sales stops new purchases without hiding history; Reopen resumes.
- Archive retires it; add-ons are never deleted, and restoring an archived add-on lands on Closed, never Open.
Rules to know
- The perks are the product. Attach the add-on’s value as perk bindings; if the workshop it admits to is a gated agenda session, gate that session on the same perk and the chain works end to end — see Perks.
- An add-on rides on a ticket. It is bought alongside a registration at checkout, not on its own.
- Free today. Add-ons carry no price yet; paid add-ons arrive with pricing later.
- A refund policy can be applied to an add-on, same as to a ticket type — see Refund policies.
- Add-ons can be bundled. A bundle can package a ticket type together with add-ons as one purchase.
- Every operation on an add-on is recorded in its log, so you can always see who published, closed or archived it.
Related
Perks
Define what the add-on grants.
Bundles
Sell a ticket and add-ons as one box.