If prices can't be added we will check in the fare tables for the point to point prices and for a Market price modifier and apply those modifiers to each of the individual tickets in the trip.

The Root class defines the product association for the nesting — one or more products that the nesting applies to. It may also define an optional Nesting Name display name. When the account's Child Selection Criteria is Sales Authorizations Availability, a root might optionally enable Independent Availability by Seat Class. When the account's Child Selection Criteria is Most Specific, a root might optionally enable Compounding Price Modifiers.

This case is to test the different combinations of prices on MP fare tables with or without modifiers and JP rules to a route, to see which has greater weight, and how they impact the sale process.

any additionals to the price, such as taxes or modifiers will be waived. In this example the user will just pay 1000 points. The .06 from the modifier, and the .19 from the IGV tax are waived.

In case you are using MP scheme and using modifiers, you will see a section with the Modifier price version ID: link so you can identify modifier set up applied to the ticket.

The search engine will show results based on trips that have available prices. First, it will make it check the trip date against each matching fare table’s effective date range, and only use one that is valid for that day. If more than one is valid, it picks the best match (the most current one). If none are valid, it fails clearly instead of silently using an expired list. Depending on the pricing schema, it will check modifiers or JP records to show the price that best matches the request.

Both the UP and NO CENTS round strategies should not be used when applying percentage discounts, fees or price modifiers since this may result in some odd prices displaying in the cart. For example, an article with a price of $9.99 after a discount or fee is applied may be shown in the subtotal as $9.