Skip to main content
Print

What are Pricing Rules?

Pricing Rules allow you to automatically adjust ticket prices in ExperienceBank without changing the original prices in your booking system.

They provide a flexible way to increase or decrease prices before they are sent to supported Online Travel Agencies (OTAs), making it easy to manage different pricing strategies across your sales channels.

Whether you’re running an Early Bird promotion, applying a Weekend surcharge, or increasing prices during peak season, Pricing Rules help you automate these adjustments while keeping your booking system as your single source of truth.


Why use Pricing Rules?

Managing prices across multiple sales channels can be challenging, especially when each marketplace has different commercial requirements.

Pricing Rules allow you to:

  • Increase prices to cover marketplace commissions.
  • Offer discounts during promotional campaigns.
  • Create seasonal pricing strategies.
  • Apply different pricing to specific marketplaces.
  • Reward customers who book early.
  • Add surcharges for weekends or peak travel periods.
  • Keep one base price in your booking system while automatically sending adjusted prices to connected marketplaces.

Instead of manually updating prices every time your pricing strategy changes, ExperienceBank applies these adjustments automatically based on the conditions you define.


How Pricing Rules Work

ExperienceBank sits between your booking system and your connected marketplaces.

When your booking system sends pricing information to ExperienceBank, any active Pricing Rules are applied before the prices are sent to supported marketplaces.

The original prices stored in your booking system are never modified.

The process works as follows:

  • Your booking system sends the base ticket price to ExperienceBank.
  • ExperienceBank checks whether any active Pricing Rules match the booking conditions.
  • If a matching rule is found, the ticket price is automatically adjusted.
  • The updated price is sent to the connected marketplace.

This allows ExperienceBank to act as the pricing layer between your booking system and your distribution channels.


Example

Suppose your booking system contains the following ticket price:

Booking System PricePricing RulePrice Sent to Marketplace
€100Increase by 10%€110

In this example:

  • Your booking system continues to store €100.
  • ExperienceBank applies a 10% increase.
  • The marketplace receives a price of €110.

The original booking system price remains unchanged.


Additional Examples

Booking System PricePricing RulePrice Sent to Marketplace
€100Increase by €5€105
€100Decrease by €5€95
€100Decrease by 10%€90
€75Increase by 20%€90
€100Increase by 15%€127.50


Real-World Examples

Example 1 – Covering Marketplace Commission

Your booking system price is:

€100

GetYourGuide charges commission on each booking.

Instead of increasing prices in your booking system, create a Pricing Rule that increases the ticket price by 10%.

Result:

  • Booking system price remains €100
  • Marketplace price becomes €110

Example 2 – Early Bird Promotion

You want to encourage customers to book summer tours early.

Create a Pricing Rule that:

  • Reduces prices by 15%
  • Applies only to bookings made between 1 June and 15 June
  • Applies only to tours taking place between 1 July and 31 August

Customers booking within the promotion period automatically receive the discounted price.


Example 3 – Weekend Surcharge

Your boat tours are more popular on weekends.

Create a Pricing Rule that:

  • Increases prices by €10
  • Applies only on Saturdays and Sundays

Customers booking weekend departures will automatically pay the higher price, while weekday prices remain unchanged.


Example 4 – Peak Season Pricing

Demand is significantly higher during school holidays.

Create a Pricing Rule that:

  • Increases prices by 20%
  • Applies only between 15 July and 31 August

The higher prices are automatically sent to supported marketplaces during this period.


What Can Pricing Rules Be Based On?

Pricing Rules can be configured using one or more conditions.

For example:

  • Marketplace
  • Activity
  • Option
  • Ticket Type
  • Booking period
  • Activity date
  • Time of day
  • Weekdays
  • Minimum number of days before departure

These conditions can be combined to create highly targeted pricing strategies.


Supported Price Adjustments

ExperienceBank supports two adjustment methods.

Percentage

Adjust the ticket price by a percentage.

Examples:

  • Increase by 10%
  • Decrease by 20%

Fixed Amount

Adjust the ticket price by a specific amount.
Examples:

  • Increase by €5
  • Decrease by €10

Important Notes
Pricing Rules do not change the prices stored in your booking system.
Pricing Rules only affect new bookings made while the rule is active. Existing bookings are never recalculated.
Pricing Rules only apply to marketplaces that support pricing synchronisation through ExperienceBank.

Frequently Asked Questions

Will Pricing Rules change my booking system prices?

No.
Pricing Rules only adjust the prices ExperienceBank sends to supported marketplaces. Your booking system always keeps the original price.

Can I increase and decrease prices?

Yes.
Pricing Rules support both price increases and price decreases using either percentages or fixed amounts.

Can I create seasonal promotions?

Yes.
Pricing Rules can be limited to specific booking periods, travel dates, weekdays, or times of day, making them ideal for seasonal promotions.

Can multiple Pricing Rules apply to the same booking?

No.
If multiple Pricing Rules match the same booking, ExperienceBank applies only one rule: the matching rule with the highest priority.
Learn more in Understanding Pricing Rule Priority.

What should I do next?

Once you’re familiar with how Pricing Rules work, continue to Creating and Managing Pricing Rules, where you’ll learn how to create your first Pricing Rule and configure each available setting.


Related Articles

Now that you understand what Pricing Rules are, continue with the following guides:

Table of Contents