Skip to main content

Dev Station Technology

Transport and logistics

Logistics software that keeps working when the signal drops

Dispatch consoles, driver apps and the proof that ends a delivery dispute. Built for operators who lose money in the gap between what the office knows and what the driver is doing.

68Dispatcher calls a day before the build
42Trucks on the first deployment
16Screens on one refresh cycle
40+Developers on staff
What this is

One gap, and everything follows from it

A customer rings about a drop. The dispatcher does not know, the driver phone is engaged, and the warehouse remembers something different. Close that gap and most of the other problems stop being problems.

Offline is not optional

Loading bays and steel-framed units kill mobile data. Records are written to the phone first, then drained from a queue the driver can watch.

Proof ends the argument

Receiver name, PO number, a photo and a signature before a drop can be closed.

Services

What we build for transport operators

Dispatch consoles

Every screen on one refresh cycle, so the office is looking at the same minute the driver is in.

Driver apps that work offline

Written to the device first, queued, and visible to the driver so nobody wonders whether it sent.

Proof of delivery

Receiver, PO number, photo and signature captured before the drop closes.

Loading and manifest checks

Every consignment scanned at the dock, or the truck does not leave with it missing.

Route sequencing

Stops reordered with the saving stated in kilometres, not asserted in a slide.

Telematics ingest

Position and engine data over MQTT, with a broker in front so the console stays responsive.

Records

What an operator has to be able to produce

The compliance side decides the data model before anyone argues about screens.

Daily walkaround checksA check in every 24-hour period the vehicle is in service, with a system for reporting and recording any defect that affects roadworthiness.
Driver defect reportsDVSA licensing guidance expects the report and the rectification work to be kept for 15 months, showing who the defect went to and what was done.
Nil defect recordsKept for a shorter period, and operators differ on how long. Decide the retention rule during the build, before an audit asks.
Delivery evidenceNo regulation requires it, but six disputes a month at around three hours each is the number that usually pays for the work.
Case study

Forty-two trucks, nine spreadsheet tabs, one dispatcher

TruckFleet Labs dispatch console and driver app built by Dev Station
Logistics

TruckFleet Labs

A short-haul operator ran 42 trucks on a spreadsheet with nine tabs and a group chat holding 61 people. We built a dispatch console and an iOS driver app where every record is written to the phone first.

68Dispatcher calls a day before the build
Who we build for

The operators who call us

Short-haul and distribution fleets

Teams where one dispatcher holds the whole picture and nobody else can cover the desk.

Third-party logistics providers

Operators answering to customers who want evidence, not reassurance.

Own-account fleets

Manufacturers and retailers running their own vehicles alongside everything else.

Telematics and fleet software vendors

Product teams who need the field app their platform is missing.

Related reading: IoT fleet management, offline-first apps and vehicle inspection apps.

FAQs

What buyers ask first

Can you integrate with our telematics provider?

Usually yes. Position and engine data normally arrive over MQTT or a provider API, and we put a broker in front so a hundred units reporting at once does not slow the console down.

What happens when a driver has no signal?

The record is written to the phone and queued. The driver can see the queue draining, so nobody has to guess whether a delivery was recorded.

Do we have to replace our whole system?

No. Most engagements start with one workflow, usually proof of delivery or the dock check, and grow from there.

Who owns the code and the cloud accounts?

You do, from the first commit. Repositories and cloud accounts stay in your name.

Tell us where the phone calls come from

Thirty minutes with the engineers on the workflow that costs you the most time. If a platform on the market fits better, you will hear that on the call.

Let's Talk