ParcelFly — Delivery Management System
A logistics platform for domestic and international parcel operations, merchant accounts, hubs, courier partners, tracking, COD, and financial workflows.
2
shipping scopes
6+
parcel operations
COD
payment support
The brief.
-
problem
Parcel operations span merchants, hubs, delivery personnel, couriers, tracking events, and accounting.
-
overview
Built a logistics system managing parcel lifecycle from pickup through tracking and settlement.
-
solution
Built Laravel features for parcel management, tracking events, merchant/hub workflows, shipping rates, and delivery finance.
-
role note
I focused on parcel operations, tracking, merchant workflows, shipping rates, and delivery finance features.
-
business goal
Provide one system for parcel operations, merchant workflows, courier coordination, and COD finance.
Modules I worked on
Stack
Laravel PHP MySQL REST APICase study.
Personal project — built as a core product. The notes below describe the product and what I built.
Project Overview
ParcelFly is a delivery-management application for managing parcel operations from pickup through tracking and payment settlement.
What I Built
I built features for parcel operations, tracking, merchant workflows, shipping rates, and delivery finance as a core product.
Operational Scope
The platform includes merchants, shops, pickup requests, hubs, delivery personnel, parcel status updates, courier companies, COD payment methods, support workflows, and financial records.
Shipping Features
Domestic and international shipping use separate rate and insurance structures. International workflows also include pre-alerts, commodities, events, and plan subscriptions.
Implementation notes
The parcel lifecycle is modelled as an explicit status machine: pickup-requested, collected, in-hub, in-transit, out-for-delivery, delivered, or returned. Every transition writes an immutable tracking event, which is what the public tracking endpoints and merchant timelines replay. COD settlement runs on a per-hub ledger with reconciliation reports that match courier remittances against delivered parcels, so accounting sees a closed loop per payout cycle instead of scattered records.
Rate calculation separates domestic and international pricing into their own structures. International shipments additionally carry pre-alerts, commodity declarations, and plan-based insurance, all validated before label generation so bad payloads fail early. Merchant onboarding, hub assignments, and delivery-personnel accounts share one role system with scoped permissions, and status webhooks notify merchants on every transition their integrations subscribe to.