Understand ticket price locks, discounts, inventory and gift components

In GiveCampus Events, available controls depend on your permissions and the interface used by your institution.

Ticket-type price and fair-market value cannot be changed once non-preview, non-incomplete tickets have been issued for that type. Do not register staff at zero and plan to raise that same ticket type's price afterward. Configure the intended public price first and evaluate an appropriate promo code or separate scoped ticket option for complimentary guests.

Promo codes support dollar/percentage discounts and start/end dates, with usage limits where configured. That can support a time-bounded discount approach, but is not proof of an automatic scheduled change to a particular ticket type's stored price. Check which items the discount applies to before describing an early-bird setup. This article does not mean a universal selected-ticket-only automatic price schedule.

The ticket-type form's maximum available quantity is event-wide inventory, explicitly not a per-registration limit. Setting it to two does not give every registrant two free tickets. A first-two-free-plus-paid-extras rule needs a separately package/promo/guest configuration; do not assume it from the inventory field.

The product's ticket gift-component calculation is price minus fair-market value, floored at zero. An undiscounted 500 ticket with FMV zero therefore has a 500 gift component. Registration-level discounts, packages and add-ons can affect the final totals. Event reporting uses configured ticket FMV and ticket gift designations separately. Verify those settings; a reporting designation is not confirmation that money reached a particular bank/ledger account, and these product calculations do not determine a donor's legal tax treatment.