# Logistics OS

Courier operations platform, 2026.
Concept project: a self initiated study. The brand is fictional; this is not client work.
Interactive demo: https://magrus.vercel.app/demo/logistics

Courier operations on one platform, from booking to cash.

## Objective

A courier company often runs on separate tools and phone calls: bookings in one place, dispatch in another, drivers reached by phone, vehicles tracked in a notebook and cash on delivery in a spreadsheet. Nobody sees a parcel's whole journey, and money slips through between the van and the bank. We designed one platform where every booking, trip, vehicle and payment shares the same record.

## Approach

- One shipment record runs through everything: booking, pricing, dispatch, delivery, invoicing and reconciliation all read and write the same entry.
- Prices come from written rules, so a quote no longer depends on who answers the phone.
- An admin sees the whole business; a dispatcher sees pickups and free drivers; a driver sees today's stops; a customer sees their own parcels; finance sees invoices and the cash still to collect.
- Every status change tells someone: the customer gets an alert, a failed delivery opens a follow up task, and the admin gets a daily summary.
- The demo runs in the browser on sample data, so anyone can switch between the five roles and try each screen.

## How the system fits together

Parts:
- Customer (build layer, person)
- Dispatcher (build layer, person)
- Driver (build layer, person)
- Finance (build layer, person)
- Admin (build layer, person)
- Booking (build layer, surface)
- Dispatch screen (build layer, surface)
- Driver screen (build layer, surface)
- Fleet (build layer, surface)
- Finance screen (build layer, surface)
- Admin dashboard (build layer, surface)
- Pricing (intelligence layer, engine)
- Dispatch (intelligence layer, engine)
- Shipment record (intelligence layer, store)
- Notifications (intelligence layer, engine)
- Reconciliation (intelligence layer, engine)
- Activity feed (intelligence layer, surface)
- Tracking page (growth layer, surface)

Connections:
- Customer → Booking
- Booking → Pricing
- Pricing → Shipment record
- Dispatcher → Dispatch screen
- Dispatch screen → Dispatch
- Dispatch → Shipment record
- Driver → Driver screen
- Driver screen → Shipment record
- Admin → Fleet
- Fleet → Dispatch
- Finance → Finance screen
- Finance screen → Reconciliation
- Reconciliation → Shipment record
- Shipment record → Notifications
- Notifications → Activity feed
- Notifications → Tracking page
- Customer → Tracking page
- Activity feed → Admin dashboard
- Admin → Admin dashboard

## Features

### Booking with tracking numbers

A customer or a dispatcher books a pickup, the price comes from the pricing rules, and the shipment gets its tracking number straight away.

### Dispatch and driver assignment

Dispatchers see waiting pickups beside the drivers and vehicles that are free, and assign each job from one screen.

### A phone friendly driver screen

Drivers see their stops in order, update each status, record why a delivery failed, and capture proof of delivery at the door.

### Fleet, maintenance and fuel

Each vehicle carries its maintenance schedule, fuel log and running costs, so the admin can see which vans are due for service.

### Finance and cash on delivery

Invoices and payment records sit beside the cash each driver collected, so finance can reconcile cash on delivery at the end of each day.

### A tracking page for customers

Customers enter a tracking number and see where their parcel is, without calling anyone.

### Admin dashboard and activity feed

The admin sees the day at a glance, and an activity feed logs each automation as it runs: customer alerts, follow up tasks for failed deliveries and the daily summary.

### Five roles, five views

Each person sees the screens their job needs, and in the demo a role switcher moves between all five.

## How we would build it

- Kickoff, Requirements and scope: We agree the requirements, the scope and the plan, and who signs off each milestone.
- Week 1, Accounts and roles: Sign in, the five user roles and what each may see, and a first dashboard to land on. Demo screens: Role switcher.
- Week 2, Customers and booking: Customer accounts and branches, then a booking flow that gives every shipment its tracking number. Demo screens: Booking screen.
- Week 3, Pricing and dispatch: Pricing rules and pickup scheduling, then the screen where dispatchers assign drivers. Demo screens: Dispatch screen.
- Week 4, The driver's day: The screen drivers use on the road: status updates, failed deliveries with a reason, and proof of delivery. Demo screens: Driver screen.
- Week 5, Fleet: Vehicles, their maintenance schedules, fuel logs and running costs. Demo screens: Fleet screen.
- Week 6, Money in: Invoices, payment records and the daily cash on delivery reconciliation. Demo screens: Finance screen.
- Week 7, Tracking and reports: The customer tracking page, notifications, dashboards and financial reports. Demo screens: Tracking page, Activity feed, Admin dashboard.
- Week 8, Launch and handover: Testing and fixes, going live, then documentation and a handover to your team.

## Craft

- The demo runs on sample data in the browser.
- Pricing, dispatch and reconciliation logic is plain TypeScript with automated tests.
- The driver screen is sized for a phone held in one hand, with large touch targets.
- A role switcher moves between the five views; there is no sign in.

## Results

This is a studio concept, so there are no client results. What it's built to show: what one shared record changes for a courier team, from booking desk to doorstep, and a plan for building it in weekly steps.

## Credits

Credits: the team. Disciplines: Product design, Full stack engineering, Automation.
Stack: Next.js, React, TypeScript, Tailwind CSS.

Source: https://magrus.vercel.app/work/logistics-os
