Every flight number carries a fare per cabin class, and the journey price a passenger sees is built from those fares. You never have to set a single one, but every one you do set is a lever.
Where a price comes from#
For each class on each leg, the engine resolves the fare in strict order:
- The explicit fare you set for that class.
- Your economy (Y) fare times the world's class multiplier: by default 1.6× for premium economy, 2.8× for business, 4.5× for first (your world may differ).
- The engine's auto fare: a distance-based reference price for that leg, times the class multiplier.
Leave fares blank and the flight sells at the auto price, which tracks the route's distance sensibly. The auto fare is also your anchor: pair pricing sliders work in percent of it, and it is shown wherever you price a route.
The four pricing tools#
| Tool | Scope | Behaviour |
|---|---|---|
| Airport pair settings | One route (and optionally its return) | Set or reset per-class fares and the on-board service level; applied atomically to every flight number on the pair |
| Ticket price adjustment | Your whole network, or everything from/to an airport | One-shot percentage change to current fares, per class; the fuel-surcharge-style blunt instrument |
| Standard pricing policy | Network-wide and per country pair | A persistent percentage of standard price applied to every journey's total at booking time; keeps applying as schedules change |
| Fare products | One origin–destination pair | Through-fares that replace the segment sum on connections you market |
The pair settings block lives on both Market Analysis and Inventory, so you can reprice without leaving the route you are studying, including a one-click match of a competitor's fare. For the standing policy, the most specific rule wins: an explicit route fare stays your base price, a country-pair rule beats the network rule, and rules never stack.
Through-fares: price the journey#
By default a connection is priced as one journey: the engine's default fare for the origin-destination distance, scaled by how you price the legs it is built from (legs at 20% over default make a connection at 20% over default). That keeps a one-stop from costing more than the nonstop it is slower than. Worlds created before v1.56.1 still charge the sum of the segments. A fare product on an O&D pair replaces the journey price for the classes you fill in, whenever your flight operates the first leg of the connection. Price below it to win connecting traffic over your hub; price above it where passengers have no alternative. Options priced this way carry a "through" tag in Market analysis under fog.
Service is part of the price#
The pair settings also set on-board service (None to Premium). Service costs you per passenger per hour, and passengers judge it against what their cabin class expects: skimping in business class hurts more than skimping in economy. Cabin product itself is set per aircraft in Cabins.
Pricing under fog#
You will never see a demand curve. Price too high for a customer type's budget and those passengers do not trade down gracefully; they disappear from your option entirely. The honest feedback loop is loads and revenue: see How booking works and Inventory & load monitoring.