One record per parcel
Pickup, sort, run, attempt, and signature live on the parcel, not in four tools that each hold a fragment.
About
A depot is a promise, sorted by zone.
Manifesto
Every parcel has two audiences: the sender who wants proof and the recipient who wants a knock at the door. Most tools serve one and leave the other to a phone line.
Parcelry is built for the hour where both are true. One record per parcel, one owner per failed attempt, and a tracking link that says the same thing the control room sees. This demo shows that shape with sample data.
How the work is organised
Three habits, repeated.
Failed attempts get a name
A missed door without a reason is a rumour. Every attempt carries a reason and a next step.
The recipient reads the same thing
Public tracking shows the events the board shows. There is no friendlier second version.
What we will not trade
Three lines we keep.
- No number without a sourceEvery figure here is counted from the sample file or labelled Sample. Nothing is rounded up to look better.
- No dark pattern in a formNo pre-ticked consent, no fake urgency, no confirmation that hides what was sent.
- No coverage claim we cannot drawThe runs page draws the runs in the data. If a zone is missing, it is missing on purpose.
A fictional timeline
How the demo got here.
Sample dates, written for this demo. Not a company history.
- Sample 2024
One route sheet
A printed run sheet, a phone, and a driver who knew the doors.
- Sample 2025
The board takes shape
Runs, attempts, and exceptions on one screen, with a public tracking page for the recipient.
- Sample 2026
Services and zones
Service pages, zone runs, and a quote request that collects scope without quoting a rate.
- This build
A template, not a product
Two brands, one codebase, sample data throughout. The docs explain how to swap both.
The roles behind the demo
Fictional roles, real responsibilities.
Roles are illustrative. No real person is named or photographed.
-
Route dispatch
Owns the run plan, the cut-offs, and the calls that keep a window from slipping.
-
Hub sorting
Owns the cage plan, the intake scan, and the discrepancy list that leaves the door.
-
Customer support
Answers the recipient with the same events the board shows, and writes down what was missing.
-
Data and reporting
Keeps the charts counted from the file, and refuses to add a figure that has no source.
Where to go next
See the night as a working board.
The dispatch board is the same story with the sample file loaded.