Store-and-forward queue
Reports save locally, show a clear pending/synced state, and replay in order when the vessel reconnects.
Product
Reporting — online and offline
The report is filed either way. Sync happens when the link returns.
Most maritime software assumes the vessel is a branch office with a slightly worse connection. It is not. A noon report that only exists if VSAT is up is not a noon report.
Maritronix reporting is written for store-and-forward. Officers complete voyage, noon, incident, and checklist reports on the ship’s network. The pack sits in a local queue with a visible sync state. When the link is back — VSAT, 4G in port, or a USB drop to the agent — the queue drains in order.
Shore does not pretend. Dashboards distinguish confirmed data from last-known. Superintendents can see which vessels have a stale noon without phoning the Master. ISM and PSC packs assemble from the same reports, so the next inspection is not a scavenger hunt through shared drives.
How it actually runs
Noon & voyage
Position, consumption, weather, and cargo events in the shape officers already know — not a generic form builder.
Incident & near-miss
Structured capture with attachments that survive an offline stretch and still land in the right shore inbox.
Honest shore view
Fleet tiles show last confirmed report time. Stale is visible. Guesswork is not dressed up as live data.
ISM / PSC packs
Pull the last N reports, drills, and acknowledgements into an inspection pack without rebuilding a folder.
Port & 4G burst
When the ship hits harbour Wi-Fi or a stronger link, the queue flushes without officers re-keying anything.
The rest of the stack
Crew onboarding
From offer letter to first watch, without the paper chase.
Crew accountingWages, allotments, and owner statements that reconcile.
Ship schedulingFrom port rotation to berth window, without the email relay.
Container managementFrom stuffing plan to discharge, with every box accounted for.