The operational platform built for RoRo, not adapted to it.
Most enterprise software used in RoRo shipping was designed for a different operating model. CRM understands customers but not voyage economics. Generic transport systems understand capacity but not cargo specifications. CargoVerse exists to close that gap.
Three cargoes.
Three operational realities.
BMW X5
Caterpillar D11
14m Agricultural Trailer
In container shipping, cargo is the abstraction.
In RoRo, cargo is the specification.
Generic CRM doesn't know a BMW X5 from a Caterpillar D11. Container-derived TMS treats cargo as weight and volume. Every operator ends up building its own shadow database — in Excel, in shared folders, in the head of the planner who has been there longest.
Container software sees units.
CargoVerse sees cargo.
RoRo doesn't fit inside tools built for other markets.
Three categories of platform are usually proposed. None of them hold a RoRo operator's reality.
| Capability | Generic CRM | Generic CPQ | Container TMS | CargoVerse |
|---|---|---|---|---|
| Customer management | ✓ | Partial | Limited | ✓ |
| Cargo specification | ✗ | Partial | Limited | ✓ |
| Allocation impact | ✗ | ✗ | Partial | ✓ |
| Voyage profitability | ✗ | ✗ | Limited | ✓ |
| Shared operational model | ✗ | ✗ | ✗ | ✓ |
Each generic tool was designed for a different operating model. RoRo's cargo specification doesn't fit any of them.
The comparison feels theoretical until you sit in a contract negotiation. The CRM tells you the customer is important. The CPQ tells you what they paid. The TMS tells you the capacity that was consumed.
None of them tells you whether the next two years should be priced at the same rate — because none of them holds the operational pattern that shaped the last two. CargoVerse does, because cargo, schedule, allocation, and contract sit on the same data model.
What it looks like when cargo specifications live outside the operational system.
CargoVerse brings those specifications into the operational model itself — not as proxies, not as Excel reconciliation, but as the entities the operator actually plans against.
The operator pays a tax on its own organisation every single year — for a structural mismatch between the tool and the business.
Compounded margin leakage. Contracts renewed with the same operational pattern that hurt them last cycle. Cargo accepted late that displaces higher-yield allocation two rotations forward. Decisions made on what was available, not what was true.
One operational picture — cargo, schedule, contract, cost.
CargoVerse changes where the data lives at the moment the decision gets made. Pricing, voyage planning, allocation, and contract structure share the same data model and the same real-time state — not a new dashboard, but a shared operational picture.
Cargo specification, not abstraction
BMW X5, Caterpillar D11, 14-metre trailer — modelled as themselves, with their actual deck and rotation consequences.
Decisions inside the same picture
Commercial, operations, and finance look at the same model — without reconstructing it from spreadsheets first.
Reference model, not finished package
CargoVerse is an accelerator. Every implementation adapts to the operator's actual processes. That's the only way we've seen it work.
More than a decade of exclusive RoRo and PCTC work.
CargoVerse is the productisation of what Cartagena has been building — for customers, on Microsoft Dynamics 365, around workflows the operators themselves helped define.
Wilhelmsen Ocean
CargoVerse was developed by consultants, architects, and solution specialists who have worked exclusively with RoRo and PCTC operators since 2012.
Cartagena’s founder originally built CPQ and pricing systems inside Wallenius Wilhelmsen Ocean — on the operator side — before bringing that decade of experience into Cartagena. CargoVerse is the productisation of those workflows on Microsoft Dynamics 365 Power Platform. Current version: 2025.
Each of these engagements solved concrete operator problems: contract tracking, allocation by deck configuration, voyage profitability in real time, EDI portals for OEMs. CargoVerse implementations start from that reference model and adapt to the operator's actual processes.
The friction operators stop carrying.
- No separate customer database to keep in sync
- No duplicate cargo records across operations and commercial
- No nightly synchronisation between CRM and TMS
- No rebuilding reports in Excel before each board meeting
Microsoft Dynamics 365 and Azure make that possible — because the operator's ecosystem is already there, and CargoVerse inherits it instead of replacing it.
- Familiar interfaceOutlook, Teams, SharePoint, Excel — short learning curve, low change-management cost.
- Security and GDPREU data residency, identity, audit trails, encryption — at platform level, not bolted on.
- Power Platform extensibilityCustom workflows, integrations, Power BI for management reporting.
- Long-horizon investmentThe platform evolves alongside Microsoft's commitments to D365 and Azure.
The competitive advantage in RoRo shipping is decision quality, not execution speed.
Better operational decisions show up directly in voyage profitability, allocation quality, contract performance, and customer-level margin. The operators that decide with the full picture — at the moment the cargo is accepted, the rotation is set, the contract is renewed — outperform those that reconstruct it after. CargoVerse exists to bring that picture to the moment the decision is actually made.
See how CargoVerse would run in your operation
We walk through the reference model and the workflows in the accelerator, and discuss what gets adapted for an operation like yours. 45 minutes, live in the platform.
Request a walkthrough