Shipping requests, a dispatcher workstation, proof of delivery and trip margin
Freight is an app for cargo shipping requests and dispatcher work. A request goes from intake to closing, the driver confirms delivery from a phone, and revenue, costs and margin are calculated from actual data.
Dispatch: request counters, exceptions (late to a stop, delivery with remarks), today's stops and a request board by status.
Overview
Freight: what it does and how it works
Freight from request to closing. A request has a customer, shipper and consignee from the shared contact book, loading and unloading addresses with contacts and time windows, cargo (type, weight, volume, pieces), terms and vehicle requirements, planned dates, rate, extra charges and documents. Statuses go in order: new, pending approval, planned, vehicle assigned, loading, in transit, delivered, awaiting documents, closed — or cancelled, or problem delivery; the server won't allow an invalid transition, and won't allow a cancellation, problem or step back without a reason. The dispatcher's workstation: a board by status, trip requests, multi-stop, weight and volume checks against vehicle capacity, manager approval of changes, delays and exceptions, reassignment, an action log.
A trip is requested from Fleet via an event and tracked through its events; without Fleet, the carrier and vehicle are entered by hand. The vehicle comes from the shared Vehicles service, with availability. Proof of delivery from the driver's phone: time, recipient, a drawn signature (not legally binding) or an electronic signature via NCALayer verified by your NCANode service (the screen shows the verification facts: signer, certificate, revocation), photos, a comment, damage, shortage, the reason a delivery failed; resending never duplicates anything. Costs per request and trip — fuel, tolls, parking, repairs, per diems, a hired carrier — are linked with Payments without double counting.
Revenue, costs and margin per request and trip come from actual data, and the customer invoice is in Invoices.
How it works
How to use it, step by step
1
The dispatcher creates a request: customer, loading and unloading points, cargo, dates and rate
2
The request goes through approval and planning and gets a vehicle — from Fleet or manually
3
The driver sees the request in “My deliveries” on their phone and marks route points
4
At unloading, the driver confirms delivery: recipient, signature, photos, remarks
5
The dispatcher receives the original documents and, if needed, signs the confirmation with an electronic signature
6
The customer is invoiced, margin and costs are calculated, and the request is closed
Features
What you can do
Request: customer, shipper and consignee from the shared contact book, loading and unloading addresses with contacts and time windows, cargo (type, weight, volume, pieces), rate and charges
Statuses in order from new to closed; the server won't allow an invalid transition, and won't allow a cancellation, problem or step back without a reason
The dispatcher's workstation: a board by status, exceptions, today's stops, reassignment and an action log
Multi-stop: several loading and unloading points in one request
Checking cargo weight and volume against vehicle capacity
Manager approval of changes
A trip is requested from Fleet via an event; without it, the carrier and vehicle are entered by hand
Proof of delivery from the driver's phone: time, recipient, a drawn signature, photos, comment, damage, shortage or the reason for non-delivery; resending never duplicates anything
Electronic signature of proof of delivery via NCALayer with a timestamp and verification by your NCANode service — the screen shows the signer, certificate and revocation
A link to sign on your own computer and a QR code for eGov Mobile
Costs per request and trip (fuel, tolls, parking, repairs, per diems, a hired carrier) without double counting with Payments
Revenue, costs and margin per request and trip from actual data; shipping finances by month
The customer invoice is issued in Invoices
Screenshots
What it looks like
Real app windows with a fictional company as an example. Click a screenshot to enlarge it.
Dispatch: request counters, exceptions (late to a stop, delivery with remarks), today's stops and a request board by status.Card for a delivered request: completed route points, proof of delivery with the recipient, damage and drawn signature, vehicle and money — revenue, costs, margin.Signing proof of delivery with an electronic signature: the screen shows exactly the data that will go to NCALayer, its SHA-256 and a timestamp from the tsp.pki.gov.kz service.The driver's phone: the request route and proof of delivery — who received the cargo, the recipient's on-screen signature and a damage mark.
Integrations
Works together with
Contacts — customers, shippers and consignees from the shared book
Fleet — requesting a trip via an event and tracking its progress
Vehicle Passport — the vehicle from the shared Vehicles service, with availability
Invoices — the customer invoice for the request
Payments — costs per request and trip without double counting
We are honest about what works only with an external provider or is still planned:
Signature verification requires your NCANode service, and signing requires NCALayer on the signer's computer; without NCANode, the signature is saved as “received, not verified”
Signing through eGov Mobile by QR hasn't yet been tested with the real eGov Mobile
The platform has no map yet — the route is shown as a list of addresses
