Booking Rules Overview
Overview
Booking Rules are available in the product module and allow users to control both functionality throughout the application as well as display. They are also designed to provide users with the opportunity to personalize and control the output and functionality per brand, per product, per customer and more by utilizing filters. Although there are some booking rules that require additional set-up from Softrip, there are also many bookings rules that users can update and manage on their own.
Users can access booking rules by selecting the Product module, hovering over set-up, and then selecting “booking rules”.
Creating a Booking Rule
To set-up a new booking rule, users can access the + (plus) symbol to begin building. Once there, users can choose the Rule Area, Rule Type, describe the rule, enter rule text, or add additional filters.
Rule Area
Rule areas come out of the box in the Softrip installation or created by Softrip via Programing Requests. This is a required field and can be filed in either by typing in the rule area name and choosing it from the drop down or by accessing the search grid using the arrow.
Rule Area
The rule areas are abbreviated when selecting from the drop-down. If users want to view a summary of the function of the rule area, they can expand the search criteria by opening the search grid and viewing the description column.
Rule Type
There are four different Rule Types that define the action of the rule that is being created.
Display
Can be used by internal users. If selected, the information entered into the Rule Text will display in areas such as the invoices, documents, and reservations.
Execute
Used for rules that are set up by Softrip. Typically associated to an action that may occur outside of queues in operations.
Event
Used for rules that are set up by Softrip. Typically associated to trigger an action on a queue.
Scheduled Event
Used for rules that are set up by Softrip. Typically associated when a queue is to be sent at a specific time. An example would be “send the queue every day at 9:00AM EST”.
Description
The description field is for internal use and is used to describe the booking rule.
Rule Text
Users can enter information under the “rule text” area. Depending on the rule area that is selected, this information is then displayed on areas such as reservations, invoices, or documents.
An example would be using the “rule text” to enter the information that users want displayed under either the invoices or the documents.
Defining the fields
The following filters are available under booking rules.
Res Status
Users can control if a certain booking rule will apply depending on the reservation status of a booking such as “active” or “option”.
Sell Methods
Different rules can be applied based on the avenue in which the booking was made, either call or web.
Brands
If there are multiple brands under one application, users can control if a booking rule only applies to certain brands.
Supplier ID's
Control which booking rule applies to different suppliers such as hotel chains, transfer companies, etc.
Service ID's
Control which booking rule applies to different service IDs. This includes specifying information for bookings that have a specific tour or specific room category.
Service Types
Control which booking rule applies to specific service types such as any booking that include transfers or air components.
Product Codes
Users can control if a booking rule applies to specific product codes such a an entire tour or a specific custom group traveling.
Destinations
Certain information can be controlled based on the destinations that passengers are traveling to. For example, users may want specific information to be displayed for Ireland but different information to be displayed for Rome.
Currencies
Users can control if the booking rule only applies if a booking is under a specific currency.
Note: This only applies if the customer supports multiple currencies.
Market Codes
Control which booking rule apply to specific bookings based off of the market codes that they are made under.
Customer ID's
If certain booking rules only apply to certain travel agencies, then the IATA number can be added under the booking rule. This is useful if users offer different insurance tiers to different agencies.
Book Dates and Departure Dates
The book dates and departure dates help determine which rule to apply based on either:
The date the reservation was made
The date the reservation departs
Example
A company may decide they want to provide specific vouchers in the travel documents to their customers that are traveling to a destination within the month of October.
Users can create a DOCCOVER booking rule with special text and update the departure date details in the filter so that they can advise there are special vouchers included in their documents.
Customer Types
Use this to control if a booking rule only applies to certain customer types.
Note: Users can update customer types under product codes.
Show on Web/Show on Documents
If the booking rule or the rule text should display on reservations and/or documents, select the check boxes to show on web or docs.
How the System Determines a Booking Rule When Multiple Rules Apply
When multiple booking rules match a reservation, the system evaluates them by specificity and returns the most relevant rule first.
Rule Prioritization (Relevance)
Rules are scored based on relevance, which reflects how closely they match the reservation context—for example, product, service, customer, or applicable dates. The rule with the highest specificity is given priority.
Factors Driving Specificity
Rules that contain more matching filters are ranked higher. Key fields include:
Product / Service Scope: ProductCode, ServiceID, ServiceType
Market / Brand / Customer: MarketCode (header vs. service via MarketHeader), Brands, CustomerAffiliation, CustomerID, CustomerType
Status and Channel: ResStatus, SellMethod, WeekDays
Date and Duration Windows: BegBook / EndBook, BegDep / EndDep, FromDur / ToDur
How the System Handles Ties Between Booking Rules
Sometimes two or more booking rules match a reservation equally well. When that happens, the system still returns an ordered list of rules, and the first one in that list is applied.
Step 1: Relevance Comes First
Rules are ranked by how closely they match the reservation. A tie happens only when all the important filters—such as ProductCode, ServiceType, market/brand/customer settings, and date or duration ranges—are identical.
Step 2: Common Tie-Breakers
If multiple rules are still tied, the system uses additional checks to decide which one comes first:
Narrower date or duration ranges are preferred (e.g., tighter booking or departure windows).
Sequence (Seq) values help set priority—lower numbers are treated as higher priority.
Timestamp (DateStamp) may be used if everything else is equal, often favoring the most recent entry.
Step 3: Applying the Rule
After sorting, the system simply picks the first rule in the list. This ensures there is always a clear outcome, even when rules look identical.
Practical Application
The rules engine generates a ranked list of all matching rules, ordered by relevance (most specific first). The calling process then selects the top-ranked rule, ensuring that the most targeted rule takes precedence.
To influence rule selection, narrow the scope of a rule by specifying fields such as ProductCode, restricting date ranges, or setting a MarketHeader.
How to Upload Image to a Rule