Instruction
Customer or operator creates a shipping instruction and the system generates a work number.
Featured Case Study
BEST GROUP Phase-1 Logistics Operations and Finance System
A delivery-focused system for an overseas freight-forwarding company. The work connects messy operational communication, order milestones, cost requests, finance review, billing, reconciliation, and management summaries into one role-based business workflow.
Problem
The company relied on scattered Excel files, chat records, emails, and manual follow-up to manage shipment progress and financial settlement. That made it hard to see who owned the next step, which costs had been requested, which bills were approved, and how each shipment affected profit.
My Role
I treated the project as a real delivery case rather than a small demo. I organized the requirements into roles, entities, states, workflows, permission boundaries, QA checks, deployment notes, and handoff materials.
System Scope
- Shipping instruction and work-number creation for customer/operator entry.
- Order information and operation nodes such as booking, truck, customs, bill of lading, and arrival.
- Advance receipt, prepayment, and deposit cost requests submitted by operators.
- Finance review, receivable/payable/deposit bill generation, reconciliation, and profit summaries.
- Role-based access for customers, operators, finance staff, branch admins, and HQ admins.
Workflow
From shipment request to financial close
Operations
Operator completes order data and updates booking, truck, customs, bill, and arrival nodes.
Cost Request
Operator submits advance receipt, prepayment, or deposit requests with shipment context.
Finance Review
Finance reviews requests and turns approved records into receivable, payable, and deposit bills.
Reconcile
Finance updates bill status, checks settlement, and produces reconciliation and profit views.
Engineering Value
The project shows that I can convert a messy business operation into structured product modules, database-backed states, API flows, role permissions, and usable UI screens.
Delivery Value
Beyond code, I prepared deployment templates, smoke checks, manual QA notes, requirement documents, traceability notes, and handoff materials so the system could be understood and operated after delivery.
Evidence
Repository evidence for resume review
The GitHub repository is organized as a delivery package, not just source code: product requirements, traceability, QA notes, deployment templates, and frontend / backend implementation are linked together for review.