Courier Management System Project: Android Pickup Scheduling and Live Tracking

A courier management system is an Android app that books doorstep parcel pickups, prices them before the courier arrives, and tracks each parcel through scan checkpoints using its AWB number. Booking a courier by phone or WhatsApp leaves the customer with no written slot, no price until pickup, and no tracking until someone calls back — the parcel is effectively invisible between handover and delivery. This project replaces that with one app: the customer books a slot, sees the price live, and follows the parcel from pickup scan to OTP-verified delivery, while the courier's handset records every scan. Bookings and scans are stored locally in Room so the app keeps working offline, and WorkManager syncs them in the background when the network returns. The demo build covers the Pune–Mumbai corridor with four parcels and six scan stages, and the same design extends to any city pair.

This is a built-to-order software project: the Android Studio source, the clickable app demo, and the complete viva kit (report, PPT, Q&A) are prepared fresh for you.

Booking by phone vs this app

A booking starts on the customer's phone and ends with an OTP handover at the receiver's door, and every step in between is a scan that both sides can see. The customer fills the pickup form and the app prices the booking from the rate card while checking the chosen slot against the clock; the booking is saved to the on-device Room database immediately, so a dead network never loses it. WorkManager carries the booking to the server when connectivity returns, the courier's handset scans the parcel at pickup, and each hub scan appends to the timeline that the customer and receiver watch. Because a status can only change through a scan, the timeline is an honest record of where the parcel has actually been — and the OTP handover at the end is the only step that needs the receiver present. Nothing is invented between scans, and nothing is shown before its scan exists.

1. The customer enters the pickup address, destination city, parcel weight and parcel type on the booking screen.
2. The app prices the booking live from the rate card and offers today's five two-hour slots, disabling any slot that has already passed.
3. On confirmation the booking is written to the Room database with a generated AWB number, and a WorkManager job syncs it to the server when the network is available.
4. The courier scans the parcel at pickup; the scan fixes the booked weight, starts the timeline, and triggers an FCM notification to the customer and the receiver.
5. Every hub scan — departure, sorting, out for delivery — is appended to the timeline with its time and place; the customer watches progress by AWB number.
6. At the door, delivery completes only when the receiver shares the 6-digit OTP; the handover is recorded against the AWB number and the parcel moves to Delivered.

Tech stack:

• Kotlin
• Jetpack Compose
• Room database · SQLite
• WorkManager background sync
• Firebase Cloud Messaging
• Retrofit · REST API
• Material Design 3
• Android Studio · Gradle

The app is built around four capabilities that work together. The pickup scheduler is the entry point: address, destination city, weight and parcel type, then one of five two-hour slots, with past slots disabled by comparing each slot start against the device clock. The live price estimator reads the same three-zone rate card the customer can open, so the ₹139 quoted for a 1.2 kg Pune–Mumbai parcel is traceable to the table. The tracking screen shows the parcel's six scan stages rather than a guessed location, and the offline-first Room store keeps every booking safe when the network drops. Around those four sit the parcels list with four parcels, the courier card with a call action, and an OTP handover that closes the delivery with proof instead of a verbal confirmation.

• [Pickup scheduling with slot picker] The customer enters a pickup address, destination city, weight and parcel type, then picks one of five two-hour slots for today. Slots whose start time has already passed are disabled by comparing against the device clock, so a pickup can never be booked in the past.
• [Live price estimator] The price updates as the form changes, computed from the rate card: three zones (same city, metro, national) with a base price up to 0.5 kg and a fixed charge per extra 0.5 kg slab. The demo's 1.2 kg Pune–Mumbai parcel prices at ₹139, matching the rate card exactly.
• [AWB tracking with scan timeline] Entering an AWB number shows the parcel's six-stage scan history — Booked, Picked up, Departed hub, In transit, Out for delivery, Delivered — with the time and place of each scan. A status can only advance when a scan exists, so the timeline can never jump ahead of reality.
• [Courier card with call action] The tracking screen names the assigned delivery partner with vehicle, rating and trip count, and offers a one-tap call. The demo courier is Rahul Kamble, bike, 4.8 stars across 312 trips.
• [Parcels list] All of the customer's parcels in one list with AWB number, route, status pill and price, so repeat bookings and delivered parcels stay visible without re-entering numbers.
• [Rate card] The full tariff in the app — base price and per-slab charge per zone, plus fragile handling, COD fee and fuel-surcharge notes — so the price the estimator shows is always traceable to a published table.
• [Offline-first storage and background sync] Bookings, scans and slots live in a Room database on the device, and WorkManager syncs them when the network returns. Periodic sync runs at most every 15 minutes, the minimum interval Android allows for periodic work.
• [OTP-verified delivery handover] Delivery completes only when the receiver shares the 6-digit OTP sent to their phone, and the handover is recorded against the AWB number as proof of delivery.

• Complete Android Studio project source in Kotlin with Jetpack Compose UI
• Room database schema with DAOs for parcels, scans and slots
• WorkManager sync worker and FCM notification wiring
• Clickable app demo (booking, tracking, parcels list, rate card) with realistic Indian data
• Project report PDF (background, design, methodology, architecture, results)
• PPT presentation for final review
• Viva Q&A preparation document (Room, WorkManager, FCM, offline-first design, OTP flow)
• Rate-card configuration and a test checklist covering booking, pricing, sync and handover