Vehicle logistics for roll-on / roll-off
Every unit,
ramp to release.
A vessel drops six hundred cars on your quay in a single tide. RoroLogix accounts for all six hundred — scanned at the gate, parked in a known bay, photographed for damage, billed by the day, and released only to the person holding the paperwork.
Runs on a phone in the sun · Works with no signal
One scan, three seconds · No RFID, no proprietary readers
Gate scans
Scroll to discharge ↓
Chain of custody
One vessel,
told by the scroll.
The manifest lands before the ship does
Every VIN, make, model and consignee is loaded while the vessel is still at sea. By the time she berths, the gate already knows exactly what to expect.
EDI · CSV · fixed-width
Duplicate VINs flagged
Six hundred units, one tide
Drivers work off a running list on their phones. Units are checked against the manifest as they come off the ramp — not reconciled days after.
Off-manifest arrivals held for review
One scan. Three seconds.
A QR on the windshield card, scanned once. The gate keeps moving at peak discharge and nobody writes a plate number by hand.
Cards laser-printed in bulk
before the vessel arrives
Every car in a known bay
The system picks the bay and tells the driver where to park. Damage photos and condition notes attach to the unit on the spot.
Bay-level location · timestamped photos
The clock stops at the gate
Storage accrues by the day and stops the moment the unit leaves. No release without a matching authorisation — and the charges post on exit.
Gate pass verified · charges posted
The kit
One record, every screen
RoroLogix is a single progressive web app that fits the device already in each person's hands — the gate operator's rugged handheld, the inspector's tablet, the office browser. Install it from the browser in a minute, and it keeps working when the yard's signal doesn't. The card on the windshield is the piece of paper that ties all of it to the physical car.
Modules
One scratch, followed to the cent
Inspection, claims and accounting aren't three systems passing spreadsheets — they're three views of the same append-only record. Here's a single scratch on a single unit, from the second it was photographed to the line it became on a statement.
Following unit 1HGCM82633A004352 — LH door, one scratch
Inspection
Structured condition checks at discharge and again at release, with every photo bound to the unit, the stage and the second it was taken. Two inspections, one record — so "it was already like that" gets answered by the record, not by memory.
Damage map & severity · dual-stage checks
Inspector sign-off · works offline
Scratch · 40 mm
Claims
Any damage record becomes a claim in one tap. The evidence pack — photos, gate scans, timestamps, signatures — assembles itself from the unit's history, and the claim tracks against the carrier, the terminal or the insurer until it settles.
Auto evidence pack · respondent tracking
Settlement to the cent · outcome logged to the unit
Accounting
Storage accrues per unit per day against each party's tariff, handling posts at the gate, and settled claims land as credits on the same statement. Invoices generate on release — and every figure is readable over the API, so your ledger stays the ledger.
Per-party tariffs · voyage statements
Release-time invoicing · /api/v1 export
Field conditions
Designed for the yard, not the office
Terminal software usually gets built by people who have never stood on hot asphalt at 2pm trying to read a screen through a scratched visor. These decisions came from the yard, and each one closes a failure we watched happen.
Windshield cards that survive the dashboard
A dashboard behind glass in the tropics runs 60–70°C, and direct thermal print turns black in a week. Cards are laser-printed in bulk on heavy matte stock before the vessel arrives. Thermal is kept for short-life tags only.
Keeps working when the signal drops
Scans, photos and moves are recorded on the device and queued. When the connection returns they sync in order, and a conflict is surfaced to a supervisor instead of silently overwritten.
Phones you can get repaired locally
Runs on rugged Android handhelds and tablets with user-swappable batteries, not sealed proprietary scanners with a six-week RMA to another country. A dead battery costs a minute, not a shift.
An append-only record
Every scan, move, inspection and release is written once and never edited. When a consignee disputes a scratch or a storage bill, the answer is a timestamped photo and a signature, not an argument.
Both sides of the gate
The carrier and the dealer see the same unit
The terminal and the dealership normally argue over two different spreadsheets. Here they read one record, each from their own side of the fence.
Shipping lines & terminals
Discharge a full vessel and close the voyage the same week, with the yard, the paperwork and the invoicing already agreed.
- Voyage reconciliation — manifested against landed, with shortages surfaced during discharge
- Yard allocation across multiple lots, with occupancy you can see before the ship arrives
- Per-party tariffs, so one voyage can bill three consignees three different ways
- Driver, inspector, gate and manager roles with separate permissions
Island dealerships & importers
Stop calling the port. See your units land, watch the storage clock, and send someone to collect on the right day.
- Your consignments only — landed, inspected, cleared or held
- Storage days running per unit, so nothing sits accruing unnoticed
- Release requests raised online instead of at the counter
- Shareable arrival status for a customer waiting on their car
Integrations
Your accountant never has to log in
Storage charges, gate moves, inspections and releases are all readable over a documented REST API. Post them straight into the ledger you already use, or pull a voyage into your own reporting. No export, no re-keying, no closed integration surface you have to pay to open.
{ "vin": "1HGCM82633A004352", "voyage": "SEABORNE ARROW / 2617", "state": "STOWED", "location": "LOT A / BAY 27", "landed_at": "2026-08-12T09:14:22Z", "storage_days": 3, "charges_to_date": { "amount": 4500, "ccy": "USD" }, "inspections": [ { "type": "DISCHARGE", "photos": 6 } ], "hold": null }
Getting started
Start with one vessel
Nobody should cut a working terminal over on faith. Run a single voyage in parallel with whatever you use today and compare the two at the end of it.
Send a past manifest
We load a voyage you've already discharged and set up your lots, bays, parties and charge rates. You see your own data in the system before committing to anything.
Run one voyage in parallel
Your gate scans the next vessel into both systems. Drivers and inspectors train on the real thing, on their own units, with the old process still standing behind them.
Reconcile, then cut over
Compare the two records unit by unit. When the numbers agree — and the yard prefers the phone — the old system is switched off.
rorologix.com
Bring your worst
voyage. We'll run it.
Tell us the vessel that gave you the most trouble last year — the one with the shortages, the disputed damage and the storage nobody could agree on. That's the one we want to load.