Build a courier and parcel tracking system

You are a developer who builds logistics software.
I work in Logistics & Supply Chain: a logistics company running warehouses and a delivery fleet. This work matters to shippers, carriers and warehouse teams.

## Goal
Build a system for booking parcels, assigning them to riders, and tracking them until delivery.

## What matters in Logistics & Supply Chain
- People involved: warehouse managers; dispatchers; drivers; fleet managers; customs brokers; shippers.
- Rules and standards that usually apply: driver working-hours limits; road safety and vehicle fitness; customs and trade paperwork (HS codes, e-way bills and GST in India); dangerous-goods rules; insurance and liability terms in contracts.
- Numbers that matter: on-time delivery rate; OTIF; cost per shipment; fleet utilisation; order accuracy; damage rate; dock-to-stock time.
- Common risks to plan for: missed delivery windows; fuel price swings; damage and theft; customs holds; driver shortages.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Service area and volume: [CITIES, PARCELS PER DAY]
- Users: [customers, branch staff, riders, admin]
- Payment types: [prepaid, cash on delivery]
- Stack: [STACK]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Summarise what you understood about the product, its users and the launch scope. Point out anything unclear or contradictory and ask before you guess.
2. Build parcel booking with rates by weight, zone and speed.
3. Generate airway bill numbers, labels and barcodes.
4. Build hub and branch scanning for each movement.
5. Build the rider app: assigned parcels, route order, proof of delivery with photo, signature or OTP.
6. Build public tracking with a timeline.
7. Build cash-on-delivery reconciliation per rider.
8. Build reports: on-time rate, failed deliveries, returns.
9. Give a launch checklist covering security, performance, SEO, accessibility, backups and monitoring.
10. List what is deliberately out of scope for version 1 and what to build next.

## What to deliver
- Plan and data model
- Phase-by-phase build
- Status flow
- Rider app screens
- Reports

## Expert rules
- Build mobile first and make every screen work from 360px wide upwards, with labels, keyboard support and 4.5:1 contrast.
- Validate every input on the server, use prepared statements, hash passwords, protect forms with CSRF tokens and check roles on every admin action.
- Give complete files with full paths; never write "rest of the code stays the same".
- Respect delivery windows, customs rules and driver-hours limits. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Start with the plan (stack, structure, data model, screens), then build in numbered phases.
- Use tables for data models and endpoint lists.
- End each phase with how to run and test it.

## Before you answer
Check your draft against this list and fix anything that fails:
- The answer is practical enough to use today without rewriting.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on on-time delivery rate and cost per shipment.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.