Anonymized case study
Customer ordering portal for a 24/7 maritime operation
Phone and email orders left the operations desk re-entering and reconciling changes by hand.
Work shown is anonymized to protect the organizations involved.
01 / Context
The setting
A 24/7 maritime operation needed a shared ordering workflow for external partner companies and its operations desk.
02 / Challenge
What needed to change
Partners submitted and changed service orders by phone and email. Staff had to re-enter the details, reconcile changes, and keep the current order clear.
03 / What I built
The implementation
I built a self-service portal for submitting orders and requesting changes. Staff can approve or reject each change using a side-by-side comparison of the requested and current data.
Duplicate-order detection, time-based editing cutoffs, and validation rules keep the ordering workflow consistent. A third-party vessel-data API verifies and imports records.
Multi-category PDF document submission and role-based dashboards support different users, including a read-only partner view. Full change history, an audit trail, and SMS/email notifications keep changes traceable.
04 / Results
What the work made possible
Around 100 active external users use the portal. Partner adoption rose from under 50% to over 90% in about five months, with several partners reaching 100%.
I shipped 16 feature releases during that period in response to user feedback. Over multiple years, the portal grew from its first build into a core operational system.
05 / Technologies
The tools behind the work
Have a similar problem?
Tell me how the work happens today. I can help you find a practical starting point.