Walk-Up, FCFS, or Advance Booking? Choosing the Right Model for Your Operation
Every transport and tourism operator hits the same fork at some point. Keep the kiosk-only, walk-up, first-come-first-served model that has carried the operation for years? Open up online advance bookings and start managing capacity weeks ahead? Or run both, and let customers self-select? The answer shapes how the office is staffed, how the crew runs the boarding, how the marketing budget gets spent, and how the operator's cash actually arrives. And it is one of the few decisions where the wrong call is more often the prescriptive one than the operational one.
The advice operators get, vs the advice they need
The default SaaS pitch is usually some version of "take advance bookings, capture the customer earlier, capture more revenue." For some operators, the pitch is completely right. For others — and there are more of them than the marketing implies — it is wrong. Tide-dependent embarkation, weather-variable sailings, multi-skipper co-op rotations, FCFS terminal queues, and customers who genuinely want same-day flexibility all push the operation toward walk-up. That choice is usually deliberate. Telling those operators their model is broken because it does not look like an advance-booking model is a category error.
The operators who get the choice right are the ones who weigh their physical operation, their customer profile, and their cash-flow needs against the trade-offs. This article walks through the three live options — walk-up / FCFS, advance booking, and hybrid — what each is good at, what operation suits it, and a short list of signals that point in each direction. We are not going to tell you which is correct. You know your tides, your skippers, your terminal layout, your customer mix, and your peak weeks better than any platform vendor. What follows is the decision framework, not the verdict.
Walk-up / FCFS / kiosk-only — what it is good at
Walk-up and FCFS models have been running tourism and transport for a very long time. Operators who run them well are not stuck in the past — they are running a model that fits the physical operation.
What the model is good at:
Same-day flexibility. Visitors who arrive at a tourist island, city terminal, or regional pier without a fixed plan can board the next sailing. No app, no account, no advance commitment. Conversion happens at the kiosk window.
Tide-dependent and weather-variable sailings. If the sailing only runs when the tide is right, the wind drops, or the swell allows, advance bookings create a refund-and-reschedule problem on every cancelled departure. Walk-up sidesteps it.
Multi-skipper co-op rotations. A co-op of independent skippers running a shared kiosk (Caldey Island-style, or any pier where several owner-operators share a brand) needs every transaction tagged to the skipper who took the run. The walk-up kiosk handles that natively.
FCFS terminal queues. Council vehicle ferries and short-hop passenger ferries with a queue-on-the-day culture often serve regular commuters who would not tolerate the friction of advance booking for a $4 crossing.
Operational simplicity. One channel, one place money changes hands, one inventory pool. The audit trail is straightforward. The crew knows who is on board because they sold them the ticket.
What is required to run this model well is not advance booking. It is operational tooling: fast card payment at the kiosk, QR-scanned tickets at boarding so the crew is not eyeballing a paper count, a live manifest the office and crew see at the same time, a customer database that builds itself from every transaction (operator-owned, not platform-owned), weather-cancellation SMS to today's ticketed customers with a refund-or-rebook link, audit-grade reporting for council contracts or trust accountability, and multi-skipper revenue attribution if the operation is co-op-shaped. These are the capabilities walk-up operators most often need — and the ones the advance-booking-centric marketing rarely talks about.
Advance booking only — what it is good at
For other operators, advance booking is the model the physical operation favours. The conditions that make it work:
Peak-season capacity certainty. Whale-watching operators in season, regional ferry operators on a public holiday weekend, day-tour operators in school holidays — when demand reliably exceeds supply, advance booking captures the visitor who needs to commit two weeks ahead. Without it, those visitors book a competitor or a Viator listing instead.
Channel mix and OTA control. Once the operator wants visibility on Viator, GetYourGuide, or a regional OTA, advance booking is the only model that lets the platform cap how many seats the OTA can sell, reserve direct-channel capacity, or release reserved seats 24 hours out. None of that works on a same-day-only model.
Dynamic pricing. Peak, off-peak, and shoulder pricing assume the customer is committing in advance and that the price reflects how full the sailing already is. Walk-up customers pay one rate at the kiosk. Advance bookers can be priced against demand. Peak Season Capacity Management → covers the maths.
Package bundling. Selling a ferry + tour + accommodation package as one booking — three legs, one transaction, one confirmation — requires advance commitment for each leg.
Cash-flow smoothing. Bookings taken three weeks ahead with a deposit move cash forward before the cost of running the sailing is incurred. For seasonal operators with tight off-season cash, that timing matters.
Operators who lean into advance booking do so because the physical operation is predictable enough to honour the commitment. Where it is not, the model collapses under the cost of refunds and rebookings.
Hybrid — advance booking and walk-up on shared inventory
The third option is the one many operators land on after enough seasons. Take advance bookings for visitors who want to commit, keep the kiosk open for those who turn up, and pool the inventory so the same 200-pax sailing is visible to both channels in real time.
Hybrid is not "advance booking with a kiosk bolted on" or "walk-up with a website widget." Both channels have to draw from the same pool. The crew does not care whether a ticket was bought three weeks ago or three minutes ago — the QR scans the same way, the manifest updates the same way, the weather-cancellation SMS reaches both groups. The operator gets the advance-booking benefits where the physical operation supports them, and the walk-up benefits where the same-day customer still matters.
Where hybrid works:
Mixed customer base — long-haul visitors who book ahead alongside local commuters or last-minute weekend visitors
Mostly predictable sailings with occasional weather risk — advance bookings honoured most of the time, with a tested cancellation comms flow for the days they are not
OTA marketing reach without abandoning the walk-up customer — list a fraction of capacity on Viator, keep the rest for direct and kiosk
Seasonal operations with a clear peak — advance booking dominates in peak, walk-up returns in shoulder
The architectural requirement is that one inventory pool serves all channels, with per-channel rules layered on top. Without that, the operator is reconciling two systems manually, which is worse than running either model on its own. The True Cost of Generic Booking Systems for Transport Operators → covers why this single-pool, multi-channel pattern is harder than the SaaS marketing implies.
The decision framework — five questions to answer
Answer these honestly:
How predictable are your sailings? If weather, tide, or skipper availability cancels more than one in twenty departures, advance booking pushes refund-and-reschedule cost up steeply. If sailings run as scheduled most of the time, advance booking is operationally cheap.
Where do your customers come from? A customer flying in from Manchester for a one-week visit needs to commit before they leave home. A regular commuter or local weekender does not. Look at the mix.
Is peak-season demand reliably exceeding supply? If yes, advance booking captures revenue the walk-up model leaves on the table. If no, advance booking adds friction without adding revenue.
Do you want to be on Viator, GetYourGuide, or other OTAs? OTAs require advance booking. If the marketing reach matters, the channel comes with the model.
How is your cash flow shaped? Off-season cash gaps are easier to bridge with deposits taken three weeks ahead than walk-up cash arriving on the day. If cash timing is tight, advance booking helps. If it is comfortable, this signal is neutral.
A sixth question for those considering a model change: what is the cost of being wrong? Switching to advance booking and discovering customers will not commit ahead costs you bookings. Staying with walk-up and discovering you could have captured 10% more visitors costs a slightly suboptimal model. Asymmetric.
Signal list — what each model is telling you
Print this, or copy it into the operations notebook. The signals stack — the more of each list you tick, the more clearly the model points one way.
Signals that point to walk-up / FCFS / kiosk-only:
Sailings cancel for weather, tide, or sea state more than occasionally
Skipper or vessel rotation changes day-to-day
Most customers arrive at the pier without a prior booking
Crossing or experience price is low (commuter-fare territory)
Council, government, or trust contract — accountability is to a board, not a market
Co-op of independent operators sharing one branded kiosk
Average ticket bought less than 24 hours before sailing
Customer expectation is same-day flexibility, not advance commitment
Signals that point to advance booking:
Peak season reliably sells out
Customers travel from outside the region and need to plan ahead
Marketing budget includes paid social, SEO, OTA listings, or partnerships
Average ticket bought several days or weeks before sailing
Dynamic pricing or peak / off-peak tiers are part of the revenue plan
Multi-leg packages (ferry + tour + accommodation) are part of the offer
Cancellation rate is below 5% — the platform can honour the commitment
Signals that you should run both:
Customer base is genuinely mixed — long-haul visitors plus regulars or weekenders
Peak season needs advance bookings; shoulder season needs walk-up
OTA listings are valuable for marketing reach but the kiosk is not going anywhere
Some sailings are predictable, some are weather-dependent
The operator wants the optionality and is willing to invest in the platform that supports it
Changing your mind later
The model is not permanent. Operators add advance booking after years of walk-up. Some scale back from advance booking when refunds and reschedules become unmanageable. Some add a kiosk after going OTA-heavy and realising the same-day customer was being turned away.
What makes the switch painless or painful is the platform underneath. If the operational tooling — POS, QR, manifest, weather comms, customer database, audit — is already in place, switching modes is a configuration change. The crew uses the same scanners. The office sees the same manifest. The customer database keeps growing. If the platform is built around one model only, the switch becomes a migration project. The right time to think about the platform is before the model choice is locked in. One that handles both natively gives the operator the right to change their mind later without ripping out the system.
How JetSetGo handles this
JetSetGo runs both models on the same platform. Walk-up operators turn on the operational-apps cluster — kiosk POS, QR scanning, live manifest, customer database, weather-cancellation comms, audit reporting, multi-skipper attribution — and leave advance bookings off. Advance-booking operators turn on the inventory management capabilities — channel caps, peak pricing, package bundling, OTA connectors — and run alongside a kiosk or skip it. Hybrid operators run both on one shared inventory pool, with per-channel rules layered on top. The operator chooses which capabilities to enable. The platform does not assume the model.
Book a demo → to see the capabilities relevant to your operation, in the configuration that fits the model you already run.

