Operations
A load has fourteen states, and it cannot skip one.
The lifecycle is enforced, not suggested. A load cannot jump from booked to invoiced because somebody was in a hurry, and every change is written to an append-only history with the person who made it, the time and a note.
Multi-drop and shared loads
One trip delivering to several clients, each drop carrying its own client, pallet count, weight and revenue — so a shared load is costed properly instead of split by guesswork.
The whole load record
Client and client reference, PO and waybill numbers, loading and offload locations, planned against actual times, product description, pallets, weight, and the temperature regime with its target — ambient, chilled or frozen.
Vehicles, drivers and subcontractors
Assign the truck, the driver or a subcontractor with a per-trip rate. Revenue is recorded flat, per pallet or per kilometre, against the distance run.
Customer tracking without a login
Every load carries an unguessable tracking link you can switch on per client. Customers see the timeline; they never see invoiced, paid, or a cancellation. Rate limited, and off by default.