Knowledge Center Blog
brightness_6
  • Theme
  • brightness_6 Auto
  • brightness_7 Light
  • brightness_2 Dark
language English EN (GB)
Language ✕
  • Dansk
  • Deutsche
  • Eesti
  • English
  • Español
  • Français
  • Hrvatski
  • Italiano
  • Latviešu
  • Lietuvių
  • Lëtzebuergesch
  • Magyar
  • Malti
  • Nederlands
  • Norsk
  • Polski
  • Português (BR)
  • Português (PT)
  • Română
  • Slovenčina
  • Slovenščina
  • Srpski
  • Suomi
  • Svenska
  • Türkçe
  • Čeština
  • Ελληνικά
  • Български
  • Русский
  • Українська
  • 中文 (香港)
  • 日本語
Log in
Developers Blog
Log in
Home chevron_right Organizers chevron_right Discounts chevron_right Policy rules explained
search Search

Policy rules explained

Learn how to configure discount titles, types, conditions, preview, and rule status for price policies and coupons.

description View as Markdown
auto_awesome Open with keyboard_arrow_down
  • ChatGPT
  • Claude

The discount editor is used for every rule in a price policy and every discount in a coupon. It defines the discount, the conditions that must be met before it applies, and how it appears to customers.

In a coupon, the editor is split across steps: Discount contains the type, value, and Applies to; Who gets it contains the conditions; and Checkout contains Title at checkout and the preview. In a price policy, a rule opens in its own view with all of these parts, plus Delete this rule and Done. Done only validates the rule and returns to the list; nothing, including turning on a rule, is saved until you select Create policy or Save changes.

You can also use the AI Assistant on this page to configure discounts. Click at the top of the page to open the chat window. For an overview of price policies and coupons, see Discounts overview.


Title at checkout

Title at checkout is the customer-facing label shown at checkout and on the customer's receipt instead of the word “Discount”. Choose a short, descriptive name, such as Group discount or Students, so customers immediately understand why their price changed.

A title is required for price policy rules and optional for coupon discounts. If you leave a coupon discount untitled, customers see “Discount”.

Discounts with the same Title at checkout are added together into one line at checkout and on the receipt. Give each discount a unique title so customers can tell them apart.


Discount type, value, and Applies to

Choose a Discount type, enter its value, then choose Applies to when that option is available.

  • Percentage — makes every seat in the order cheaper by the percentage entered. For example, a value of 20 gives 20% off each seat. A percentage always applies to each seat; 100% makes the seats free.
  • Amount off — subtracts a monetary amount from each seat or from the whole order.
    • Each seat — subtracts the amount from every seat, never reducing a seat below zero.
    • Whole order — subtracts the amount from the order total once.
  • Fixed price — sets a price for each seat or the whole order.
    • Each seat — each seat costs the value entered. A seat that already costs less keeps its regular price.
    • Whole order — the whole order costs the value entered when its regular total is higher.
  • Free ticket — enter a value in Buy. For every N matching seats in an order, one more seat is free; the cheapest matching seat is free. For example, Buy 3 makes one seat free for every four matching seats. This type has no Applies to setting.

For Amount off and Fixed price, monetary values are in the event's currency: entering 5 gives $5, €5, or whatever currency the event uses. Percentage discounts are not affected.

For Amount off and Fixed price, Applies to offers Each seat or Whole order. A percentage discount gives the same total discount per seat as it would for a whole order, so it always applies to each seat.

Per-seat discounts lower the price of each sold seat, so Statistics shows those seats at their discounted price. A Whole order discount keeps the individual seat prices at their regular price and appears as a separate order-level discount line in Statistics.


Conditions

Conditions are checks on an order, seat, event, or purchase. A discount without conditions applies to every order for the price policy's selected events, or to everyone who enters the coupon code.

Under Apply when, choose how multiple conditions match:

  • All are true — every condition must match.
  • Any is true — at least one condition must match.

Click Add condition to open a list of fields, grouped into Order, Seats, Event, and Purchase, with a short example for each field. The list has no search.

Quick add appears only while a discount has no conditions. It offers 4+ seats, Online only, Box office only, Students (price policies only), and Weekdays.

Seats conditions — Attendee type, Sector, Row, Seat number, Seat feature, and Seat price — are checked seat by seat. Each seat's discount applies only to seats that meet them. Number of seats and Order total always count the whole order. A Whole order discount covers the whole order as soon as one seat meets its conditions. For example, a Whole order Fixed price with a Sector condition prices the whole order, including seats in other sectors.

The available fields and operators are:

GroupFieldWhat it checksOperators
OrderNumber of seatsSeats in the order, for example 4 or moreis at least, is at most, is exactly, is not, is more than, is less than, is even, is odd
OrderOrder totalThe order total before discountsis at least, is more than, is at most, is less than
SeatsAttendee typeStudent, Child, Senior, or Person with disability; available for price policies only. When a turned-on rule has this condition, a type choice appears for each seat: customers choose online and the cashier chooses at the box office. The choice offers Standard plus the types those rules use. Customers see Students, Kids, Retired people, and People with disabilities; the editor calls them Student, Child, Senior, and Person with disability. Seats given a type get its discount. Entase does not check eligibility, so check it at the door. Coupons do not offer this condition for this reason.is any of, is none of
SeatsSectorA part of the hall; pick or type namesis any of, is none of
SeatsRowRow names on the seating chart, for example the first 5 rowsis any of, is none of, and the number operators
SeatsSeat numberSeat numbers, for example odd or even seatsis any of, is none of, and the number operators
SeatsSeat featureWheelchair space or Limited view; seating-chart seats onlyis any of, is none of
SeatsSeat priceThe seat's regular priceis at least, is more than, is at most, is less than
EventEventSelected events; this includes every date of those events, including dates added lateris any of, is none of
EventEvent dateWhether the event is before, on, or after a dateis before, is after, is on, is on or after, is on or before
EventEvent day of weekA day or days of the week, for example Monday to Thursdayis any of, is none of
EventEvent start timeThe event start time, for example matinees before 15:00is before, is from, is at
EventEvent day of monthA day from 1 to 31Number operators
EventEvent monthA month, for example Decemberis any of, is none of
PurchasePurchase dateThe purchase date, for example an early-bird dateis before, is after, is on, is on or after, is on or before
PurchasePurchase day of weekThe purchase day of the week, for example Tuesday dealsis any of, is none of
PurchasePurchase timeThe purchase time, for example a happy houris before, is from, is at
PurchasePurchase day of monthA day from 1 to 31Number operators
PurchasePurchase monthA purchase month, for example Januaryis any of, is none of
PurchaseDays before the eventHow early the purchase is made, for example at least 30 days before the eventis at least, is at most, is more than, is less than, is exactly
PurchaseHours before the eventHow close the purchase is to the event, for example at most 3 hours beforeis at least, is at most, is more than, is less than, is exactly
PurchaseSales channelWhether the seats are sold Online or at the Box officeis, is not
PurchaseBox office operatorWho sells the seats; an online sale counts as sold by the website it came fromis any of, is none of
PurchaseSegmentSales from a segment link or a segment selected at the box office; shown only when you have segmentsis any of, is none of

For fields that accept lists of numbers, enter values such as 1, 2, 3 or 1-6. Separate values with commas or spaces; 1-6 means 1 to 6. Row and Seat number lists also accept names such as A, B, or 12A, but ranges and number operators work only with numbers. The hint below the field shows “Read as: …”.

Event, Sector, and Box office operator compare names exactly as stored, including capital letters; commas and extra spaces do not matter. The Event condition finds events by title. Pick names from the suggestions, and update a condition after you rename an event, sector, or team member. To match online sales from one website with Box office operator, enter the site's address without www., for example example.com.

Values must be above 0, and a percentage can be at most 100. Buy must be a whole number from 1 to 100. You can add up to 30 conditions to a discount and up to 50 discounts or rules to a coupon or policy.

Days before the event and Hours before the event count whole days of 24 hours and whole hours, rounded down. For example, 3 hours and 40 minutes before an event counts as 3 hours. Event start time and Purchase time take whole hours from 00:00 to 23:00. is from includes that hour; is at matches only that exact time, so an event at 19:30 does not match is at 19:00.

Important: In a price policy, Event date compares only among the events selected in that policy's Events step. Anytime events have no start, so no condition on an event's date or time matches them — even with is none of or is not. This includes Event date, Event day of week, Event start time, Event day of month, Event month, Days before the event, and Hours before the event. All date and time conditions use the event's time zone.

Conditions saved with the old editor that cannot be displayed in the new editor remain shown as they were saved and continue to work. To edit one in the current format, choose an operator from its list. If its value fits, it becomes a regular condition with the same value; choosing another field replaces it with a new condition.

Tip: A segment discount is not secret: anyone can open a segment link. Use a coupon when you need a private discount.


Checkout preview and rules that are off

The Checkout preview uses an Example order, not your prices: its seats cost 20 in your currency. It shows 2 seats by default, or the number from a Number of seats condition; a Free ticket shows Buy + 1 seats. It assumes that the order meets the conditions. If the configured discount would not lower the example price, it shows a No saving warning. Compare a Fixed price with your real prices yourself.

A price policy rule can be turned off. When it is off, the editor states that customers do not get the discount and offers Turn on. Its settings remain saved until you turn it on again.

For how Entase chooses between eligible discounts at checkout, including coupon and price policy discounts, see Discount stacking explained.

Was this article helpful?
explore Organizers
  • Getting Started
  • Events & Program
  • Sharing & Embedding
  • Box office & Orders
  • Statistics
  • Balance & Payouts
  • Settings
  • Team
  • Stages
  • Tickets
  • Discounts
  • Segments
  • Personal Account
menu_book More in Discounts
  • Discounts overview
  • Creating a price policy
  • Attaching a price policy to an event
  • Creating a coupon
  • Discount stacking explained
  • Batches of coupon codes
  • Coupon limits: uses, seats, and once per customer
Learn how to Entase.
© 2026 Entase, Inc.

Entase

  • Events
  • Sign up

Platform

  • Pricing
  • Global reach
  • Integration
  • Marketing tools
  • Booking tools
  • Collaboration

Use cases

  • Theater and opera
  • Concerts and parties
  • Expos, fairs and festivals
  • Museums and attractions
  • Tours and experiences
  • Workshops and seminars
  • Fundraising
  • Tournaments

Knowledge center

  • Organizers
  • Attendees
  • Developers
  • Blog

Legal

  • Terms of use
  • Privacy policy
  • Cookie policy
search Questions? Search
auto_awesome LLM? Read llms.txt
support_agent Need help? Start chat