Ferry lines: timetables, ticketing, and a one-click GaleraHub link

Until now, MangoHost was a hotel product with a hotel's assumptions baked in — rooms, nights, housekeeping. A ferry line has none of that. It sells a seat on a scheduled sailing, and the software that runs it needs a timetable and a fare matrix, not a room grid.

Choosing 'ferry' as a business type at signup swaps the whole operations set rather than hiding fields that don't apply. Set up your ports and vessels once, build a weekly timetable, and MangoHost keeps four months of actual sailings materialised ahead of it. Fares are priced by direction, class and passenger kind — a real fare card is a matrix, not a single number, and now it's built like one.

At the counter, a ticket sale issues a per-passenger or per-vehicle code with a cryptographically signed QR on it. At the gate, that code is scanned and checked — not phoned back to the counter to confirm — and a gate agent's whole screen is scanning tickets, nothing else. Seats are checked and held in one indivisible database step, so two counters racing for the last seat at the same moment cannot both sell it.

A disruption — a delay, a cancellation, a general notice — is posted once from Service updates and rides out automatically to the route's GaleraHub listing while it's active, so a passenger checking the listing sees the same notice the counter is working from.

And a ferry tenant connects to GaleraHub the same one-click way a hotel already does: no hand-built listing to wait for, no separate onboarding path. That matters because most new ferry lines coming onto MangoHost will want a GaleraHub listing from day one, the same as most new hotels do.