Marine Technology / Software buyer’s guide
Ferry ticketing systems: software, reservations and fare payment
Choose the right kind of ferry ticketing system for your route, compare published vendor capabilities, and test the boarding, capacity, and peak-demand cases that decide whether it works.
Choose by service type first. A commuter pass, a car deck, and a sightseeing departure are different systems.
A ferry ticketing system sells fares, controls capacity, validates passengers at boarding, and reports the money. The right one depends on the service. Walk-on commuter routes need fast validation and transit passes, vehicle ferries need deck-space reservations, and tour-style routes need online sales and reseller connections. Choose the service type first, then test boarding, schedule disruption, and on-sale traffic with your own data.
What a ferry ticketing system does
At its simplest, the system publishes sailings and fares, takes payment, issues a ticket, and confirms that the ticket is valid at the gate. A complete platform also controls capacity on each sailing, produces a passenger and vehicle count, manages changes when a sailing is cancelled, and gives finance a sales record it can reconcile.
The work spans several teams. Customers buy online, by app, by phone, at a kiosk, or at a booth. Terminal staff scan and load. Customer service rebooks. Finance reconciles card settlements, reseller sales, and refunds. A demonstration that shows only the checkout page covers a small part of the job.
Ticketing or reservations: know which you need
A 2019 vendor review prepared for Kitsap Transit draws a useful line. Ticketing generally sells access for near-immediate use, often with boarding still first come, first served. A reservation holds a place at a specified future time. Many operators need both, on different routes or for different customers.
The same review found no system built around consistent, recurring commuter reservations and called the dedicated commuter ferry market small. That finding is several years old, so ask current vendors to show you this case rather than assuming it either way. It remains a good warning: a product built for one-off leisure trips may handle a regular rider awkwardly.
Start with your type of ferry service
Vendors often serve more than one of these groups, but each service has a different hardest problem. Name yours before you compare products.
| Service | What the system must do well | Vendors to research first |
|---|---|---|
| Walk-on commuter ferry | Very fast boarding, passes and transfers, regional transit fare cards, agency reporting | Masabi, Anchor, your regional fare program |
| Vehicle and passenger ferry | Deck-space inventory, vehicle dimensions, check-in lanes, standby, schedule changes | Hogia, Carus, E-Dea, Liknoss, PDMS |
| Long-route or overnight ferry | Cabins, onboard sales, freight, revenue management, travel agents | Hogia, Carus, E-Dea, Liknoss, Expian |
| Tourist, island, or seasonal ferry | Online sales, resellers, timed departures, simple scanning | Anchor, Zaui, Starboard Suite, FRS flexWays |
This is our reading of how vendors describe their products, not a ranking. A vendor not listed against a service type may still serve it.
Ferry ticketing vendors compared
| System | What the vendor publishes | What to test |
|---|---|---|
| Hogia BOOKIT | Reservations, dynamic pricing, mobile check-in, gates, kiosks, plate recognition, freight, commuter products, and tools for moving bookings during disruption. | A cancelled sailing with mixed cars, foot passengers, and freight |
| Carus CarRes | Booking, ticketing, port processing, and onboard services, from fast passenger-only ferries to vehicle and freight services. Based in Åland, Finland. | Which modules a smaller route actually needs |
| E-Dea R5 | Modules for reservations, pricing, ship inventory, terminal and yard, and check-in and boarding. Based in Naples, Italy. | Deck planning and yard flow on your busiest sailing |
| Liknoss SeaOnLine | Passenger tickets, garage organization, freight, and ancillary services, licensed on premises or as hosted software. Based in Athens, Greece. | Which hosting model fits and who supports it in your time zone |
| PDMS Compass | Booking online, by phone, at kiosks, or in offices, port ticketing that can run offline, and rugged handhelds that print tickets on deck. | A terminal network outage in the middle of loading |
| FRS flexWays | Pricing, inventory and capacity, self-service check-in, boarding, and an API for accounting, loyalty, and port connections. Affiliated with the FRS shipping group. | How your fare rules and port interface would be configured |
| Anchor | Dynamic pricing, multiple sales channels, staff scanning, and reseller connections. Publishes pricing as a percentage of web sales with no monthly or setup fee. Hornblower Group announced it as an independent division that still serves Hornblower. | Treatment of your data and pricing, given the Hornblower connection |
| Zaui | Passenger and vehicle tickets from one inventory, live deck capacity, real-time manifests, and reseller and agent portals. | Vehicle sizes that take more than one standard space |
| Expian | Multiple routes and pricing rules, reseller connections, and an API-first design. P&O Ferries is its named ferry customer. | Terminal self-service and any vehicle check-in you need |
| Starboard Suite | Reservations and ticketing for passenger vessels, with check-in, a ticket scanner, and a kiosk. | Whether a tour-style tool fits a scheduled route |
| Masabi Justride | Mobile ticketing for transit, launched with Fire Island Ferries in 2017 using visual validation, with no handheld reader. | Fare evasion and boarding speed with visual checks |
This table reflects vendor publications reviewed in November 2026. We have not tested these products. Features can depend on plan, region, and setup, so confirm them in a demonstration.
What recent ferry projects show
Washington State Ferries says its online ticketing and reservation tools are more than a decade old and struggle with growing demand and smartphone use. Its modernization page lists $23.7 million in funding, a restructuring in March 2026, vendor selection in winter 2026 to 2027, and a first rollout in late 2027 or early 2028. Anchor announced a contract with the system in January 2025, while the current state page names no ticketing vendor, so check the state’s page for the latest position. Booking pressure remains visible: local coverage reported problems when summer 2026 reservations opened.
The Steamship Authority in Massachusetts issued its request in December 2024, received nine responses, scored nearly 750 criteria and questions, and selected E-Dea on a five-year, $5,779,484 contract. Coverage from September 2026 reported the project running about 30 days behind, with options including a short delay or postponement to October 2027.
San Francisco Bay Ferry shows how channels can divide. Anchor handles app and paper tickets, including event sailings, while frequent riders are encouraged to use the regional Clipper card. One Clipper account cannot pay for a group, and Clipper is not accepted on event services, so the two channels serve different riders.
P&O Ferries replaced legacy software with Expian on its Hull to Rotterdam route, in a deployment reported at six months. Timelines vary widely, and a vendor’s setup estimate is not the same as your whole project. Fare rules, integrations, training, and customer communication all take time.
Features that matter most
- One inventory across website, app, phone, kiosk, booth, and resellers, so that a sold space is sold everywhere.
- Capacity by sailing, with separate limits for passengers, vehicle space, cabins, and accessible spaces where they apply.
- Vehicle rules for length, height, trailers, motorcycles, and commercial vehicles if you carry them.
- Fare products for one-way trips, returns, passes, concessions, groups, and residents, including how proof of eligibility is checked.
- Validation that still works when connectivity drops, with a clear process for syncing afterward.
- Disruption tools that move or refund a whole sailing and notify every affected customer.
- Live counts for the crew, with a defined way to stop boarding at the vessel’s permitted limit.
- Reconciliation of sales, refunds, card settlements, reseller commissions, and deferred revenue.
- Open access to your data, plus connections to accounting and a marine operations dashboard.
Seven tests to run before you sign
Bring real fares and a real timetable. Ask the vendor to perform each test while your terminal, customer service, and finance staff watch.
- Cancel a full sailing. Move customers to the next departure, refund those who decline, and show what each team and customer sees.
- Sell the last vehicle space through two channels at once. Then try a vehicle that needs more than one standard space.
- Scan a full boarding line on a handheld at normal walking pace. Include a duplicate ticket, a wrong-date ticket, and a concession fare.
- Disconnect the terminal network during boarding. Keep loading, then reconnect and check the counts.
- Change a booking from a car to a foot passenger after payment. Confirm the refund, capacity, and accounting entries.
- Reconcile one day from sales through refunds, reseller commissions, and the bank deposit.
- Simulate your busiest on-sale. Ask for evidence at your expected traffic, and agree who is responsible if the site slows or fails.
Ferry ticketing costs: how to compare them
Few vendors publish a full price, and pricing models differ. Anchor publishes percentage-of-web-sales pricing, with 4% as its lowest published rate. A 2019 review for Kitsap Transit recorded per-ticket pricing, a service fee of about $2,000 a month for one ticketing product, and about $40,000 upfront with $60,000 a year for an enterprise ferry system. At the larger end, the Steamship Authority contract is about $5.8 million over five years. These figures are dated or specific to one buyer, so use them only as a sense of range.
The cheapest model depends on your fares. In the hypothetical example below, the same per-ticket fee is expensive for a low-fare commuter route and inexpensive for a high-fare vehicle route. Build the same model with your own volumes and quoted rates.
| Hypothetical route | 4% of web sales | $0.75 on every ticket or booking | $100,000 flat fee |
|---|---|---|---|
| Commuter: 300,000 tickets at $10, 60% sold online | $72,000 | $225,000 | $100,000 |
| Vehicle: 40,000 bookings at $80, 90% sold online | $115,200 | $30,000 | $100,000 |
These rates and volumes are illustrative, not quotes, and exclude card processing. Also budget for hardware, kiosks, integrations, data migration, training, change requests, reseller commissions, and your own project staff. Ask who pays each customer-facing fee.
U.S. rules to raise with the vendor
This is a starting checklist, not legal advice. Confirm how each rule applies to your operation with counsel and your funding agency.
- Disability access: 49 CFR Part 39 covers passenger vessel operators. It bars extra charges for passengers with disabilities, limits advance-notice requirements and says notices must reach responsible staff, and sets rules for accessible cabin bookings. Check that fare rules, notes, and holds in the system support these duties.
- Phone and website access: Section 39.55 addresses telephone reservation services and written information. Ask separately for the vendor’s accessibility testing of its website, app, and kiosks.
- Federal transit funding: recipients should review FTA Title VI guidance before changing fares or fare media. Requirements vary by agency size and service, so a move to app-only tickets is worth checking early.
- Card security: PCI DSS applies to merchants that handle card data. Ask which party is responsible for each requirement, and get it in the contract.
What to put in the contract
Add ticketing requirements to your procurement early. If an outside operator runs the service, the ferry operations RFP should state who owns the system, the customer data, the fare revenue, and any card agreement, and what happens to each when the operating contract ends.
- Service levels for availability, peak on-sale periods, support hours, and incident response.
- Your right to export customer, booking, and financial data in a usable format, including at exit.
- Who sets fees charged to customers, and who keeps them.
- Limits on how the vendor can use your data, especially if it is affiliated with another operator or an aggregator.
- Acceptance tests based on your own disruption and peak-demand scenarios.
- A fallback plan for ticket sales and boarding if the system is unavailable.
Frequently asked questions
What is a ferry ticketing system?
It is software, and often hardware, that sells ferry fares, controls capacity, validates tickets at boarding, and reports sales. Larger systems also handle vehicle space, cabins, freight, terminal check-in, and onboard sales.
What is the difference between ferry ticketing and a ferry reservation system?
Ticketing sells a right to travel, and boarding may still be first come, first served. A reservation holds a place on a particular sailing. Vehicle ferries usually depend on reservations, while many walk-on commuter routes rely on ticketing and passes.
What is the best ferry ticketing software?
There is no single best product. Commuter, vehicle, overnight, and tourist services have different needs. Shortlist vendors with comparable routes, then test cancellation, boarding, offline use, and peak demand with your own data.
How much does a ferry ticketing system cost?
It depends on scale and pricing model. Published examples range from a percentage of web sales to about $5.8 million over five years for the Steamship Authority. Compare quotes using your own ticket volumes, average fares, online share, and implementation costs.
Can small ferry operators use tour booking software?
Often, for scheduled passenger services with simple fares. Check it carefully if you need vehicle space, commuter passes, transit transfers, standby lists, or agency reporting, because tour tools may not be designed around them.
How do ferries prevent overselling vehicle decks?
They keep one live inventory across every sales channel and count deck space rather than simply counting vehicles. Test this by selling the last space from two channels and booking a vehicle that takes up more than one standard space.
Do ferry tickets work without internet at the dock?
Some systems support this, but methods vary. PDMS, for example, says its port ticketing can run offline, and Masabi’s visual validation does not need a handheld reader. Test what happens to duplicate scans and passenger counts during an outage.
Can a ferry accept a regional transit card and its own app?
Yes. San Francisco Bay Ferry uses Clipper alongside its own app and paper tickets. Plan how each channel handles groups, event sailings, transfers, and discounts, because the rules can differ.
Sources & research notes
Company capabilities and program facts are based on the primary sources below, reviewed November 6, 2026. Scenario calculations, scope checklists, and fit assessments are our editorial analysis.
- Hogia · Ferry systems and BOOKIT ↗
- Carus · Ferry reservation and port systems ↗
- E-Dea · R5 ferry platform ↗
- Liknoss · SeaOnLine ferry reservation ↗
- PDMS · Compass ticketing and reservations ↗
- FRS Systems · flexWays ↗
- Anchor · Ferry ticketing software ↗
- Hornblower Group · Anchor division announcement ↗
- Zaui · Ferry booking software ↗
- Expian · Ticketing platform ↗
- Starboard Suite · Passenger vessel reservations ↗
- Masabi · Fire Island Ferries launch ↗
- Kitsap Transit · Reservation system vendor landscape (2019) ↗
- WSDOT · Ticketing and reservations modernization ↗
- Steamship Authority · Reservation system vendor selection ↗
- San Francisco Bay Ferry · Using Clipper ↗
- U.S. DOT · 49 CFR Part 39, passenger vessels ↗
- FTA · Title VI Circular 4702.1B ↗
- PCI Security Standards Council · Merchant resources ↗