Noor — Merchant Admin &

Noor — Merchant Admin & Operations Admin

Three production admin systems for a delivery service — built solo end-to-end, including real-time chat and billing logic.

⚠️ Problem

A delivery service needed three separate operational systems working at once: a panel for merchants to manage their own orders and billing, a central ops panel for the company's own courier fleet, and a customer-facing tracking site — each with a completely different user and a different job.

🔒 Constraint

Real production traffic, existing users depending on the systems daily, and — on the merchant panel — real money moving through billing logic that had to be correct, not just functional-looking.

🛠️ Solution

Merchant admin panel: built almost entirely solo (359 of 368 commits) — orders, tariffs, promo codes, invoices, reporting, real-time chat with customers/support (WebSocket), and later real billing logic (cash accounting, commission tracking, payment-status handling).

Central operations admin (cpanel): the company's largest internal system: courier management, live GPS tracking, in-app chat, and the fleet-management/credit system for company-owned courier scooters. Built largely solo through its first year (~84% of commits in that period), then onboarded and reviewed a successor once my focus shifted to the merchant panel's billing work.

Customer-facing delivery website: Next.js 15, React 19 — live GPS courier tracking with animated route rendering, rendering-performance and memory optimization, i18n, Framer Motion, OTP-based auth.

📈 Result

Three systems still running in production today, each shipped and maintained by me for over a year. This is real, closed-source production work — not a personal or practice project.