Order timeline integrity
Every status transition is recorded with a timestamp and cannot be modified after the fact. The timeline is the single source of truth for what happened on an order.
Proof and control
Operational trust, not marketing trust
Trust in logistics means you can verify what happened, not that someone told you it went well. Here is how LuLuGo builds that verification into every order.
Trust record
Delivery proof package
Pickup
Drop-off
Item
DeliveredTimestamped status transition
Audit trailQuote, assignment, POD, payment aligned
PaymentConnected to confirmed dispatch
Proof of delivery
Delivery proof is not optional — it is built into the completion workflow. Drivers cannot close an order without uploading the required evidence.
Payment and contract integrity
Payment is tied to the dispatch contract, not to informal agreements. The financial trail follows the same path as the operational trail.
Access control
Different roles see different things. The console, the customer portal, and the driver portal each have their own permissions — and territory-based operations ensure that access is scoped appropriately.
Privacy and legal
We handle delivery data, route information, and payment records with care. For detailed policies, see:
Order timeline integrity
Every status transition is recorded with a timestamp and cannot be modified after the fact. The timeline is the single source of truth for what happened on an order.
- Every status transition is timestamped and immutable
- Quoted, assigned, picked up, delivered — each recorded as it happens
- No manual overrides that bypass the audit trail
- Your team, your customer, and the driver all see the same timeline
Proof of delivery
Delivery proof is not optional — it is built into the completion workflow. Drivers cannot close an order without uploading the required evidence.
- 3 photos required on every delivery — enforced by the system
- Optional signature capture when the recipient is present
- POD attached to the order record permanently
- Available in your account for reference or dispute resolution
Payment and contract integrity
Payment is tied to the dispatch contract, not to informal agreements. The financial trail follows the same path as the operational trail.
- Payment proceeds only after driver confirmation
- Price locked to the quoted route — no post-delivery adjustments
- No charges before the assignment is confirmed
- Financial record matches the dispatch record
Access control
Different roles see different things. The console, the customer portal, and the driver portal each have their own permissions — and territory-based operations ensure that access is scoped appropriately.
- Role-based console access with defined permission boundaries
- Territory-scoped operations for dispatch and driver management
- Separate customer and driver portals with distinct permissions
- Actions are logged — who did what and when
Privacy and legal
We handle delivery data, route information, and payment records with care. For detailed policies, see:
What we do not claim
Trust is also about what we choose not to overstate. Here are the boundaries of what the system does today.
- Tracking is status-based, not continuous GPS streaming — you see timestamped status changes, not a live dot on a map
- Delivery photos are uploaded via URL-based fields, not native camera integration
- We do not claim end-to-end encryption of delivery communications
- Session security is standard web authentication — enterprise-grade session hardening is a future milestone