# Policy rules explained > Learn how to configure policy rules: customer-facing titles, discount values and levels, conditions, match logic, and rule management. A price policy is made up of one or more **rules**. Each rule defines a discount, the conditions that must be met before that discount applies, and how the discount is applied. Understanding every field lets you build precise, predictable pricing. You can also use the AI Assistant on this page to configure policy rules. Click AI assistant button at the top of the page to open the chat window. For full details about discounts, see [Discounts overview](/organizers/discounts/discounts-overview.md). For instructions on creating a policy before adding its rules, see [Creating a price policy](/organizers/discounts/creating-a-price-policy.md). --- ## Rule title The **Title** field is the customer-facing label shown on the customer's receipt when the discount from this rule is applied. Choose a short, descriptive name, such as *Group discount* or *Students*, so customers immediately understand why their price changed. --- ## Discount value, type, and level A discount has three inputs: **Value**, **Type**, and **Level**. - **Value** — enter the number for the discount. - **Type** — select how Entase interprets that number: - **%** — applies a percentage discount equal to the value entered. For example, a value of `20` gives 20% off. - **currency units** — applies a flat discount equal to the value entered. For example, if the value is `2` and the ticket costs `20 USD`, the discount is `2 USD`. - **currency units - fixed** — sets the final price to the value entered, regardless of the standard price. For example, if the value is `10` and the ticket costs `30 USD`, a `20 USD` discount is applied and the final price is `10 USD`. - **Level** — choose where the discount is applied: - **per-seat** — applies the discount to each seat in the order. - **per-order** — applies the discount to the whole order. For percentage-based discounts, use **per-seat** where possible. The discount has the same effect at either level, but per-seat discounts make the data in Statistics easier to read. **per-order** discounts are usually used with flat **currency units** discounts; however, use **per-seat** whenever possible. > **Important:** All discounts applied at the **per-order** level appear in Statistics as **Order discounts and fees** in the ticket breakdown sections. --- ## Conditions By default, a new rule has no conditions. A rule without conditions always applies because no checks are made against specific criteria. This is common for coupons, where the customer must enter a promo code, but it is bad practice for price policies because the system applies the discount automatically. To add conditions: 1. Click add button in the rule's **Conditions** section. 2. Select the conditions evaluation: **When ALL are true** or **When ONE is true**. - **When ALL are true** uses AND logic: every condition must match. - **When ONE is true** uses OR logic: at least one condition must match. 3. Set the condition's **Field**, **Operator**, and **Value**. 4. Click add button again to add more conditions if needed. The available condition fields are: | Field | Value or format | |---|---| | **Seats in booking** | Number | | **Customer status** | Dropdown: kids, students, retired people, disabled people | | **Seat feature** | Dropdown: suitable for handicaps, limited visibility | | **Sector** | Text or number | | **Row** | Text or number | | **Seat** | Text or number | | **Purchase - full date** | `YYYY-MM-DD` | | **Purchase - time (0-23)** | `H:M` in 24-hour format | | **Purchase - day of the week (1-7)** | Number `1`–`7` (Mon–Sun) | | **Purchase - day of the month (1-31)** | Number `1`–`31` | | **Purchase - month (1-12)** | Number `1`–`12` (Jan–Dec) | | **Purchase channel** | Dropdown: online, box office | | **Operator name** | Text | | **Order amount** | Number | | **Production title** | Text (event title) | | **Event start - full date** | `YYYY-MM-DD` | | **Event start - time (0-23)** | `H:M` in 24-hour format | | **Event start - day of the week (1-7)** | Number `1`–`7` (Mon–Sun) | | **Event start - day of the month (1-31)** | Number `1`–`31` | | **Event start - month (1-12)** | Number `1`–`12` (Jan–Dec) | Available operators depend on the field: - **equal to (`=`)** - **not equal to (`!=`)** - **greater than (`>`)** - **greater than or equal (`>=`)** - **less than (`<`)** - **less than or equal (`<=`)** - **is odd number** - **is even number** - **is any of these** — enter comma-separated values - **is none of these** — enter comma-separated values --- ## When to add more policy rules Add another rule when you need different discounts or when the required condition groups cannot be represented in one rule. For example, to give students a 10% discount and kids a 15% discount, create two rules. If both students and kids receive the same 10% discount, one rule can cover both groups. --- ## Best practices - **Keep rule titles short and clear.** The title appears on the customer's receipt, so use a customer-friendly label rather than an internal code. - **Use per-seat discounts where possible.** This makes Statistics easier to read, especially for percentage-based discounts. - **Add conditions to price policy rules.** A rule with no conditions applies automatically. - **Limit internal box-office coupons to the box office.** Coupons intended for internal box-office use only should always include a **Purchase channel** condition equal to **box office**. For coupon setup instructions, see [Creating a coupon](/organizers/discounts/creating-a-coupon.md). > **Tip:** Always test your configured rules by going through checkout on both the online channel and the box office. Confirm that the discount triggers as expected in each channel. --- ## Editing policy rules The policy rules management page lists all rules for the current price policy or coupon. - Use the **Enabled/Disabled** toggle on a rule to turn it on or off as needed. - Click edit button on a rule to edit it. - Click the delete button on a rule to remove it. Disabling a rule preserves its settings so you can enable it again later without reconfiguring it.