Skip to main content
vinu.

Case Study

Storage Cost Management Platform — CMA CGM

Designed and built an enterprise workflow platform to standardize storage guarantee operations across six business teams at CMA CGM — replacing fragmented manual processes that contributed to approximately $16M in annual storage-related financial exposure.

Role · Frontend EngineerType · Enterprise · Internal OperationsStack · React · TypeScript · Redux · Material UI

The Problem

$16M exposed to manual calculation errors

Storage guarantee workflows were owned by six teams — Intermodal, Equipment, Port Operations, DDSM, Client Solutions, and VIP — each using their own approach. Manual calculations meant inconsistent cost recovery, approval delays caused by email chains, and no centralized view of outstanding guarantee exposure. The business needed one standardized platform that all roles could operate within.

Architecture Decisions

How I solved it

Multi-stage workflow modeling over simple CRUD

Storage guarantees follow a real business lifecycle: create → approve → confirm → amend → close. Modeling the UI around these stages — with role-aware transitions and validation gates at each step — made the system far more governable than a generic form with status fields.

Client-side dynamic pricing engine

Storage costs depend on equipment type, terminal, tier pricing, and whether calculation uses calendar days or working days. Encoding this logic in the frontend gave users immediate cost feedback during request creation, reducing incorrect submissions and back-and-forth approvals.

Bulk operations as a first-class feature

Operations teams process dozens of requests daily. Designing bulk update and mass apply functionality from the start — not as a shortcut — meant the platform scaled to actual workload without extra overhead per request.

Frontend validation layer preventing duplicate guarantee periods

Overlapping guarantee periods for the same container caused downstream billing errors. A client-side validation layer caught date conflicts before submission, with role-specific restrictions layered on top to enforce governance at the UI level.

Role-Based Design

Four roles, one coherent platform

The platform exposed different actions to each role — Requestors created and submitted, Approvers reviewed and actioned, Guarantors confirmed commitments, and Administrators managed settings and overrides. Role-based UI controls weren't just a permission layer — they were the primary way the workflow stayed accountable and auditable across departments.

Stack

ReactTypeScriptReduxMaterial UIReact Hook FormMUI Data GridRole-Based Access Control

Outcome

~$16M

Financial exposure area addressed

4 roles

Unified in one workflow platform

7+ steps

End-to-end workflow standardized