Every order not yet on a run, in one list. The 🏷 chip is the run tag your sales team typed in eSuite (orders without a chip just weren't tagged — they're under "No run tag"). Pick a run on any row, or All → new run ⚡ a whole group.

Orders appear here grouped by run once they load.

Orders load automatically when you sign in, and plot on the map as violet dots. Press Refresh any time to pull the latest.

Two-way messages with drivers (their Chat tab). Reply below; they get it instantly.

No driver messages.

Address notes drivers sent from the road — fix the customer record, then mark done.

No address updates.

Goods sent back by drivers, with reason and photos — for you to process (credit / restock).

No returns to process.

No failed deliveries.

No incidents reported.

Receipts drivers submitted — review the photo, then approve or reject. Approved claims will feed actual-vs-estimated cost on the Dashboard.

No expense claims.

Service reminders, faults drivers flagged in their post-run check, and anything the team logs here.

No vehicle issues.

No drivers yet — add your first below.

Tap a vehicle for its full record — service, rego, repairs, tyres, inspections, odometer history and linked issues.

No vehicles yet.

Loading…

No drivers sharing location right now.

No active runs right now.

Per-driver stats over the selected period. Pulls from runs (delivered/failed/unload times/km), shifts (hours worked), and approved expenses.

Pick a date range to see driver stats.

Dispatch a run to see today's cost estimate.

Draw delivery areas on the map → tap the map to drop points, then Finish. Build a whole zone into an optimised run in one click.

Loading zones…

Loading customers…

Loading run history…

Optionally give each weekday its own number, so a different person looks after the drivers each day. Leave a day blank to fall back to the default.

These prefill new runs and back the capacity & planning warnings.

These feed the cost breakdown on the Dashboard. Drivers don't see the dollar amounts — they only see distance & time on their app.

Run weights now come from each order's LINES: random-weight items use the actual kg entered on the order, and carton items use the product's packing (e.g. "12 x 700g" = 8.4 kg, "20L" oil = 20 kg). This number is only used for items whose packing has no weight (e.g. "8pcs") — the capacity bar shows how many stops needed it.

Used to estimate a run's weight from its cartons and compare to the truck's capacity (set each truck's capacity under Vehicles).

Customers whose eSuite notes mention "signature" always require one.

Comma-separated — the methods drivers can choose from.

Placeholders: {name} {driver} {link} {stops}. SMS only sends to Australian mobiles (04…).

Customise the public page customers see when they open their tracking link.

Alerts show on the Dashboard. Email sending isn't switched on yet — this records where they should go.

Every delivery-run tag your sales team types in eSuite (TransUserStr1), with what KIND of run it is — that drives the whole board: Regional runs build as-is · the Sydney pool gets split across drivers each morning · Sydney driver tags ARE your drivers (they feed the pool) · Pickup and Transport show as info lists (no truck run). New tags are picked up from eSuite automatically at 6am — or check now:

The pool "Split Sydney" creates a run for each morning. It automatically includes every tag marked "Sydney driver" in the Runs list above (which syncs from eSuite) — this list is for EXTRAS only: casuals or drivers eSuite doesn't tag yet. No need to repeat names that are already driver tags.

eSuite account category codes and what they mean (RES = Restaurants, etc.). Stored here so you can keep it up to date — ready to show on the Customers screen.

Maps the eSuite user number (the order's CreatedUser) to a name, shown as "by …" on Outstanding orders. The list below is prefilled with the user numbers seen in your recent orders — just type each name and press Save. (155 / 59 / 154 are staff; -2 / 0 / -1 are system/online imports.) To refresh the full list, run select userno, userlogin, username from users in eSuite and paste it below.

Who can sign in to this office console, and what they're allowed to do. Add each person's login email and pick their level:

You (bevanwong@taitung.com.au) are always an admin and can't be locked out. Drivers use the separate driver app and don't need to be listed here.
⚠ Right now this controls what each person sees in the app. To make it a hard lock at the database level too, just say the word and I'll switch on the server security rules.

👥 Who can log in and what they can do now lives under the Team & access tab above.

Connections: eSuite ✓ · Google Maps ✓ · Twilio & Drive are configured via secure server secrets.