Order to Freight Proof: four roles, one shipment

An ERP earns its keep in different days for different people. This guide walks the demonstration shipment — ORD-2601, 24 t of malt barley from Edmonton to Calgary — through the four roles that touched it, on the records they actually worked. Everything below happened on this live system.

The shipper: Prairie Malt Processors

The shipper’s thread is short because the system carries it: the order was taken in once — shipper, consignee, lane, weight, terms — and everything after named that order. When the load was out, the shipper followed it on their own view link, no account, no login: the board posting, the bids as they resolved, the dispatch, the tracking milestones, and at 11:15 the storm exception with its revised ETA — visible at the same time the operator saw it, from the same record. The invoice that closed the shipment, INV-0001, totals exactly the accepted bid plus the itemised waiting time and GST. The signed proof of delivery sits behind the same link as a document entry with its hash.

The dispatcher: the desk that runs the day

The dispatcher’s day starts from the position, not from assembling it: the dashboard’s approvals, exceptions and overdue items across the suite, and the Freight Progress panel on each open order. For ORD-2601 the dispatcher posted the load at rate-on-request, watched two bids land, accepted the lower bid on the record (the other bid declined itself, on the record, for the carrier to see), confirmed the load plan, and put the dispatch up for the workflow’s second-wallet approval — the control that means no truck rolls on one signature. When the storm exception landed at 11:15 it was already in front of the desk as an open exception with the corridor note from the route record; the decision — proceed at reduced speed, hold the 2A alternate in reserve — is written on the tracking record it was made against.

The carrier: Delorme Transport, owner-operator

Delorme Transport is one truck and its owner, and the system treats that as a full participant, not a small tier. The carrier sits on the Carrier register as Active — insurance and safety rating on the record. The bid was placed under the carrier’s own wallet: a 53-foot dry van, ready on the pickup date. It was accepted, and that bid — typed once, by the carrier — became the load plan’s rate and the freight bill’s linehaul without anyone re-typing or shaving it. After delivering in Calgary at 14:20, the same operator posted capacity on the return lane and bid on the Calgary → Edmonton return load: accepted, booked, and the truck ran home earning instead of empty. A carrier-filtered portal of their own — seeing only their freight, in their own view — is the one named platform step still ahead (it rides the platform’s wallet-to-company binding work); today the carrier works the shared record set as a collaborator under their own wallet and personal module holds, the same gate law as everyone else.

The second wallet: the dispatch approval

One role in this run is a control, not a job title: the workflow’s dispatch approval is assigned to a second member of the operation — the template names the Dispatcher role — and the haul does not proceed until that approval is decided on the record. On this demonstration tenancy the approval resolved to the tenant owner’s session under the platform’s designed fallback, because the bench tenancy carries no second active member; the two-signature path itself is the template’s design and is stated here plainly rather than dressed as exercised with two people.

Why one record matters

Four roles, four different days, one shipment file. The shipper’s invoice is the carrier’s bid; the dispatcher’s exception is the shipper’s exception, at the same minute; the proof of delivery is a hash anyone can check. That is what the token gate buys: not software rental, but a single record of the freight that every party can stand behind — held, never spent, at 1 IMP per module per month.