Vendor demos look alike. The features check out, the slides land cleanly, the procurement team has a defensible scorecard. None of it predicts whether the system will still be earning its place in the operation in 2036.
The mistake most checklists make is to grade features as yes or no. A vendor can demo a capability without the data model that makes it work at scale, and the structural problem only surfaces months into production. The deepest of those problems is when a container TOS has been retrofitted to serve RoRo: the data model, the workflows, and the billing engine were built for boxes, and vehicles are not boxes.
This guide walks through twelve places where that retrofit breaks, each as a concrete operational scenario, with the answer pattern that separates a purpose-built RoRo TOS from a container TOS with a vehicle skin.
Why Container TOS Retrofits Fail in RoRo
A container is identified by a number stencilled on its side, stored vertically in a stack, billed per day at a flat demurrage rate, and released against a booking that names the container by number. A vehicle is identified by a VIN read through a windshield, stored on a two-dimensional grid where every spot is independently retrievable, billed against a stream of chargeable events under a per-customer tariff that steps with dwell, and released against an authorisation specific to the individual unit.
The two cargo classes share the word "terminal" and little else. A container TOS retrofit passes a one-hour demo because every feature is technically present. It fails in production because the data model treats a unit as a flexible asset class, the yard hierarchy is shallow, the billing engine is per-day flat, and the tenancy model assumes one terminal one operator.
The Twelve Scenarios
1. The same VIN moves through booking, pre-announcement, receipt, yard moves, photo QC, load scan, and voyage closure on one record. Walk me through that chain in front of me.
The test is unit lifecycle integrity. A purpose-built RoRo TOS treats the VIN as the identity from booking to load and stores every state change on the same record. A container TOS retrofit shows you a discharge log, a yard log, an invoice log, and a load log, and the integration between them is a foreign key that breaks under volume.
2. A shipping line transmits 300 unit bookings for next month's vessel. Walk me through pre-announcement, physical receipt against the announcement, and automatic assignment to the next outbound vessel.
The test is the inbound flow that defines vehicle terminals. Vehicle terminals receive units over weeks and assign them to outbound vessels later, against booking and customer agreement. A serious RoRo TOS pre-allocates yard space against the announcement, validates each arriving unit at the gate, and runs the next-vessel assignment as a workflow. A retrofit treats receipts as ad-hoc and reconciles after the fact.
3. Show me the yard view with row, lane, bay, and spot hierarchy. Look up a specific VIN and return its position in seconds.
The test is two-dimensional yard topology. Container TOS yard models are designed for vertical stacking, indexed by bay-row-tier, where retrieving a container requires picking from the top of the stack. Vehicle yards are flat grids with thousands of independently addressable spots, where every unit must be reachable on its own without moving others. A retrofit will show you a flat list or a stack model and try to convince you the difference does not matter.
4. A customer's 800-unit parcel arrives on one vessel and distributes across three physical yards. Maintain parcel-level consolidation and present unified visibility to that customer.
The test is multi-yard parcel management. Container TOS treats each terminal as a silo and the customer assembles the cross-yard view themselves. A serious RoRo TOS maintains a parcel record that spans multiple yards under one operator, with movement history per unit and a customer-facing report that does not require the customer to know which yard holds what.
5. The vessel has departed. Reconcile what loaded against what was supposed to load, at VIN level, and walk me through exception handling for units left behind.
The test is voyage closure at unit granularity. Container TOS closes the voyage at container count, which is structurally insufficient for vehicle exports where each unit has a specific manifest entry. A serious RoRo TOS reconciles per VIN, exposes missing-versus-extra exceptions, and produces the post-voyage report the line and the manufacturer expect.
6. Forty units booked for tomorrow's vessel will miss the cutoff. Walk me through the shut-out workflow: customer notification, re-routing, storage clock continuation, re-handling fee.
The test is the shut-out workflow container TOS does not have. Containers that miss a vessel remain on yard until the next call. Vehicles that miss a vessel trigger an explicit response: customer notification, re-assignment to the next vessel based on space and contract, continued storage billing, and a re-handling fee. A retrofit handles shut-outs as manual exceptions and lets billing slip through.
7. A vehicle sits 35 days with three yard moves, photo deliveries, a wash, and a customer-requested expedite. Show me every chargeable event auto-attached to the right tariff and the right customer, with no operator memory required.
The test is event-driven auto-billing at the VIN level, which is where most of a RoRo terminal's revenue actually lives. Container TOS bills per box per day at one flat rate, which misses the entire surface of accessorial events. A serious RoRo TOS logs every operational event against the unit with a chargeable flag, applies the customer's contract tariff automatically, and runs a reconciliation pass before invoicing that surfaces missed or duplicate charges.
8. Storage steps from basic at day 0, to premium at day 14, to penalty at day 30, all per-customer contracted. Apply the tier transition automatically and surface it on the invoice.
The test is tiered storage tariff. Container TOS typically models storage as a single per-day rate, occasionally with one threshold for free time. Vehicle terminals negotiate per-customer tiered tariffs that step at multiple thresholds. A serious RoRo TOS supports per-customer tiered tariffs with automatic transitions on the calendar, line-item invoice presentation showing the per-tier breakdown, and a customer portal view that warns the customer before the next tier kicks in.
9. One yard segment holds units from four shipping lines and several other customers. Enforce per-customer release rules, tariffs, visibility, and operator access without cross-contamination.
The test is multi-client tenancy inside a shared physical operation. A serious RoRo TOS exposes per-customer rule sets that govern release, billing, visibility, and access, all enforced consistently across screens, reports, and customer-facing portals. Container TOS often assumes terminal-wide tenancy and leaves operator vigilance to bridge the gap.
10. Every vehicle is photographed at receipt, after yard moves, before load, and at any incident in between. Photos are indexed per VIN with timestamp and operator, available to the line and the manufacturer through the same record the gangs are working on.
The test is photo-based quality control, structural to vehicle terminals and absent from container terminals. A serious RoRo TOS captures photos on the handheld at each state change, writes them back to the unit record in real time, and surfaces them to the line and the manufacturer through the same operational record. Photo evidence is operational, not assembled after the fact.
11. Show me the margin on a single VIN. Revenue captured (storage tier, accessorial charges, handling fee) against cost incurred. Then aggregate to customer and to terminal.
The test is per-vehicle profitability reporting. Container TOS reports at shipment or at TEU, which is structurally too coarse for vehicle terminal management. A purpose-built RoRo TOS reports at VIN level, aggregating up to customer, to vessel, and to terminal, so that operations leadership can see which customers, which segments, and which dwell bands are actually profitable. A retrofit will show you a TEU-equivalent report that hides the answer.
12. Which RoRo terminals at my unit volume and customer mix have been running on your system for three or more years? Can I speak to them unscripted?
The test is real reference depth at comparable operations. A vendor with operational depth in RoRo will name two or three customer terminals matching your profile, with multi-year operational history, and will offer unscripted operator-level calls. A vendor with thin RoRo experience offers scripted executive references at non-comparable sites or evades the comparability filter entirely.
How to Read the Answers
A vendor's score on these twelve scenarios is less about saying yes than about how the yes lands. Three patterns reliably separate operational maturity from sales polish.
Naming customers. References to specific terminals, specific scenarios, specific outcomes signal a vendor who has lived the answer. References to "typical customers" or "industry best practice" signal one who is improvising.
Surviving the follow-up. A vendor who has done the work takes a second-level question and stays specific. A vendor who is rehearsing pivots to architecture, roadmap, or strategy when the question goes one layer deeper.
Naming the unhappy path unprompted. A vendor who volunteers what their system does badly, what they have learned, and where the next investment is going has the self-awareness a ten-year relationship needs. A vendor who only describes the happy path will deliver the unhappy path on Monday morning.
Red Flags in Vendor Demos
A demo dataset where every vehicle is in perfect state, with no partial discharges, no shut-outs, no tier transitions, no contested billing. A clean dataset is a dataset that has not been used.
A yard view that looks like a satellite layer without row, lane, bay, and spot structure. The visual is a decoration over a flat data model, and operators will not navigate it the way they navigate a real yard.
A billing model that quotes a single flat storage rate per day. Real RoRo terminals run tiered tariffs by dwell band, per-customer contract rates, and accessorial charges per event. A flat rate is a sign the billing engine was never tested against an actual vehicle terminal's revenue model.
Closing
The twelve scenarios above are the operational realities every RoRo terminal lives, and the twelve places a container TOS retrofit breaks. A vendor that has carried the operation through them for a decade answers each concretely, with named customers. A vendor that has not will reach for slides.
Logisoft has carried these answers across stevedores and terminal operators. The terminal operating system covers the unit-lifecycle chain from booking to voyage closure, auto-charging at event level, tiered storage tariffs, multi-client tenancy, and per-vehicle profitability. The yard management module covers the two-dimensional yard hierarchy, multi-yard parcel, and pre-announcement. The terminal operators solution maps the full operating model. If you want a second opinion on a specific scenario, we will walk you through the answer with named references at APS Stevedoring in Jacksonville and Sallaum Terminals in Belgium.
