For river cruises, expedition ships and charter vessels
A small ship is a hotel with restaurants, a bar, a spa, excursions and a store room — except it also moves, and you cannot reorder mid-voyage. Almost no software covers all of that together, so operators run cabins on one system, the bar on another and provisioning on a spreadsheet. FullGuest runs the whole vessel: cabins, every outlet, excursions, stores and crew, with one folio per guest.
Cruise software is built for the giants — ten thousand berths, casinos, a dozen decks. A 40-cabin river boat or a 90-guest expedition ship gets quoted a system priced for a fleet, or ends up stitching hotel tools together and hoping.
Everything a small ship sells and consumes runs in one place, which is what makes a single guest folio possible and what makes provisioning something you can actually plan.
Cabins behave as rooms: assignment, occupancy, housekeeping status, and a guest record with identity documents captured before boarding rather than in a queue at the gangway.
The single most useful thing on a ship: everything a guest spends anywhere aboard lands on one bill, so nobody reconciles chits at disembarkation.
The constraint that makes a ship different from a hotel: you load in port and live with it. So the store room has to be honest, and consumption has to be tracked against recipes rather than guessed.
A small crew covers many roles, and turnover is constant. The venue should hold the knowledge rather than the person who is leaving at the end of the season.
River cruises, expedition and small ocean ships, day-charter and dinner-cruise operators — broadly, vessels that run like a boutique hotel with outlets rather than like a floating resort city. If you are operating a 3,000-berth liner with casino and duty-free bonded stock across jurisdictions, this is not built for you and we would rather say so.
Not fully, and this is the honest limit. FullGuest is a connected system: it needs a working link to take an order or post to a folio, so it suits vessels with reliable onboard connectivity — river routes, coastal itineraries and ships with dependable satellite. If your vessel routinely loses connection for hours, that is a real constraint and you should weigh it before anything else on this page.
Rates are priced by date and cabin type, which fits itineraries sold as dated departures. It is not a voyage-package engine with per-berth occupancy tiers of the kind large lines use, so if your pricing is built around triple and quad occupancy across cabin grades, ask us how it maps to your fares before committing.
Those are maritime systems and they are not ours. FullGuest covers the hospitality side of the vessel — cabins, food and beverage, excursions, stores and crew records. It captures guest identity documents at check-in, which is usually the input your manifest process needs, but it does not file them for you.
Recipes turn a passenger manifest and a menu into a quantity — how much flour, protein and wine a voyage will consume — so you load against a figure rather than an instinct. Then batch and expiry tracking with oldest-first consumption keeps fresh stock rotating, and wastage recorded by item means each voyage loads better than the last.
Yes. Excursions, spa treatments and tastings run as bookable services with genuine capacity limits — a set number of seats per departure, enforced when two guests book at the same moment — and the charge lands on their cabin folio.
Yes, the same way a group runs several outlets: each vessel is its own operation with its own stock and staff, reported on one definition of revenue and cost, with a shared store ashore able to supply them via costed transfers.