If you have multiple fares, the order in which they are listed in the table directly affects how fares are applied in your checkout widget and affects overall performance.
To optimise performance, it is recommended to list fares in descending order (from HIGH to LOW), following these guidelines:
From more complex to simpler rules
From more complex to simpler rules
Start with fares that have multiple rules and end with those that have none. The more specific the rule, the fewer database queries will be required, the better the performance of your checkout widget.
📒 NOTE
The same applies when using only one rule. Start with a fare with the highest value, and list all others in descending order.
The below example shows the correct and incorrect usage of the occupancy rule:
✅ Price | ❌ Price
1. >= 75% $90 | <= 50% $70
2. >= 50% $80 | <= 76% $80
3. >= 0% $70 | <= 100% $90
From most expensive to cheapest
From most expensive to cheapest
Ventrata takes all the possible fares assigned for the day and returns the cheapest one, adjusting the final fare based on the applicable rule(s).
📘 EXAMPLE
We have two fares: the fare for a larger booking size is at the top and the one for a smaller booking size is below.
This order is also justified by the pricing, as the 4-passenger fare is more expensive and therefore listed first, while the 2-passenger fare is placed lower as it is cheaper.
This setup helps ensure faster performance and accurate fare application.