This article covers Opera V5 (OXI)-specific behaviours that can affect how FLYR pushes price and restriction updates. Understanding these will help ensure your optimization setup works as expected.
For data reporting differences between Opera V5 and FLYR, see Data Differences Between Opera V5 (OXI) and FLYR Reporting.
1. Derived Rate Plans — Base and Dynamic Base Rate Configuration
Description
If a derived rate plan includes both a Base Rate and a Dynamic Base Rate, FLYR will set the Base Rate as the parent rate plan. This may cause inconsistencies in rate inheritance.
Suggested Workaround
Only configure one type of Base Rate per derived rate plan — either a Base Rate, a Dynamic Base Rate, or an Advanced Dynamic Base Rate. Avoid combining more than one type on the same rate plan.
2. Derived Rate Plans — Price Updates Not Supported for Dynamic Base Rates
Description
Price updates cannot be pushed for child rate plans that use Dynamic Base Rates or Advanced Dynamic Base Rates. Because these rate plans do not store fixed prices in Opera — prices are calculated dynamically at the time of booking or availability check — there is no fixed value for FLYR to update.
Suggested Workaround
None. This is a known limitation within Opera and OXI.
3. Derived Rate Plans — Restrictions Not Supported for Dynamic Base Rates
Description
Opera requires a stored price in order to apply restrictions. Because FLYR and the integration adapter cannot retrieve prices for derived rate plans using Dynamic or Advanced Dynamic Base Rates, restrictions cannot be sent or applied to these rate plans.
Suggested Workaround
None. This is a limitation of the FLYR/Adapter integration due to Opera's design.
If you have any questions about how these behaviours may affect your setup, reach out to our support team. We're here to help.