Road transport

We build the dispatch and settlement system for trucking companies

AI drafts the waybill and trip settlement from the transport orders and receipts, checks fuel against your norm, then flags late trips without a POD. Built for your dispatch desk, live in days.

See AI handle your own work.

AI enters the trip data

Reads the transport order and the container list the customer sends, and opens the trip with the customer, the route, the containers and the weight already filled in.

AI checks the numbers match

Compares the arriving documents against each other and against what is already on file: cargo weight, drop site and the rate you signed. Anything that disagrees surfaces before the truck is sent.

AI drafts the trip documents

Drafts the dispatch order, the waybill and the freight statement on your own document templates. Your team reviews before anything is sent.

Every trip in one view

The system shows which trucks are on the road, which trips are still waiting on a POD, and which settlements are held over the fuel norm.

The whole trip from order to settlement

Every stage captures the trip, AI drafts the documents and runs the checks, and the next step starts on its own.

  1. 01

    Order intake & quote

    AI reads the transport order email, matches the lane to your rate table, and drafts the quotation with the customer, route, cargo type, weight, and the pickup and delivery dates already filled in. Confirm the order and a trip opens on its own, with the customer linked.

  2. 02

    Dispatch & assignment

    AI checks which trucks are free by area and payload, suggests a match, and drafts the dispatch order, carrying the plate, driver, and planned kilometres onto the trip. The trip moves to Dispatched and the departure time lands on the schedule.

  3. 03

    Loading & waybill

    When the driver's loading photos come in, AI reads the actual quantity, weight, and seal number off them and fills the waybill from the trip record. The trip moves to On the road and the waybill is issued.

  4. 04

    On the road

    As the driver checks in along the route, AI reads each update and refreshes the ETA and trip status against the departure time and the checkpoints passed. The trip stays On the road, and an ETA that starts slipping raises a flag to dispatch.

  5. 05

    Delivery & handover

    At drop-off, AI reads the POD photo and the signed handover record, capturing the receiver, delivery time, and any shortage or damage, and stamps the delivery. The trip moves to Delivered and the customer gets a delivery confirmation.

  6. 06

    Fuel & cost check

    Back from the run, AI reads the fuel and toll receipts and logs the actual kilometres, litres, loading fees, and detention on the trip cost sheet, then computes fuel against the norm. Anything over the norm holds the settlement for review before it can close.

  7. 07

    Settlement & invoicing

    Once the costs are approved, AI drafts the trip settlement and the freight charge statement from the trip record, with revenue, margin, and the receivable totalled. The settlement posts to accounting and the trip margin updates the moment it lands.

Every role gets its own app

Dispatch, drivers, accounting, and managers each get their own app, all reading and writing the same trips.

Dispatch board

Dispatch sees today's trips by stage, which trucks are free, and the delivery windows surfacing in red.

Driver screen

Drivers see the trips assigned to them; they accept a trip, snap the delivery photo, and report costs after each run.

Settlement desk

Accounting works one trip with its costs against the fuel norm and the approve button in a single view.

Fleet dashboard

Managers see trips, revenue, cost per kilometre, and margin by route and by truck.

Nothing routine waits on you

Trip status moves on its own, deadlines get flagged, and settlements are approved before they leave.

The trip stage moves itself

As loading, delivery, and settlement land, the trip stage updates on its own.

Late trips get noticed

A trip past its delivery window without a POD alerts dispatch.

Return trucks get filled

A truck marked returning surfaces to dispatch for the next load before it reaches the yard.

Fuel over norm needs sign-off

A trip burning more than its fuel norm waits on the dispatcher before settlement.

Maintenance never sneaks up

A truck nearing its service interval by mileage is flagged before the next dispatch.

The system works with the AI you already use

Claude, ChatGPT or a coding assistant can read and update the data in it, within each person's own access.

  • Claude
  • ChatGPT
  • Gemini

Switch in days, not months

We start with one thing your team does by hand today. Once that one is running, we take the next.

  1. 01.

    We learn how you work today

    We go through your documents, your rate sheets and how the desk handles them day to day.

    What we need from youOne session, and a sample document set.

  2. 02.

    We build it and walk your team through it

    The system works the way you already do. Your team is doing real work in it inside the first week.

    What we need from youOne person to review it with us.

  3. 03.

    We keep changing and improving it

    When the process changes or new work comes up, you tell us and we do it. The system keeps up with how you work instead of going stale.

    What we need from youA message when something changes.

500 containers a month.The paperwork closes at the gate.

“Documentation used to take around 2 hours/day; now it's usually done in 5 minutes. Most importantly, the team works from one set of numbers instead of conflicting files.”

Phuoc TranPhuoc TranGiám đốc (Director), Conta Vietnam

A copy per desk, reconciled by eye. Lotics keeps one shipment record. A change made anywhere is the change everyone sees.

Read the case study
Frequently asked questions

Typically 1-2 weeks. Week 1: build the data tables, document templates, and import your truck, driver, and historical data. Week 2: train staff and run real trips. Setup is included in the plan.

Time with the team during the audit, your rate table, fuel norms, document templates, and truck and driver lists, plus someone to review as we build. We handle the rest.

Your dispatch, drivers, and accounting use it daily. We stay on to adjust the tables and add automations as your process changes. Ongoing support is part of the subscription.

Yes. We configure it to how you take orders, dispatch, and settle, rather than making you change to fit the software. When your process changes, we adjust the system.

No. The dispatch board, settlement desk, and fleet dashboard all read and write the same trip data — one source of truth, many purpose-built apps onto it. The scattered files and Zalo threads you have now are exactly what that removes, not adds to.

AI checks reported litres against the fuel norm for the truck's actual mileage. Trips over the norm are flagged and the settlement is held for dispatch to review before approval.

A truck marked returning surfaces to dispatch right away. The next load is matched before the truck reaches the yard, sparing a deadhead run.

We connect the data from the GPS monitoring device your trucks already run. Position and mileage flow onto the trip, and drivers update loading and delivery status themselves.

AI fills the waybill content from the trip for your staff to file on the transport authority's software, the way they do it by hand.

Lotics handles order intake, dispatch, trip documents, fuel reconciliation, and settlement, for fleets of 5 to 200 trucks. VAT invoices still issue through the accounting software you already use, with trip data synced across.

Yes. Lotics imports from spreadsheets. Our team brings in your truck, driver, rate table, and historical trip data while we build the system.

Yes. Role-based permissions control who can view, edit, or approve specific records. Each person sees only what is relevant to their role.

Yes. Every change is logged with who made it, what changed, and when. Full history on any record for audits, disputes, or internal review.

Cloud servers in Singapore, encrypted in transit and at rest. Daily automatic backups. You own your data and can export everything at any time.

Yes. iOS and Android. Check status, receive notifications, and approve requests on the go. Real-time sync with web.

See your operations running on Lotics

The demo runs on your own documents, not on our example.

Book a demo

30 minutes, scheduled by phone or Zalo.