Six shipping workflows moved out of spreadsheets into one operations system.
CASE STUDY
·
2026

Six shipping workflows moved out of spreadsheets into one operations system.

Wood industry group, maritime shipping operation.
SHIPPING OPERATIONS SYSTEM · CONTAINER EXPORTS

WORKFLOWS

6

PLANNING TO REPORTING, IN ONE SYSTEM

VGM

Calculated

TARE AND VERIFIED GROSS MASS PER CONTAINER

ACCESS

Role-based

ONE RECORD PER SHIPMENT

DATA

Unified

ONE STORE INSTEAD OF A FOLDER OF FILES

SITUATION

Container exports ran on spreadsheets that nobody could audit and everybody had to update.

Planning, booking management, container execution, tare and verified gross mass calculations, documentation tracking and operational reporting each lived in its own set of Excel files, kept by hand, hard to audit and slower with every added container.

WHAT WAS BUILT

A shipping operations system with a structured workflow for each of the six, one data store behind all of them, the tare and verified gross mass calculated in the system for every container, configurable reporting, and role-based access, so each person sees and edits what their role allows.

HOW IT RUNS

As a centralized secure web platform for the shipping operation, with every change recorded against the user who made it.

WHAT CHANGED

One record per shipment from planning to documentation, a verified gross mass that comes out of the system rather than a calculator, and an audit trail where there was a folder of files.

THE STACK

WORKFLOWS
Planning, booking, container execution, tare and VGM, documentation, reporting

DATA
Unified store, one record per shipment

ACCESS
Role-based, change history per user