The flow (recommended)
1) Search available services for a flight
The user provides flight number and date. You show what’s available (Fast Track, Delay Care, etc.) with pricing.
2) Show the user what they’re buying
Your UI should highlight:
- terminal and address (where to go)
- working time and open status
- booking deadline (pre-order time)
- the access method (QR / code / instructions)
3) Create an order (one per passenger)
Create an order for the passenger and store the returned order ID.
What to show in your UI
When presenting airport services, show:- service type (Fast Track, Delay Care, etc.)
- terminal and address (where to go)
- working time and open status (don’t present as guaranteed when closed/no-info)
- pre-order time (latest time the user can book)
- how to use the service (where to present the code / voucher)
UX guidance (what to communicate)
Explain pre-order time
Explain pre-order time
If pre-order time is “2h”, the user must book at least 2 hours before departure. Show a clear “book by” time in your UI.
Respect open status
Respect open status
If open status is
closed or no-info, don’t position the service as guaranteed. Consider hiding it or showing a warning.Use one order per passenger
Use one order per passenger
If the user needs to book for multiple travelers, your UI should support repeating the booking flow for each person.
What to collect and store
What to collect before booking
What to collect before booking
You typically collect:
- passenger name
- flight number and date
- passenger type (adult/child) if pricing differs
- selected service option (and variant)
What to store after booking
What to store after booking
Store:
- the order ID
- booking status
- price and currency
- the access code (or voucher details) and “where to go” instructions
Your UI should display the access code prominently, plus terminal/address, so the passenger can use the service without contacting support.

