About CargoVerse

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.

12+
Years exclusive RoRo and PCTC work
5
Major operator implementations behind the product
2006
Microsoft partner since
Microsoft Solutions Partner, Digital & App Innovation

Built by a Microsoft Solutions Partner for Digital & App Innovation

CargoVerse is developed by Cartagena AS. The designation is awarded by Microsoft and measured on delivery performance, certified skills and documented customer outcomes. Cartagena has delivered on the Microsoft platform since 2006.

What you're actually managing

Three cargoes.
Three operational realities.

BMW X5

Segment
Automotive
Allocation
Standard deck configuration
Operational impact
Predictable capacity consumption

Caterpillar D11

Segment
High & Heavy
Allocation
Deck protection and clearance requirements
Operational impact
May constrain adjacent cargo allocation

14m Agricultural Trailer

Segment
Project / Agricultural
Allocation
Non-standard lane geometry
Operational impact
Different capacity and margin profile

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.

PLATFORM PREVIEW — Cargo specification
Cargo specs Allocation Voyage Contracts BMW X5 — Unit 4827 Automotive · Forecast lane: Bremerhaven → Zeebrugge LENGTH 4.92 m lane metres allocated HEIGHT 1.76 m decks compatible: 2-5 AUTO-ASSIGNED Deck 3 Lane 14 · pos. 7-12 Margin profile EUR 247 / unit vs. contract baseline EUR 234
Illustrative — the cargo specification view shows segment, dimensions, deck assignment, and margin profile in one record.
The difference in one picture

Container software sees units.
CargoVerse sees cargo.

CONTAINER SOFTWARE
Unit
— TEU equivalent
Unit
— TEU equivalent
Unit
— TEU equivalent
vs.
CARGOVERSE
BMW X5
Automotive · 4.92m · Predictable
Caterpillar D11
H&H · Deck-protected · Rotation-blocking
14m Trailer
Project · Non-standard · Different yield
Why the generic stack falls short

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.

The cost of abstraction

What it looks like when cargo specifications live outside the operational system.

01
Every decision requires interpretation. Planners translate cargo into system-friendly proxies before they can act on it.
02
Pricing relies on historical assumptions. Quotes go out against contract baselines, not against actual cost-to-serve.
03
Allocation depends on planner experience. The system holds capacity numbers; the planner holds the knowledge of what fits next to what.
04
Profitability is understood after the voyage. The cargo has sailed before the financial picture is reconstructed.

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.

What CargoVerse exists to do

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.

CargoVerse architecture — One Dataverse, three layers, no silos A three-layer system architecture diagram. Commercial layer on top contains Pricing & Quote, Booking, and Contract modules. Shared Data Model layer in the middle is the operational centerpiece, holding Customer, Cargo, Vessel, Voyage, and Contract entities in real time. Operations layer on the bottom contains Schedule & Voyage, Allocation, and Profitability modules. The entire platform is built on Microsoft Dynamics 365 and Azure. ONE DATAVERSE · THREE LAYERS · NO SILOS COMMERCIAL Pricing & Quote Booking Contract SHARED DATA MODEL · REAL-TIME One operational picture Customer · Cargo · Vessel · Voyage · Contract OPERATIONS Schedule & Voyage Allocation Profitability BUILT ON MICROSOFT DYNAMICS 365 + AZURE
COMMERCIAL
↓
ONE OPERATIONAL PICTURE
↓
OPERATIONS

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.

PLATFORM PREVIEW — Allocation matrix
Voyage WW-2087 · Deck allocation matrix 1 conflict flagged AUTOMOTIVE HIGH & HEAVY AGRICULTURAL PROJECT Deck 1 78% — — — Deck 2 92% — — — Deck 3 65% 100% — 25% Deck 4 — 45% 30% 45% ⚠ Deck 3 H&H at capacity . Rotation impact: +6h discharge
Illustrative — allocation by deck and cargo segment, with rotation conflicts flagged before they hit the schedule.
Built through real operator implementations

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.

Wallenius
Wilhelmsen Ocean
EUKOR
UECC
Polaris
Reference · delivered by Cartagena, the team behind CargoVerse
«The Wallenius Wilhelmsen group selected Cartagena AS to deliver the modernization of its Microsoft Dynamics 365 CRM suite. The new platform equips teams worldwide with a tool to manage customer relationships, efficiently configure and price shipping rate quotes, and manage contracts.»
Wallenius WilhelmsenWallenius Wilhelmsen · D365 CE & CPQ suiteDelivered 2025 · Platform managed by Cartagena today

CargoVerse was developed by consultants, architects, and solution specialists who have worked exclusively with RoRo and PCTC operators since 2012.

CargoVerse is the productisation of more than a decade of RoRo and PCTC 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 people behind CargoVerse

Shipping people and platform engineers.

CargoVerse is built by Cartagena: consultants, architects and developers who have worked with RoRo and PCTC operators since 2012. Our development team in Bangkok has worked together in international shipping since 2014.

Cartagena's development team in Bangkok
The development team in BangkokSoftware engineering with RoRo domain knowledge
Glenn-Robert Monsen
Glenn-Robert MonsenCEO
Bjørn Lundell
Bjørn LundellCOO
What goes away

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 premise

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
Talk to a specialist Request Demo