Discounts & ticket rules

A discount code is a coupon buyers type at checkout to lower their order's total. To create one, choose Tickets → Discounts & Codes in the sidebar, then New discount. Type a Name, keep Coupon as the Type, and choose Create. Checkout only accepts coupons, so use that type for every code. The coupon's edit page opens.

• Code: what buyers type, like SAVE10. Checkout ignores letter case. A coupon with no code can't be redeemed.
• Base discount: % off or $ off, and the amount. New coupons start at 10% off. A percentage comes off the order's tickets, at their early-bird price when there is one, plus their add-ons.
• Flat applies: for $ off only. Once per order (the default) takes the amount off once, and Per ticket takes it off for each ticket.
• Max discount: the most the code takes off one order. Leave it blank for no cap.

No discount takes off more than the tickets and add-ons cost. The switch at the top of the edit page marks the coupon Active or Inactive, and checkout refuses inactive codes. Nothing on the edit page is kept until you choose Save. A coupon works only once you tick it onto tickets in the Tickets section of each event's editor.

By default, Tickets appears in the sidebar for the Owner, Admin and Manager roles. To change who sees it, see Roles and permissions.

Discount codes and ticket rules are set up in different places, and checkout combines them in a fixed order.

• Discount codes belong to the project. You create a code once under Tickets → Discounts & Codes, then tick it onto each ticket that accepts it, in any event. A code never works on a ticket it isn't ticked onto.
• Ticket rules belong to one event. In the event editor, open Ticket Rules and turn on early-bird pricing, donations, access-code tickets, group purchasing or bundles. Each feature you turn on gets a section of the event editor, where you set it up for that event only.
• Batched releases belong to one event too. The Batched Releases section is always in the event editor, under Tickets.

At checkout, early-bird pricing lowers each ticket's price first. A discount code then comes off that price plus add-ons, and a group discount comes off the tickets alone. A donation is added last, and no discount reduces it. A buyer can apply one code per order. Bundles take none of these: no early-bird price, code, group discount or donation.

When the discounts bring an order's total to zero, the buyer confirms it without a payment step.

Two cards on a coupon's edit page decide when the code works and how much it gives. Open the coupon from Tickets → Discounts & Codes, and choose Save when you're done.

Eligibility sets when the code works at all. When an order fails one of these, checkout refuses the code rather than giving a smaller discount.

• Min. tickets and Max. tickets: how many tickets the order needs. Blank means no limit.
• Valid from and Valid until: when the code starts and stops working. Blank means it works straight away and never expires.

Discount Rules change the amount by quantity or date. Choose Add rule, or Start from a preset for a filled-in rule: Buy 3 or more gives 15% off from 3 tickets, Buy 5 or more 25% off from 5, Big spender (10+) 30% off from 10, and Last 7 days before the event 20% off. That last preset comes without dates, so set them yourself.

• Each rule has a name, Min. tickets, Max. tickets, Valid from, Valid until and its own Discount. A $ off rule is taken Per order or Per ticket.
• Checkout reads the rules from the top and uses the first one that matches the order. When none matches, the base discount applies, so a rule never refuses a code.
• Drag a rule, or use its arrows, to change the order, and put the most specific rule first. The trash icon deletes a rule.

When a buyer changes the quantity after applying a code, checkout checks the code again, so a different rule can apply, or the code can be refused.

Tickets → Discounts & Codes lists the project's discounts, newest first, with each one's type, a summary of its code and amount, and its status. Filter by status (All Statuses, Active or Inactive) or by type, or search by name. The list shows 25 discounts a page; choose 10, 50 or 100 at the bottom.

Click a discount to open its edit page. Each row's ⋯ menu has Edit, Deactivate (Activate for an inactive one) and Delete.

• Deactivate and Activate save straight away. Checkout refuses an inactive code on every ticket it's ticked onto, until you activate it again.
• Delete asks you to confirm first. The code stops working on every event, and Events can't restore it.

To let buyers use a discount code on a ticket, open the event in the event editor and open Tickets. In the ticket's ⋯ menu, choose Edit, tick the codes under Discount codes, and choose Save. The list shows every coupon in the project with its code and amount, and marks inactive ones Off. Clear unticks them all.

Codes are set per ticket, so one ticket can accept several codes while another on the same event accepts none. The ticked codes show on the ticket in the Tickets section. For the ticket's other settings, see Adding tickets to an event.

At checkout, a ticket that accepts at least one code shows a Discount code box. The buyer types the code and chooses Apply, or presses Enter. An accepted code shows as applied, with Remove beside it, and the total gains a Discount line naming the code. There's no code box on a ticket with no codes, on a bundle, or in Express Lane.

Ticket rules are checkout features you turn on for one event. In the event editor, open Ticket Rules and turn on the switch for each feature the event uses. Each switch saves straight away and changes only this event.

• Early-bird pricing: a lower price while a window is open. Adds the Early-bird section.
• Donations: a gift buyers can add at checkout. Adds the Donations section.
• Access-code tickets: tickets hidden until a buyer enters a code. Adds the Access Codes section.
• Reserved seating: a block of tickets held back from public sale. Adds the Reserved Seating section, covered in Tickets.
• Group purchasing: one order for several attendees, at a group discount. Adds the Group Orders section.
• Bundles: several tickets sold together. Its section opens only from Configure.
• Batched releases: the Batched Releases section is always in the event editor, and waves work whether this switch is on or off.

Once a feature is on, choose Configure beside it to open its section. The section joins the event editor's list, under Tickets, once you reload the page.

Turning a feature off stops it at checkout and keeps its settings for when you turn it back on. Turning off Access-code tickets shows the event's hidden tickets to everyone.

Early-bird pricing takes an amount off every ticket on an event while its window is open. In the event editor, turn on Early-bird pricing in Ticket Rules, then open Early-bird. Choices save as you make them, and number and text fields save when you click away.

• Discount type: Percent off (the default) or Flat amount.
• Discount % or Amount off: how much comes off each ticket's price. It never takes more than the price itself.
• Starts and Ends: the date and time the window opens and closes. Leave either blank to keep that end open.
• Note: for your team. Buyers don't see it.

The section starts at 15% off with no start or end, so turning on early-bird pricing discounts every ticket straight away, until you set Ends or turn it off.

The event page keeps showing each ticket's full price. At checkout, the total shows the saving as an Early bird line, such as Early bird (15% off). Early-bird pricing doesn't apply to bundles, and a discount code or group discount comes off the early-bird price.

Donations add an optional gift to an order at checkout. In the event editor, turn on Donations in Ticket Rules, then open Donations. Switches save straight away, and text fields save when you click away.

• Allow custom amount: on by default. Adds a box where buyers type their own amount.
• Cause: what the donations support, like Community scholarship fund.
• Suggested amounts: the amounts buyers pick with one click, separated by commas. They start as 5, 10 and 25.
• Prompt: the heading over the amounts. With no prompt, buyers see Support followed by the cause, or Add a donation when there's no cause either.

At checkout, the buyer clicks an amount (clicking it again clears it) or types one in the Other box. The donation is added once per order, whatever the quantity, and shows as a Donation line in the total. Discount codes and group discounts don't reduce it. Events records the donation and its cause with the order. Bundles don't offer a donation.

An access code hides chosen tickets from the event page until a buyer enters the code, for guest lists and invite-only tickets. In the event editor, turn on Access-code tickets in Ticket Rules, then open Access Codes and choose Add code.

• Code: what buyers type, like VIP2026. It's required. Letter case and spaces at either end don't matter.
• Label: an optional note for your team.
• Unlocks these tickets: click each ticket the code reveals. Add the tickets in the Tickets section first.

Choose Add code to save it. The pencil edits a code, and the trash icon deletes it after you confirm; a deleted code can't be restored. One code can reveal several tickets, and a ticket stays hidden while any code lists it. Deleting a ticket's last code shows that ticket to everyone, and so does turning off Access-code tickets.

When an event has hidden tickets, its ticket list on the event page shows a Have an access code? box with an Unlock button. A right code adds its tickets to the list until the buyer reloads or leaves the page. A wrong one shows That code isn't valid for this event. Events checks the code again when the order is placed.

Group purchasing lets one buyer order tickets for several attendees in one payment, at a group discount. In the event editor, turn on Group purchasing in Ticket Rules, then open Group Orders. Number fields save when you click away, and ticket choices save as you click them.

• Minimum seats: the quantity at which an order becomes a group order. It starts at 5.
• Maximum seats: the most tickets one order can hold. 0, the default, allows up to 50.
• Group discount %: what comes off the tickets in a group order. It starts at 10%.
• Eligible tickets: All tickets (the default), or click the tickets that can be bought as a group.

Without group purchasing, one order holds up to 10 tickets. With it on, an eligible ticket's quantity goes up to Maximum seats. Once the quantity reaches Minimum seats, checkout asks who the tickets are for, with a name and a valid email for each attendee. The group discount comes off the tickets at their early-bird price, if any, and shows as a Group discount line. Add-ons and donations aren't discounted, and a discount code still applies on top.

Events records a separate order for each attendee under their email, so each one finds their own ticket in the Members portal. Bundles can't be bought as a group.

A bundle sells several of an event's tickets together as one purchase, such as a weekend pass. In the event editor, turn on Bundles in Ticket Rules and choose Configure beside it. That's the only way into the Bundles section, which isn't in the event editor's list. Then choose Add bundle.

• Bundle name: required.
• Description: shown to buyers under the bundle's name. With none, buyers see how many tickets it holds.
• Bundle items: choose Add Item, then pick a Ticket and its Qty. A bundle lists each ticket once.
• Pricing: Fixed price (the default) with a Bundle price, or Sum of items, which adds up the tickets' listed prices.
• Bundle available: on by default. Turn it off to stop selling the bundle without deleting it.

Choose Add bundle to save it. Each bundle in the list has its own available switch, a pencil to edit it, and a trash icon that deletes it straight away, without asking.

On the event page, each available bundle with at least one item appears in the ticket list with its price. Buying one uses up stock of every ticket in it, so the order fails when any of those tickets has no room left. Bundles get no early-bird price, discount code, group discount or donation. Bundles made under Tickets → Bundles in the sidebar aren't attached to events, so build the bundles you sell in the event editor.

Batched releases split one ticket's stock into waves that go on sale in order, such as 100 tickets at first and 100 more once those sell out. In the event editor, open Batched Releases, under Tickets. It lists the event's tickets: choose Split into waves on one.

• For a ticket with a set quantity, type the Tickets in wave 1, and wave 2 gets the rest. For an unlimited ticket, type a size for each wave.
• Under When does wave 2 open?, choose After wave 1 sells out (the default), On a specific date or When I say so.
• After a sell-out, Wait after the sell-out sets how many days to wait. 0 opens wave 2 straight away.
• On a date, Wave 2 opens on takes the date and time.

Choose Start selling in waves. The waves save straight away, and the ticket's quantity becomes the total of its waves. To add more waves or change them, choose Edit waves on the ticket.

When the event has more than one ticket, Apply to multiple tickets at once splits every ticket without waves into two halves, with wave 2 opening after wave 1 sells out. The starting size of each wave for unlimited tickets, and the starting wait, come from the Defaults on Tickets → Batched Releases in the sidebar: 100 tickets and 0 days unless you change them. When Enable batched releases is off there, the section shows a warning, but the waves you save still apply at checkout.

To change a ticket's waves, open Batched Releases in the event editor and choose Edit waves on the ticket. Each wave has a name, a number of tickets, and a gate that decides when it opens:

• On Sale now: open straight away. Wave 1 starts with it.
• After wave 1 sells out, numbered for the wave before it: opens once that wave sells out, after the number of days you set.
• On a date: opens at Opens on, and closes at Closes (optional) when you set one.
• I'll open it: hidden until you turn on its switch, and hidden again when you turn it off.

Each wave also has Open now, for a wave that's still waiting, Pause and Resume, which hide it from buyers for a while, arrows to sell it earlier or later, and a trash icon. Add another wave adds 50 tickets that open once the last wave sells out.

Edits wait, marked Unsaved edits, until you choose Save waves, and Discard drops them. Every wave needs at least 1 ticket, and every dated wave needs its date. Saving sets the ticket's quantity to the total of its waves.

Remove waves turns the ticket back into one pool: choose it twice to confirm. Copy to other tickets gives the tickets you tick the same waves, replacing theirs. Apply to multiple tickets at once copies one ticket's waves, or removes waves, across several tickets.

Waves sell in order. Every sale of a ticket counts against wave 1 until it's sold out, then against wave 2, and so on. Buyers can buy only from waves that are open, so the quantity they can choose stops at what's left in the open waves.

On the event page, a ticket with waves shows a line under its name: which wave is on sale and how many are left in it, when the next wave opens, or that all waves have sold out. While nothing is left in its open waves, the ticket shows Paused in place of its price and can't be bought.

Events checks the waves again when an order is placed and refuses an order the open waves can't cover. For a paid ticket, checkout tells the buyer the wave is sold out, with the next wave's opening date when it has one, before they pay.

In the event editor's Batched Releases section, each wave shows its status: On Sale, Opens with a date, Waits for the wave before it, Not opened yet, Paused, Closed or Sold out. The figures at the top count the event's tickets in waves, the tickets waiting for later waves and the tickets sold so far.

When checkout refuses a discount code, the buyer sees a message that names the reason.

• That code isn't valid: no active coupon with that code is ticked onto this ticket. The coupon is inactive or deleted, the code is misspelled, or the coupon isn't ticked onto the ticket the buyer chose.
• This code isn't active yet: it's before the coupon's Valid from.
• This code has expired: it's after Valid until.
• This code needs a larger quantity: the order has fewer tickets than Min. tickets.
• This code can't be used on this many tickets: the order has more than Max. tickets.

To fix it:

1. Choose Tickets → Discounts & Codes in the sidebar and open the coupon.
2. Check its Code, the Active switch and its Eligibility, then choose Save.
3. In the event editor's Tickets section, open the ticket with Edit and check the coupon is ticked under Discount codes.

You turn on a feature in Ticket Rules, or add or change a ticket in Tickets, and another part of the same event doesn't show it. The feature's section is missing from the event editor's list, or the switch shows as off when you come back to Ticket Rules, or a ticket is missing from Access Codes, Group Orders, Bundles or Batched Releases.

Each of these sections saves your change straight away, but the rest of the event editor keeps the event as it was when you opened it, until the page reloads. Going back to All Events and opening the event again doesn't refresh it. Saving in a section that still shows the old version writes the old version back, so a switch you turned on can turn off again, and edits to tickets or waves can be lost.

1. Reload the page in your browser. The event editor reopens on the same event and section.
2. Check that your earlier change is there, and redo it if it isn't.
3. From then on, reload after each change in Ticket Rules, Tickets or Batched Releases before you save in another of those sections.