Module: Flights
Flights is still to be organized. Unlike Hotels, there’s no equivalent „own-inventory“ fix in sight — an event organizer can rent a whole hotel, but it cannot buy and resell a block of airline seats the same way, so the model that resolved the Hotels question doesn’t carry over here.
Original Scope (From Prior Planning)
Flights offers participants flight options as information only — helping them find and compare ways to reach the event. As with Hotels, actual booking is not handled within Sabin; participants book independently, guided by instructions Sabin provides rather than an integrated booking flow.
Open Discussion: Commission Model
Whether Flights stays purely informational, or becomes commercially interesting through a booking commission — Sabin surfacing flight options through a booking partner or affiliate link, with the EO earning a percentage of completed bookings. Based on experience with Hotels (e.g. discounted codes from chains like Sheraton), real commission arrangements tend to require slow, case-by-case negotiation and often aren’t worth pursuing — the same is likely true for airlines, possibly more so.
What Still Needs Deciding
| Information-only vs. commission-based | Simple, low maintenance vs. added complexity of an affiliate/booking API integration that history suggests may not pay off. |
| Realistic scope | Whether Flights should default to information-only from the start, given the Hotels experience, rather than reopening the commission question from scratch. |
Relationship to Hotels
Previously considered a combined „Travel“ module with Hotels. Since Hotels has since moved to an own-inventory, VIP-package model that doesn’t apply to flights, the two are now tracked as separate, independently-decided modules.