WhizCloud
Case study · Chapter 01
Shipping & Cargo

From email-driven shipping ops to one self-service digital front door.

Partner Shipping — an integrated digital platform for a global container shipping carrier that connects schedule discovery, quotes, bookings, tracking, claims, and content publishing into a single ecosystem backed by live enterprise integrations.

Chapter 02
The challenge

Customer interactions were fragmented across email, PDFs, and spreadsheets.

Quotes took days. Bookings were re-keyed. Tracking required phone calls. Claims arrived as narrative emails. Marketing waited on developer releases — and shippers expected self-service.

01

Email-driven quotes

Quotes returned days later as unstructured PDFs — extending sales cycles and consuming commercial teams.

02

Spreadsheet bookings

Bookings required re-keying into operational systems, causing errors and duplicated effort.

03

On-request tracking

Updates delivered by phone or email generated high service volume and eroded trust.

04

Opaque claims & content bottlenecks

Claims lacked structured evidence; marketing depended on developer release cycles.

Chapter 03
Project Context

Client

Global container shipping carrier

Industry

Maritime logistics & B2B shipping

Integrations

Schedule · Pricing · Tracking · Claims

Engagement

Full digital platform delivery

Chapter 04
Research & Discovery

What we learned before we designed anything

Findings from shippers, commercial teams, and operations — the basis for every portal, integration, and self-service decision that followed.

Key findings

Shippers want end-to-end self-serve

Dependency on email for quotes, bookings, and tracking was a source of frustration and lost trust.

Commercial time wasted on prep

Manual quote preparation and booking re-keying should have been automated.

Claims were slow and opaque

Customers lacked status visibility; admins lacked structured evidence to process efficiently.

Content blocked by releases

Marketing could not respond quickly to market changes without engineering involvement.

Enterprise systems stay

Any new platform had to integrate deeply — replacing core ops systems was not an option.

Competitive landscape

Email still dominates carriers

Most container lines still relied on email workflows for quotes and bookings.

Disconnected tracking portals

Tracking tools existed apart from booking and claims, forcing multi-tool juggling.

No unified authenticated ecosystem

Few competitors joined quotes, bookings, tracking, claims, and CMS in one place.

User Persona

Marcus

Logistics Manager · B2B Shipper

Goals
  • • Book quickly with accurate pricing
  • • Track containers in real time
  • • File and monitor claims without chasing email
Pain Points
  • • Waiting days for quotes
  • • Re-keying booking data
  • • No claim status visibility
Chapter 05
Information architecture

Four independently evolvable layers, one shipping experience.

Customer Portal, Claims Portal, Integration Platform, and Headless CMS — API-first so enterprise system changes never cascade into customer-facing code.

Four independently evolvable layers, one shipping experience.
Chapter 06
Designing solution

Self-service as the default across the shipment lifecycle.

Quotes, bookings, tracking, claims, and content share one authenticated ecosystem orchestrated through the integration layer.

Before

Quotes requested by email returned days later as unstructured PDFs.

01
Quote Requests

Instant indicative pricing from live data

  • ✓Schedule-integrated quoting with live enterprise schedule and pricing — no manual PDF prep
  • ✓One-click quote-to-booking conversion that transfers all data automatically
Before

Bookings submitted as spreadsheets requiring re-keying into operational systems.

02
Booking Requests

Structured multi-step ocean freight booking

  • ✓Cargo, dangerous goods, parties, and documents validated at entry
  • ✓Integration layer routes complete data directly to downstream operational systems
Before

Tracking updates delivered by phone or email on request.

03
Track & Trace

On-demand container visibility

  • ✓Operational datalake integration — not manually updated status fields
  • ✓Event-driven notifications for shipment lifecycle milestones
Before

Claims filed as narrative emails; marketing waited on developer releases.

04
Claims & CMS

Guided claims and headless publishing

  • ✓Claims Portal with structured evidence, admin review, settlement, and enterprise handoff
  • ✓Headless CMS with 20+ templates so business teams publish without engineering
Chapter 07
Technology

Built for enterprise logistics depth and independent evolution.

Modular API-first architecture with containerised cloud deployment, RBAC and 2FA, CDN-backed content, and live enterprise integrations for schedule, pricing, tracking, and claims.

Built for enterprise logistics depth and independent evolution.
Chapter 08
Implementation

Map the shipper lifecycle, then separate the layers.

Experience, integration, content, and infrastructure were designed to evolve independently without cross-layer disruption.

01

Discovery

Mapped every customer touchpoint handled by email, phone, or spreadsheet — and the enterprise systems feeding each one.

02

Modular architecture

Designed Customer Portal, Claims Portal, Integration Platform, and Headless CMS as independently evolvable capabilities.

03

API-first design

Built experience apps to communicate exclusively through the integration layer.

04

Self-service workflows

Delivered quotes, bookings, tracking, and claims designed for completion without manual ops responses.

05

Security & launch

Shipped encrypted auth, RBAC, 2FA, bot protection, audit logging, and event-driven notifications.

Chapter 10
Results & Impact

What changed after launch

✓

Self-service end-to-end - Shippers complete quotes, bookings, tracking, and claims without waiting for manual responses.

✓

Single customer dashboard - Active quotes, confirmed bookings, and claim status visible in one place.

✓

Eliminated re-keying - Structured digital intake delivers complete, validated data on first submission.

✓

Automated lifecycle notifications - Confirmations and status updates replace routine manual communication.

✓

Live enterprise data - Schedule, pricing, tracking, and claims integrate with operational systems — not static publications.

✓

Governance and auditability - Audit logging, RBAC, and content trails support regulated B2B shipping operations.

Chapter 11
The Learnings

Challenges & Learnings

Enterprise integration without replacement

Robust integration had to tolerate upstream data variability without modifying core systems.

Keeping layers truly separate

API-first discipline prevented ops changes from cascading into customer-facing disruptions.

Claims workflow complexity

Evidence states, admin review, and settlement had to satisfy shippers and enterprise processing.

Headless CMS adoption

Templates and editorial workflow had to match how business teams think about content.

Audit trail as product

Designing auditability into every transaction from the start built platform trust.

Chapter 12
What's next

Where the platform goes from here

Mobile app for booking, tracking alerts, and claims status
Partner portal for forwarders and agents
Predictive shipment milestone notifications
Expanded dangerous goods regulatory workflows
Commercial analytics for quote conversion and booking volumes
Chapter 13
In their words
“

Partner Shipping has fundamentally changed how our customers interact with us. What used to require emails, phone calls, and manual back-and-forth now happens instantly through the platform.

“Our commercial teams are focused on winning business rather than preparing PDFs, and our customers trust us more because they can see exactly what is happening with their shipments at any time.”

Operations Director, Partner Shipping Company
Partner Shipping Company · Global Container Shipping