Shipments and legs
Pick-up, delivery, multiple stops, a fixed time or a time window, legs subcontracted out.
CargoDesk TMS · Transport management system
CargoDesk TMS brings the shipment, the dispatch plan, the partner, the document, the warehouse, driver pay and invoice preparation into one system. Every piece of data is entered once — after that everyone sees the same thing, in real time.
Screenshots from the running system, with sample data. Page through from the dashboard to the AI assistant — click any image to see it full size.
01 / 08: Dashboard
Pick-up, delivery, multiple stops, a fixed time or a time window, legs subcontracted out.
A schedule by driver or by vehicle, with conflict detection — who is where today and what is left uncovered.
Billing cycles for collected-invoice partners, items waiting to be invoiced, an annex in one click.
Warehouses, inbound and outbound, pallet stock, storage fees among the billable items.
Master data, expiring documents, servicing, archiving — without losing the references on past shipments.
CMR, waybills and contracts by category, with permission-bound downloads and search.
Work log, per-diem, mileage, drop money, supplements — gross settlement exported to Excel for payroll.
Revenue, breakdown by partner and vehicle, month-on-month — from the same source as the dashboard.
At most haulage companies the same shipment is written down at least four times: once in the quote, once in the dispatch plan, once for the driver, once for invoicing. Every rewrite is a chance to get it wrong, and a phone call.
It will not tell you that a completed shipment has not been invoiced, that a driver's licence expires in two weeks, or that a collected-invoice partner's cycle has closed.
When the dispatcher is on holiday, nobody knows what was promised to the partner. In the system that is recorded data, not a verbal agreement.
Invoicing means collecting completed shipments, storage, prices and annexes. In the system that is a list already waiting, not two days of gathering.
A shipment invoiced twice, a lost CMR or a driver who was never notified costs far more than the monthly fee you are trying to avoid.
The estimate below comes from our own rollouts: it measures the manual work that disappears once data is created once and everyone works from it. Set your own volumes — the assumptions are shown openly, and we refine them during discovery.
Manual work that disappears
41.5hours per month
| Task | Assumption | Hours / mo |
|---|---|---|
| Entering and tracking a shipmentTemplates, saved addresses, recurring shipments, no double entry | 6 min / shipment | 15.0 |
| Collecting billing data and the annexA completed shipment lands among the items waiting to be invoiced | 4 min / shipment | 10.0 |
| Dispatch planning and driver briefingDispatch board, conflict detection, drivers see their own shipments | 3 min / shipment | 7.5 |
| Finding and sending documentsCMR and waybill attached to the shipment, emailed from a template | 2 min / shipment | 5.0 |
| Preparing driver payWork log and rates in one place, pre-filled, exported to Excel for payroll | 25 min / driver | 2.5 |
| Compiling monthly reportsRevenue and the breakdown by partner and vehicle are already there | 90 min / month | 1.5 |
| Total | 41.5 |
The estimate covers administration, not driving. It does not include the value of the mistakes avoided — double invoicing, missed items, lost documents — because that cannot be generalised honestly.
Every module works from the same data. Change a shipment's price and the report, the billable item and the assistant's answer all change with it — there is no second version of the truth.
A shipment's data is the same in the dispatch plan, on the document, in the report and among the billable items. Nothing is copied, so nothing drifts.
Completed but uninvoiced shipments, legs without a driver, expiring documents, a due collected invoice — the watchlist is on every page.
Company name, tax number, logo, brand colour and numbering format are all settings. Your staff are not using someone else's software.
The same interface in a browser and as an installed Windows application, on the same data. On the desktop, saving is native and the credentials live in the Windows credential store.
Four roles, and pay data carries its own separate right. Price visibility is a right of its own too — a dispatcher can work without seeing your margin.
The audit log shows who changed what and when. In a dispute that is no longer a matter of memory.
We can run it on our server or on yours. Backups are encrypted and restoring them is a documented procedure.
We keep developing the system, and if a feature is missing for the way you work, we can build it — with the same team.
01
Pick the partner, use saved addresses, add stops, set a fixed time or a window. For recurring work, start from a template in a few clicks.
02
Assign the driver and vehicle on the shipment; the dispatch board shows it instantly. On a conflict the system asks, but the dispatcher decides.
03
The driver sees their own shipment on their own screen. The CMR and waybill are attached to the shipment, searchable and emailable from there.
04
A completed shipment moves into the items waiting to be invoiced on its own. For collected-invoice partners, the annex is one click at the end of the cycle.
A Docker-based deployment with automatic TLS certificates. The data stays inside the EU; you choose where.
Daily encrypted backups with a documented restore procedure — a backup is only worth something once you have tried it.
The application runs with a restricted database user, sessions can be revoked, and logins and bulk exports are logged.
Version upgrades are scheduled and reversible. The Windows client updates itself.
The system works from day one; onboarding is about company data, branding, permissions, numbering formats and master data (partners, vehicles, drivers). That is usually measured in days, not months.
Partner, vehicle and driver master data can be imported from Excel. Shipments in progress are usually not worth migrating: close those the old way and start new ones in the system.
No. CargoDesk prepares invoicing — it collects the billable items and produces the invoice annex — while your invoicing software issues the invoice. Driver pay works the same way: gross settlement here, payroll calculation stays with your accountant.
We talk it through, and if it fits the logic of the system, we build it. The same developer who delivers custom projects develops the product — there is no offshore support queue between the request and the fix.
Wherever you want it: on our server inside the EU, or on your own. Either way with encrypted backups and a documented restore.
The system is web-based, so it opens in a browser, and the driver interface is designed for phones. For dispatch work we recommend a larger screen — the schedule and the shipment list carry many columns.
It depends on the size of the company, the number of users and where it is hosted, so we do not publish a template price. After a short conversation you get a concrete written proposal.
The next step
In a 45-minute online demo we walk through your own process: where the same data is created twice, and how much of it the system would take over. No preparation needed, and no obligation.
A reply within 1 business day, in Hungarian or English.