Skip to main content

How to Use Fares

Learn how to apply different fare types effectively across various sales scenarios.

1-Rule Fares

In this example, we are using the 'Booking Size' rule, where bookings with 4 or more tickets will get a different rate compared to bookings with 3 or fewer tickets.

Booking Size


We set up our rates to the below values:

Regular Rate (CZK)

Fare Rate (CZK)

Adult

200

150

Child

100

80

Family

400

300

Notice how the price changes from 200 to 150 CZK depending on the number of tickets selected in the booking:
​

Dynamic Pricing

Fares Example


Fares with AND Conjunctive Operator

We have added a 1 hour 'Notice' rule to our previous 'Booking Size', therefore the booking now has to satisfy two conditions: the booking size must be 4 or more tickets AND it must be less than 1 hour before travel date (tour start).

AND Conjunctive Operator

Dynamic Pricing with AND Operator

AND Conjunctive Operator Example


Fares with OR Conjunctive Operator

We have changed our conjunctive operator from AND to OR, therefore the booking has to satisfy only one of the conditions: either booking at least 4 tickets OR the booking must be made within 1 hour before travel date.

OR Conjunctive Operator


Notice how pricing changes when only one rule has to be met:
​

Dynamic Pricing with OR Conjunctive Operator

OR Conjunctive Operator Example

​


Percentage Fares

In this example, we use the 'Notice' fare rule and 'Percentage' to price tickets as a percentage of the regulare rate, depending on how far in advance the booking is made. Percentage extras are then calculated from the adjusted ticket or booking price.

We set up two fares:

Notice (days)

Default Percentage

Gate Price

< 1

110

Advance Online Price

> 1

105

We set up our rates to the below values:

Regular Rate

Adult

€100

Child

€50

Per Ticket Extra

10%

Per Booking Extra

10%

After adding the 'Fare' modifier on the Rates tab, you can see the percentage applied by each fare.

📗 TIP

You can override the default percentage for a ticket or extra by entering a different vale in the rates table. Entering 0 make that ticket or extra free.

Applied Fares

📒 NOTE

Fares do not change the percentage of an extra unless you override it manually. A percentage extra is calculated from the ticket price (per-ticket extras) or the booking total (per-booking extras), so it is calculated after the fare is applied.

Percentage Fares Example


No-Rule Fare

No-rule fares are empty fares that override the application of your fares and applies your normal rates instead. This comes in handy when a one-time event has the potential to draw in more customers and you can forego fares that would otherwise apply.
​

To create a no-rule fare,

  1. Press the + NEW FARE button.
    ​

    New Fare

  2. Enter the name.
    ​

    No Rule Fare
    ​

  3. Press the Create Fare button.
    ​

    Create Fare

  4. Go to the General Availability tab.
    ​

    General Availability

  5. Select the 'Date' modifier.
    ​

    Date Modifier

  6. Switch to 'Fare' in the view settings.
    ​

    Fare View

  7. Select a date from the calendar.

  8. Select the 'No rule' fare.
    ​

    Update Availability

  9. Press the Save button.

    Save

  10. Review the fare update in the General Availability tab.
    ​

    📗 TIP

    When updating availability for a date in a different month, the calendar will automatically return to the current month and reset the view to the default 'Capacity' view after you save your changes. To review your updates, switch back to the 'Fare' view and navigate to the month where the changes were made.

    General Availability

  11. Review the fare update in the manifest.
    ​

    Manifest


Fare Groups

We created fares for summer and winter seasons using the Occupancy rule. Each season requires different occupancy rules to reflect the levels of demand - higher in summer and lower in winter at varying degrees.

Our seasons are setup as follows:

Season

From-To

SUMMER

1st April - 30th September

WINTER

1st October - 31 March

We then created two fare groups - SUMMER and WINTER. Each fare has a corresponding retail price, offset by the level of occupancy, as shown in the table below.

Fare Group

Fare

Occupancy

Price

SUMMER

Summer High

> 60%

€55

SUMMER

Summer Medium

> 20%

€50

SUMMER

Summer Low

>= 0%

€45

WINTER

Winter High

> 80%

€50

WINTER

Winter Medium

> 40%

€45

WINTER

Winter Low

>= 0%

€40

In the General Availability tab, we selected the 'Month'-'Weekday' modifiers to set up seasonal pricing. By switching the view from 'Capacity to 'Fare Group', we can see how seasons are assigned. Then, we assigned each month to the corresponding fare group - either SUMMER or WINTER - in the availability detail.

Fare Groups Example


When making a booking, prices automatically adjust to both seasonal demand and occupancy levels. Here are some examples of how the above setup is applied when making a booking:

  • November (WINTER fare group, no bookings - 0% occupancy): the Winter Low fare is applied, the ticket price is €40.

  • April (SUMMER fare group, no bookings - 0% occupancy): the Summer Low fare is applied, the ticket price is €45.

  • June (SUMMER fare group, more than 20% occupancy - 19 out of 25 spots are available: the Summer Medium fare is applied, the ticket price is €50.

Fare Applied during Booking

You can use fare groups creatively for any combination of modifiers - options, seasons, and others.

Did this answer your question?