Skip to main content

Dynamic Pricing

Dynamic Pricing allows you to automatically adjust the price of a race entry based on their age.

Written by Angus Williams

This feature is useful for creating discounts, surcharges, or conditional pricing rules without needing to create multiple race categories.

For example, you could:

  • Offer discounted entry for participants under 25

Note if you are a triathlon, this feature can’t be used because the age restrictions are based on the end of the year and not the date of the event


How Dynamic Pricing Works

Dynamic Pricing is made up of two parts:

1. When

This section defines the condition that must be met.

You’ll select:

  • Field – Age on Day

  • Comparator – The rule logic (for example: equals, greater than, contains)

  • Value – The value that triggers the pricing change

2. Then

This section defines how the race price should change when the condition is met.

You’ll select:

  • Increase/Decrease – Whether the price goes up or down

  • Absolute/Percentage – Whether the change is a fixed amount or a percentage

  • Amount – The value of the adjustment


Example Scenarios

Example 1: Junior Discount

Offer a £10 discount for participants under 18.

When

  • Field: Age

  • Comparator: Less Than

  • Value: 18

Then

  • Decrease

  • Absolute

  • £10.00

Result:

Participants under 18 will receive £10 off the race entry price.


Important Notes

  • Dynamic Pricing rules apply automatically during registration.

  • Multiple pricing rules may stack depending on your event configuration.

  • Percentage adjustments are calculated from the current race price.

  • We recommend using separate races or ticket types for major pricing differences where possible.

  • Always test pricing rules before opening registrations publicly.


Best Practices

Keep Rules Simple

Using clear and straightforward pricing rules reduces participant confusion and minimises support requests.

Test Before Going Live

Avoid Overlapping Rules

Too many overlapping conditions can produce unexpected pricing outcomes.

Did this answer your question?