Fare Rule Decoder: Turn Cryptic GDS Fare Rules Into Plain English

Every GDS can print a fare rule. Almost nobody can read one at a glance. A block of penalty text like PENALTY - CHG NOTPERM/REISSUE NOTPERM ... REF PERMITTED/CHARGE USD150 tells you exactly what a client can and can't do with their ticket — but only if you're fluent in the shorthand it's written in.

The Fare Rule Decoder exists for the moment a client asks "can I change this if my plans shift?" and you don't want to spend three minutes parsing GDS penalty codes to answer honestly.

How It Works

1. Copy the fare rule textPull it straight from your GDS — the raw penalty, change, refund, or baggage remark, exactly as displayed.
2. Paste it into the decoderOpen the Fare Rule Decoder and drop the text into the box.
3. Read the plain-English resultChange fees, refund eligibility, and any baggage conditions are translated into sentences a client can actually understand — no GDS shorthand required.

Reading a Fare Rule Line by Line

A typical GDS fare rule display crams change conditions, refund conditions, and penalty amounts into a few dense lines of abbreviations. Here's a representative example of the kind of text the decoder is built to handle:

PENALTY
CHG - CHANGES PERMITTED. CHARGE USD150 PER TRANSACTION.
     REISSUE PERMITTED
REF - CANCELLATIONS PERMITTED. CHARGE USD200.
     REFUND PERMITTED BEFORE DEPARTURE ONLY
NO-SHOW - NO REFUND. TICKET VALUE FORFEITED

Read cold, this is a wall of shorthand. Read with context, it says something a client would actually want to know: changes are allowed for a $150 fee, cancellations are allowed for a $200 fee but only before the flight departs, and simply not showing up for the flight forfeits the entire ticket. That's the gap the decoder closes — not by changing what the rule says, but by turning terminal shorthand into a sentence.

Why This Matters More Than It Seems To

Fare rules are where trust gets won or lost with a client. Quoting a fare accurately is one thing; being able to instantly and confidently explain what happens if their plans change is what makes an agent look like they know what they're doing. A hesitant "let me check on that and get back to you" reads very differently from an answer given on the spot.

What to Do With the Result

Use the plain-English explanation as your fast read, then quote the specific figures — the change fee amount, the refund conditions — back to the client in your own words, or paste them directly into the itinerary you send. Treat it the way you'd treat any tool that speeds up reading dense text: it gets you to the right answer faster, but the fare rule in the GDS remains the authoritative source before you ticket anything.

It's also worth deciding, case by case, how much of the decoded text actually needs to reach the client. For a straightforward leisure booking, a single sentence on the change fee and refund status is usually enough. For a corporate client or a booking where the traveler has explicitly asked about flexibility, pasting the fuller decoded explanation — including the no-show and reissue conditions — into the itinerary itself gives them something to refer back to later without having to ask again.

Change Fees vs. Fare Difference: A Distinction Clients Always Ask About

The single most common confusion when quoting a rebooking cost is treating the change fee as the whole cost. It almost never is. The change fee is what the fare rule specifies for the act of changing the ticket — a flat charge, or occasionally waived entirely. On top of that, if the new flight's fare is higher than what was originally paid, the client also owes the fare difference between the old ticket and the new one. A fare rule that says CHG - PERMITTED. CHARGE USD150 is telling you about the fee, not about whether the new flight happens to cost more. Both figures matter, and quoting only one of them is how an agent ends up having to explain an unexpectedly large total after the fact.

When the Filed Fare Rule and Current Airline Policy Diverge

The decoder works from the fare rule text as filed and displayed in the GDS — the same text you'd be reading if you pulled it up manually. That text doesn't automatically reflect a temporary policy an airline has issued outside the filed fare rule, such as a waiver tied to a schedule change, a weather event, or an involuntary itinerary change initiated by the carrier. Those waivers typically show up as separate advisories or queue messages in the GDS rather than as part of the fare rule itself. If a client's situation involves anything outside a straightforward, voluntary change, it's worth checking for an active waiver before quoting the standard filed penalty — the filed rule may say one thing while a temporary policy currently overrides it.

Baggage Remarks: The Other Half of the Rule

Fare rules and baggage allowances are often displayed together but describe different things, and it's easy to read one while meaning to check the other. Baggage remarks generally follow one of two systems: a piece-based allowance (commonly written as 1PC or 2PC, meaning one or two checked bags included) or a weight-based allowance (a total kilogram allowance regardless of how many bags it's split across). The decoder reads baggage remarks the same way it reads penalty text — pasted in, translated to plain language — but the distinction between "how many bags" and "how many kilograms" is worth double-checking manually if a client is packing close to the limit, since going over either kind of allowance results in a paid excess-baggage charge at the airport rather than at booking.

Fare Rules Are Often Split by Direction

On a round-trip ticket, the change and refund penalties are frequently not identical in both directions — a fare rule display will often break the text into an outbound portion and a return portion, sometimes labeled EACH WAY or shown as two separate penalty blocks rather than one combined figure. It's a detail that's easy to miss when skimming, and it matters: a client changing only their return flight shouldn't be quoted a penalty that actually applies to a full round-trip change. When a fare rule is split this way, read (or paste) both halves separately rather than assuming the first penalty line covers the whole itinerary.

A Note on Currency

Penalty and fee amounts in a filed fare rule are shown in whatever currency the fare itself was filed in — commonly the local currency of the point of sale, though international fares are sometimes filed and displayed in USD regardless of where the ticket is issued. Before quoting a change or cancellation fee to a client, confirm which currency the figure is actually in rather than assuming it matches the currency you're pricing the rest of the trip in — a fee quoted in one currency and mentally converted as if it were another is a fast way to under- or overstate what a client will actually be charged.

Works Alongside Your Itinerary

Fare rule context pairs naturally with a converted itinerary — after you've turned a PNR into a client-ready booking summary with PNRGenius's main converter, decode the accompanying fare rule separately and you can hand a client both the flight details and a clear answer on change/refund terms in the same conversation.