Every training discount scenario

How to read the tables on this page

This page covers every type of condition that you can configure under Dashboard → Training courses → Pricing groups. Amounts are fictional examples excluding VAT. A course must be linked to the pricing group containing the rule; otherwise, none of that group's rules can apply.

Unless stated otherwise, the examples use a course costing €200 excluding VAT, held on 15 October 2026, with a registration made on 1 September 2026, which is 44 calendar days in advance.

A rule must contain at least one condition based on history, early registration or the course cut-off date. These are the seven possible combinations:

Leaving all three conditions empty does not create a general discount: that configuration is rejected.

Choosing a percentage or fixed amount

Both discount forms apply to the unit price for the date. A date-specific price replaces the general course price when one has been entered.

The percentage must be positive and cannot exceed 100%. A fixed amount must be positive. A discount never makes the price negative and does not apply to a zero or negative target price.

Deciding which courses are counted

History is found through the billing customer's email address, ignoring case, within the current organisation. The participant's email is not used. Several customer records carrying the same billing email may therefore contribute to the same history.

The same date is counted once, even when several participants or registrations are associated with it. The date currently being priced is always excluded. Both past and future dates may be counted when they pass the rule's filters.

The required payment

A historical registration must be linked to a payment request containing at least one payment with Completed status. The calculation checks for that status, not full settlement of the balance, the amount paid, attendance or the course price.

A date passing this first check must still satisfy the rule's time window and pricing-group scope. “Counted” therefore does not mean “settled in full”, “attended” or “completed”.

The three counting methods

Assume three eligible dates: 2 days and 14 hours, 1 day and 7 hours, then 1 day and 7 hours.

For days and hours, the date-specific duration takes priority, followed by the course duration. A missing duration contributes zero; it is not derived from the start and end times. Once the payment condition is met, the price — even zero — does not change the duration counted.

The three group scopes

Assume one date in the same pricing group, one in another group and one with no group.

The two scope options are mutually exclusive: they cannot be enabled together.

The four time windows

The window is centred on the course date being priced, here 15 October. Both boundaries are inclusive and an empty field means “unlimited” on that side. The fictional history contains 1 September, 1 October and 20 October.

Entering only Past days does not remove future dates because the future boundary remains unlimited. Use zero to close one side of the window explicitly.

Using a condition without history

Select No history criterion when a discount depends only on the registration timing or the course date.

The cut-off concerns the course date, not the day on which the customer registers. An advance threshold of zero is met by a registration on the day of the course, but not by a later registration.

Combining several conditions in one rule

Conditions within one rule use AND logic. Consider a €30 fixed discount, a minimum history of 2 dates, 30 days' advance and a cut-off of 31 October 2026.

Time-window and group filters are applied to the history before its value is compared with the threshold.

Resolving several rules

Eligible rules are never cumulative. Bookelio calculates their values from the same unit price and keeps the financially largest discount, irrespective of which rule has the highest threshold. If values tie, the rule listed first wins.

In this example, the discounted price is €175 excluding VAT, not €130: the €20, €25 and €25 discounts are not added together.

Moving from unit price to registration total

The rule first produces a suggested price per participant. That result is multiplied by the participant count, after which the customer's VAT is calculated. An excluding-VAT amount entered manually by a manager replaces the suggested total; it does not alter the rule or history.

The new participant count multiplies the awarded discount; it does not help reach a history threshold. Ten participants registered together still represent a single date in a future history calculation.

Recognising every no-discount scenario

Reproducing a scenario in the simulator

Open the discount simulator from Training courses, choose the customer and target date, then set the registration date. Select the history dates to test and inspect each rule's counted value, window, group, days in advance, and acceptance or rejection reason.

The option that treats dates as paid is only a simulator assumption. It records no payment. For the detailed operation of the tool and real history, read Understanding and testing training discounts.