Product - Shopping Flashcards
Search =
Customer asking for route+dates so includes:
- Inspiration so only Instant Search
- Request part of shopping
Types of partners for qualified and unqualified traffics
Qualified: TAs & TMCs
Unqualified: OTAs & Metas
Steps of shopping
- Flight Exploration
- Fare Exploration
Steps of Fare Exploration
- Fare selection:
Wich fares are in scope -> fare path graph - Fare path explorer
Find the cheapest fares
Algorithm for non-exhaustive search
Branch & Bound
Flex ITI mode
Calculates price only for full itinerary. No details at bound level
Choice of Flex mode can be by
Routes
Flex ITI mode: what is the typical website flow
1) Choose both dates from a calendar
2) Upsell FF at itinerary level
3) Choose exact flight on both dates
No price is ever shown by bound
Evolutions of Flex modes
ITI -> OWD (to display bound split for info)
-> Premium (to fill the holes of OWD due to the limited number of recos)
-> OWC (for more user flexiblity)
Flex OWD mode
Calculates the price only for full itinerary. Splits per bound for display.
No information can be given until all bounds chosen. When a bound recommendation is selected, the other bound is refreshed.
Flex OWD mode limitations
Due to limited number of recommendations, not all bounds/FF prices are available so in upsell steps, some cells are empty
Flex OWD mode: what is the typical website flow
1) Choose both dates from a calendar
2) Upsell FF at bound level
3) Choose exact flight on first date
The prices of the return flights are updated by the UI without a new FP call
Main difference between OWD and OWC
In OWD, the prices of the return flights are updated when the outbound is selected
Flex OWC mode
Price of the 2 bounds are independent. This requires dedicated filing
Restriction of filing to use OWC
Can use Cat 6 (Min stay) & Cat 7 (Max stay)
Cannot use Cat 10 (fare combinability - which links the fares of the 2 bounds)
Flex OWC mode: what is the typical website flow
1) Select outbound and see a price
2) Select inbound and see an independent price
Flex Premium
- Outbound request: recommendations for outbound/FF only (as the cheapest whatever inbound/FF is)
- Inbound request: recommendations for inbound/FF considering selected outbound/FF
Main difference between OWD and Premium
In Premium, the update of inbound after outbound selection is done with a Shopping call, not by the UI
Flex Dual Mode
UI display allowing calendar and upsell in the same screen (not a Flex feature)
Easy Round Trip
Increase the number of returned TS by removing the ones that can be deduced from others
Typical example of CFF
CFF for Eco lists:
- Eco Special, Eco Basic
- Premium Eco
CFF for Business lists:
- Business Flex Plus
Range of Flex Calendars depending on the modes
- ITI, OWD, Premium: +/- 3 extended to 7
- OWC: +/- 7 extended to 15
[C Calendar]
Number of FF in Flex depending on the modes
- ITI, OWD: up to 6
- OWC, Premium: up to 10
ITI doesn’t allow mix of FF
[sticks to chase hens]
Number of travel solutions in Flex depending on the modes
- ITI, OWD: 20 (10 per bounds or 20 for one way ITI)
- OWC: 20 per bound
- Premium: 50 per bound
[poor shoes -> hives=plenty]
CFF definition: where
FareXpert or ATPCo Branded Fares
Easy Round Trip vs
All Recos
Max output of Flex is defined by
Message size (235kb) and settings (not the number of recos)
[enamel]
Flex: Sold out
Create sense of urgency with a strike through ficticious price
Flex: Empty cells: reasons
No flight found, No fare found, Sold out
Configuration of AAS in Flex: where
FareXpert or ATPCo Branded Fares
AAS in Flex: 2 versions
- At FF level (“from”price and up to 20 svc)
- At reco level (ATPCo price and up to 5 chargeable)
Benefits of Branded Fares in ATPCo
Aligns all channels
Technical process with Branded Fares vs FareXpert
If CFF not found in ATPCo, goes to FareXpert
Flex Pricer for Complex Itinerary (multi-city): limitations (3)
Same FF for the whole trip
6 segments
6 FF
Flex: mixed cabins
Possible per bound but needs to be requested by user in input
Flex options to create a sense of urgency (3)
Sold out, Last Seat Indicator, Popularity Message (based on static rules)
Flex feature for stricken through old price: works with which features
Fare by Rules, corporate code, AAM
Mini rules
Short and readable description of fare rules & restrictions
Mini rules: how does it work
Interpret some categories only (just a few)
Flex stop over: customer input
Place & number of nights at stop over for each bound
How does Easy Round Trip work
For a given FF and same price, if a group of bounds are combinables between one another, we group all recos into a few recos just so that each bound appears at least once
Opposite of “Calendar”
“Travel Board”
Smart Switch
Orchestrator for MasterPricer to sometimes default to Instant for improved response time
Additional benefit of OWC
Better response time
Typical markets for OWC
Domestic markets
Pricing after shopping
Pricing by fare basis to ensure alignment
Typical number of recos returned
200
Typical OWD response time
2.5s [nails]
MCP and MSP
MCP (Massive Computation Platform) for computation offline
MSP (Massive Search Platform) for storage and search
MetaConnect replaces
Multiple FP calls but also MP calls (Kayak getting GoVoyages, etc.)
Instant feature for marketing campaigns
Can define a campaign in FareXpert which will increase the frequency of the cache refresh if scope<5% of data domain and refresh less the rest
