Every order on one board, whatever door it came in through.

The board is the operation

Almost every problem in local delivery is visible on one screen or invisible entirely. Orders in three systems — email, a spreadsheet, the phone — means the day exists only in somebody’s head, and the first sick day costs you a morning of reconstruction.

So the board is deliberately the single place: every order, whatever it came in on, with the same fields and the same lifecycle. Nothing is retyped between the store and the driver, because retyping is where addresses get broken.

Addresses are the expensive part

A delivery operation’s address book is usually worse than anyone believes. Duplicates entered three ways, unit numbers missing, postcodes that resolve to a town centre two miles from the door.

Geocoding on arrival makes that visible immediately rather than at 3pm on the road. Fleets that clean the flagged addresses once routinely find a few percent of their book was quietly costing a driver ten minutes a stop — which is real money once you multiply it by a year.

Bulk stays bulk

Operations that plan the next day in the evening do it in groups: import the file, apply a window to a batch, assign a zone to a team, reschedule everything that did not fit. Doing that one order at a time is how planning eats an evening.

Import with a per-row error report, multi-select on the board, and batch actions for assignment, windows and rescheduling exist so the group stays a group.

One lifecycle, kept honest

Created, assigned, en route, arrived, completed or failed — with arrivals detected by geofence rather than by a tap, and completions gated on the proof your rules require. Every state change carries a timestamp, which is what makes the reporting worth reading later: the numbers come from what happened rather than from what was planned.