Enter your work email and we'll send you a sign-in link. Only pre-approved Pacreo team addresses can access this app.
40 Beach St, Kippa-Ring QLD 4021
| Code | Customer | Tier | Phone |
|---|
A load is one trip out of the yard. Drops ticked off on a truck stay on its current load until you press Truck back on that truck's column, which starts the next load. Fix a drop that landed on the wrong load in the deliveries table below.
| Date | Truck | Load | Drops | Run | Zones | First drop | Last drop | Status |
|---|
| Completed | Date | Type | Inv # | Customer | Location | Vehicle / source | Load | Tier |
|---|
Each driver's work phone runs Traccar Client for the live map (Create tracker gives the setup). Drivers open pacreo-delivery-register.vercel.app/driver.html on their phone, tap their name, enter their PIN and pick the truck rego. They see that truck's drops for today and tick them off. The office gets an alert for each one.
{customer} customer name ·
{driver} driver / truck name ·
{invoice} invoice # ·
{po} customer PO ·
{location} delivery suburb / site ·
{time_req} requested window (EARLY / AM / 10AM etc)
On the run sheet: each delivery row gets a small QR code in the notes column. It encodes sms:<number>?body=<template> using the site contact phone for that row (which prefills from the customer's phone but can be overridden per delivery for site-specific contacts like foremen or subbies).
Driver workflow: pull up outside site → scan QR with phone camera → SMS app opens with recipient and message pre-filled → driver hits send. No app install, no login, works offline (the sms: URL is baked into the QR).
Customer receives: a text from the driver's own number. Replies land on the driver's phone which is usually what you want on delivery day for last-mile access queries.
Upgrade path: if this proves out at 60 days and you want centralised logging + a Pacreo-branded sending number, we can switch the QR target from sms: to a Twilio-backed web page — same UI, driver workflow is identical, sender number changes.