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
Chain of custody
Five hand-offs. Each one signed for.
Most units go missing in the gaps between systems — the manifest lives in a spreadsheet, the gate lives in a notebook, and the yard lives in someone's memory. RoroLogix keeps one record and appends to it at every hand-off, so the history of a unit can't be quietly rewritten.
Manifest
Load the vessel manifest before she berths. Every VIN, make, model and consignee is expected at the gate.
EDI · CSV · fixed-width
Duplicate VINs flagged
Discharge
Drivers work off a running list on their phone. Units come off the ramp and get checked against the manifest, not after it.
Off-manifest arrivals
held for review
Gate
One QR scan takes three seconds. The gate keeps moving during peak discharge and nobody writes a plate number by hand.
Windshield card printed
in bulk before arrival
Yard
The system picks the bay and the driver is told where to park. Damage photos and condition notes attach to the unit on the spot.
Bay-level location
Timestamped photos
Release
Storage accrues by the day and stops the moment the unit leaves. No release without a matching authorisation.
Gate pass verified
Charges posted on exit
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
- Storage and demurrage calculated per unit per day, automatically
- Damage inspection with photo evidence at discharge and at release
- 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
- Condition photos from the moment the unit came off the ramp
- 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": "GYD" }, "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.