Airlines can now control the availability of seat fares based on the time remaining until departure at the moment of seat selection. A new validation allows fares to become visible (“Show”) or expire (“Expiry”) at a defined number of hours before the flight. Therefore, depending on the time remaining before departure, selecting the same seat may now result in different charges.
Additional fields have been added to the filter view:
as well as the table view too:
We have implemented the same logic currently in place in the Fare module. You can now configure which fare applies depending on the time remaining before departure.
Example of Configuration:
Suppose we want to show seat prices as follows:
30 if time before flight ≥ 13h
90 if 13h > time before flight ≥ 6h
50 if 6h > time before flight ≥ 0h
Then, the correct setup should reflect these conditions.
Frequently Asked Questions:
Should I worry that my existing seat fares might be affected by the update?
No. All currently existing fares will have Show (H) and Expiry (H) values set to 0 by default, meaning there is no limitation on them.
Which sales channels are affected by the change?
All internal sales channels, including CRS, IBE, and API, are affected.
What if I create multiple seat fares applicable at the same time? Which one will be applied?
A fare with both Show (H) and Expiry (H) set to 0 will always have lower priority if any applicable fare with non-zero Show/Expiry values exists.
If two conflicting fares both have non-zero Show/Expiry values, the fare with the lower ID (created first) will be applied. Airlines are responsible for avoiding such misconfigurations.
What happens if there is a period not covered by any seat fare (e.g., the last 24 hours before departure)?
In this case, as before, the seat can be assigned free of charge.
What about the Upload / Mass Update Seat Fares feature?
The mass seat fare update file has been adjusted to support the new columns. By performing a special export, you can view the new columns, adjust the data, and upload it back to the system successfully.
Comments