Solution by property
A whole back office for one route
A timetable, counter ticketing, a gate scanner and a manifest — built for a line that sells seats, not nights.
One route, a timetable that fills itself in
A fare card is a matrix, and it's built like one
A ticket that can be checked, not just trusted
Why this property shape needs a different answer
A ferry line has no rooms and no nights, so a hotel PMS is the wrong product on its face — but underneath the surface, a small operator running one route needs almost the same back office a small hotel does: a schedule, a way to sell what's available, proof someone paid before they board, and a count of who's actually aboard when the boat leaves.
Most of that runs today on a paper manifest, a cash box at the counter, and whoever is on shift — which works until a paper ticket goes missing, two counters sell the same last seat at once, or someone asks for yesterday's passenger count and nobody wrote it down.
One route, a timetable that fills itself in
Set up your ports and vessels once, build a weekly timetable, and MangoHost keeps four months of actual sailings materialised ahead of it — so the counter is always selling a real, dated departure rather than a recurring slot someone has to remember to open.
A fare card is a matrix, and it's built like one
A real ferry fare is never one number. It changes by direction, by class, and by passenger kind — adult, child, senior, a vehicle. The price card is keyed by all three, so the counter charges the actual fare rather than one number with mental adjustments layered on top of it by whoever is selling that day.
A ticket that can be checked, not just trusted
Counter ticketing issues a per-passenger or per-vehicle code with a signed QR on it. At the gate, that code is scanned and validated — cryptographically, not by a phone call back to the counter to ask if it's real — so a gate agent's whole job is scanning tickets, and nothing else on that screen.
Seats that can't be sold twice
The last seat on a sailing is checked and held in one indivisible step, so two counters racing for it at the same moment cannot both win — one succeeds, and the other is refused before it ever prints a ticket for a seat that no longer exists.
A manifest you can print and hand over
Departures, Tickets and Manifest all read a date, not just today, so yesterday's load and tomorrow's bookings are both a click away — not just what happens to be on screen right now. The manifest itself is who is actually aboard for a given sailing, printable, for the day someone official asks for it.
A disruption posted once, seen everywhere it matters
A delay, a cancellation or a general notice is posted once, from Service updates, and expires on its own date or is archived by hand. While it's active, it rides out automatically to the route's GaleraHub listing — so a passenger checking the listing sees the same notice the counter is working from, instead of finding out by showing up to a sailing that already left.
Linked to GaleraHub in one click, the same as a hotel
A ferry tenant connects to GaleraHub the same one-click way a hotel does — no hand-built listing to wait for. That is a real advantage if your route touches Puerto Galera, where GaleraHub is an actual marketplace people book from; everywhere else, it is simply not relevant yet, and we would rather say that plainly than let it read as a national claim.
Worth knowing before the demo
The counter's till isn't live yet
Ticketing, the gate scanner and the manifest are all in use today. A dedicated cash and shift-takings screen for the counter — reconciling what was collected against what was sold — is not built yet, so that part of a shift close still happens outside the product for now. It is next on the list, not abandoned.
Your property, not a generic demo account
See it on your own operation
Thirty minutes with the IslandLink team, your rooms and your rates. No card, nothing to sign — and we will tell you honestly if we are the wrong fit.