Bookitive
Tickets

Discounts

Promo codes — percent or fixed amount, validity windows, usage limits, derived statuses, and why redeemed codes pause instead of delete.

Not verified yet

Discounts are promo codes buyers type at checkout: SPRING10 for 10 % off, CREW for 200 Kč off a partner order. They live per event under Discounts in the event sidebar.

Creating a code

A code has:

  • The code itself — type your own or hit the generator for a random one; copy it to the clipboard right from the list.
  • Type and value — a percentage or a fixed amount off, applied to the whole order.
  • Validity window — optional start and end; outside it the code politely refuses.
  • Usage limit — how many orders may redeem it; blank means unlimited.
  • Internal note — who got this code and why; never shown to buyers.
  • Paused — a switch to stop the code without deleting it.

Status is derived, not set

The list computes each code's status from its own rules — there is no status to manage by hand:

StatusWhy
ActiveInside its window, under its limit, not paused.
ScheduledIts start date hasn't arrived yet.
PausedYou switched it off.
ExpiredIts end date passed.
ExhaustedThe usage limit is used up.

What buyers experience

The checkout has a promo-code field. A valid code previews its effect on the total before ordering; an unknown or inactive code says so, and an exhausted one tells the buyer it's been fully redeemed — no silent failures, no support tickets asking "did my code work?".

Behaviour and edge cases

  • Redeemed codes can't be deleted — orders reference them, and your reporting needs them. Pause instead; deleting stays available for codes that were never used.
  • Codes stack with price phases, not with each other — one code per order, applied to whatever the current phase price is.
  • The list shows impact — redemptions and revenue effect per code, so you know whether INFLUENCER15 actually sold anything. Deeper breakdowns live in Sales analytics.
  • Codes are event-scoped. Running the same campaign across several events means creating the code in each — duplicating an event carries codes over.

On this page