QR Delivery and Proof-of-Delivery System
One-sentence explanation
A full-stack application that generates QR-coded labels for shipments and store transfers, logs tracking events as they're scanned, and gives customers a live, shareable delivery status page.
The problem being solved
Retailers moving inventory between stores — or shipping directly to customers — need an auditable record of where a package has been and who scanned it, without building or paying for a full carrier integration for internal transfers. A lightweight, self-hosted QR-based tracking system covers that gap: generate a label, scan it at each handoff point, and give both staff and customers visibility into status.
Planned architecture
Label generation
QR code + shipment/transfer record
Scan events
Authenticated staff scanning app
Tracking API
Event log, status derivation
Customer status page
Public, link-based, no login required
Technology stack
Nuxt for both the staff-facing (authenticated) scanning interface and the public customer-facing status pages, a PostgreSQL-backed event log as the source of truth for tracking history, and server-side QR code generation tied to each shipment or transfer record.
Current status
Concept — design complete, implementation not yet started. This is the most full-stack of the planned public projects — auth, structured data, real-time-ish status, and a public-facing page all in one system — and the one I'm most looking forward to building. No public repository exists yet.
What I expect to learn
The interesting design problem here isn't the QR codes — it's modeling delivery/transfer state as an append-only event log rather than a single mutable "status" field, so the customer-facing page can show real history instead of just a current snapshot.
Planned improvements
- Native barcode/label printer integration
- Delivery ETA estimation from historical scan data
- Customer notifications on status change
- Multi-tenant support for more than one store network