Discount codes — admin

Events → Discount codes.

Who opens it: whoever runs a season of events and hands out codes — to members, to a sponsor, to early birds. What they came to do: see every code at once, make a batch of them, and later find out which ones worked. What must be true when they leave: they know which codes are live, which are used up or over, and what the codes cost them.

Every code, across every event

A code still belongs to one event — you make one on the event's own Discount codes tab, as before. This screen lists them all together: the code, its event, whether it takes a percentage or an amount off, how many times it has been used against its limit, when it is valid (in the event's own time), and where it stands:

Filter by event, by state, or both. Edit and Deactivate work here exactly as on the event's tab, with the same checks — a percentage above 100 % is refused either way.

Who sees it: the people who can change events (Owners and Admins by default). A member whose role is limited to a group sees no codes: a code is the whole organization's, not one group's.

Many codes at once

Generate codes makes a batch of codes on one event — a hundred for a sponsor to hand out, say:

• How many (up to 1,000), a prefix such as SPONSOR-, and how many random characters follow it (at least 4). The random part never uses I, O, 0 or 1, so nobody misreads a code off a card.
• One use each unless you say otherwise, and one discount and one valid window for the whole batch.
• Name the batch ("Sponsor handout") so you can find it again.

Every code in a batch is new to your whole organization — none repeats a code any of your events already has. A batch is made whole or not at all. The list downloads as a CSV the moment the codes are made, with each code, its event, its discount, how many uses it allows and when it is valid, in the event's own time. Download a batch hands the same list over again later.

A list of working codes is worth money, so every download is written in the audit log with who took it. The Batch filter on the list shows one batch's codes and how many of them have been used.

Which codes worked

Events → Discount codes → the Redemptions tab. For whoever reads reports (Owners, Admins, Finance and Viewers by default).

Pick an event. The top of the page puts what its discounts cost beside what it took: the total before discounts, the discounts given, what was charged, and what has been refunded since — over every payment taken for the event, with a code or without. By code shows how many times each code was used and what it gave away.

Narrow it to one batch or one code to see each redemption: when the code was used (in the event's own time), which registration, who paid, which people it was for, the amount before and after, what was refunded, and where the payment stands. Export writes the same list as CSV or Excel.

Why "used" here and on the list can differ. The list counts a use the moment somebody checks out with a code, so the code is held for them. This report counts only payments that were taken. Somebody who checked out and never paid has used the code but is not in the report.

Every figure comes from the payments themselves: what Stripe says it received, and what the code took off when the checkout was made. In your own Stripe dashboard, each of those payments names the code, the amount before it and the discount — in its description and in its metadata (discount_code, amount_before_cents, discount_cents) — so the two can be read side by side. EntryWick works out the discount; Stripe only charges what is left.