B2B Logistics / Maritime Supplyfinal-feedback
Ship-Supply Operations Platform
Internal operations system for a ship-delivery supplier — unified orders, quotes, invoices, and inventory across departments.
- Modules
- Orders · Quotes · Invoices · Inventory
- Migration
- AWS Lambda + Cognito → Supabase
- Status
- Final feedback cycle
Timeline: In active rolloutStack:Next.js 15TypeScriptSupabase (Postgres + Auth)Tailwind v4
Context
A ship-delivery supplier serving commercial vessels needed to replace a scatter of spreadsheets + legacy tools with a single internal system. Departments (sales, operations, finance) were each tracking parts of the same order in different places.
Challenge
- Quote → order → delivery → invoice workflow fragmented across tools
- Inventory visibility lagged behind reality (manual counts, late updates)
- Authentication + permissions sprawled across AWS Cognito + custom logic
- Legacy stack (AWS Lambda + Cognito) was expensive to operate for the team's size
Solution
A modern, internal Next.js 15 App Router app with Supabase as the single source of truth:
- Unified order lifecycle: quote draft → approval → fulfillment → invoice
- Role-based access (sales / ops / finance / admin)
- Live inventory synced with order state
- Migrated off AWS Lambda + Cognito to Supabase in 2026-04 — same feature set, lower operating cost, faster iteration
Status
Core modules are live internally. The system is in the final-feedback cycle with the client — last round of UX tweaks before full handover and training.
What this proves
End-to-end internal B2B operations systems are deliverable in months, not years — including legacy stack migration as part of the scope.