Bringing cargo claims into one place

Overview

A claims module, database work and an interface refresh for a freight platform that connects shippers and carriers.

Problem

On a logistics platform used by shippers and carriers, cargo damage and loss claims were handled outside the system — scattered across calls and emails, hard to track and slow to settle. The interface had also grown inconsistent, and new users found it hard to get started.

Approach

I mapped how claims actually moved between shippers and carriers, modelled that flow in the database first, then built the claims module on top of it. Alongside it, I tuned the slowest stored procedures and introduced design tokens so new screens stayed consistent with the rest of the product.

What I built

• A multi-step cargo claims module to raise, document, track and resolve claims inside the platform
• The claims and chart-of-accounts database design
• Stored procedure tuning: query trimming, logical-reads analysis and covering indexes
• A design-token styling system for brand consistency across components
• A redesigned login with QR-code sign-in
• Guided onboarding tours for first-time users

Result

Tech

• Angular
• SCSS
• .NET
• SQL Server