How to Choose Freight Software for Your Transport Business

A dispatcher rebuilding runs on a whiteboard, rate cards held in one person’s spreadsheet and dockets waiting to be typed into the accounts can work for a while. As volume grows, the gaps show up in billing, in proof of delivery and in the time the office spends re-entering what the road has already recorded.

This guide explains what to check before you choose freight software or replace the platform you use. It is written for road-freight operators: carriers, couriers and distribution businesses. It covers what the category includes, where a specialist system adds value, how to test dispatch and billing, the difference between captured events and live visibility, the full cost and how to check an implementation.

What does freight software do?

Freight software supports the work between a customer booking a job and the invoice that closes it. Products package these functions differently, so treat each item below as a requirement to confirm rather than something every platform includes:

• Booking. Consignment entry by the office or by customers, with the details needed to rate and deliver the job.
• Dispatch. Assigning consignments to vehicles and runs, including transfers between runs or depots.
• Delivery records. Pickups, deliveries, exceptions and proof of delivery recorded against the consignment.
• Rating and billing. Calculating charges from customer rates and approved extras, then preparing invoices.
• Customer access. A portal where customers can book and check their own consignments.
• Reporting and connections. Operational reports and data exchange with accounting or other systems.

The category label also covers different jobs. Shipper booking tools help a business send freight through carriers. Carrier transport management platforms help an operator run its own fleet. International forwarding systems handle bookings, documents and customs work. Do not assume every product includes customs, warehouse management or route optimisation; confirm the modules that match your operation.

The terms freight software and transport management system overlap, and product labels do not define an identical scope. Compare the workflow a product supports rather than the name on the box.

What requirements should you write down first?

A short requirements list gives every supplier the same brief and keeps the comparison on your work rather than on their feature list. Describe how the operation runs today and what has to change.

• Freight and units. What you carry and how it is measured, whether by pallet, weight, cube, tonne or load, including any weighbridge or docket figures you rely on.
• Rates. How customers are charged, including contracts, minimums, surcharges and the extras you are entitled to bill.
• Network. Depots, regular runs, cross-docking, subcontractors and any linehaul between regions.
• Customers. What customers need to book, see and download, and which of them expect their own reporting.
• Systems. The accounting package, existing booking or dispatch tools and any customer systems that exchange data with yours.
• People and devices. Who dispatches, who invoices, what drivers carry in the cab and where coverage is poor.

Mark each requirement as essential or desirable. Unusual needs, such as bulk materials sold by the tonne with customers tracking their own orders, are worth stating plainly at this stage, because they decide which products are worth a demonstration.

How should you check dispatch and allocation?

Dispatch is where a demonstration shows whether the product fits your day. Ask the supplier to book a job, assign it, change the vehicle and transfer it between runs or depots while keeping its history intact.

Allocation methods vary. Manual assignment leaves the dispatcher in control of every decision. Rules-based assignment applies agreed criteria such as area, vehicle type or customer. Optimised assignment uses software to suggest runs against constraints such as capacity and time windows. A product may offer one or more of these, so confirm which methods it supports and how a dispatcher overrides a suggestion when a truck goes down mid-morning.

Subcontracted legs, depot transfers and part loads deserve their own test, because these are the movements that break a setup designed only for a single vehicle doing a single run.

What should transport billing software handle?

Billing is where a platform earns or loses its keep. Charges depend on captured events, agreed customer terms and configuration, so test the billing against your real rate cards rather than a demonstration example. Check:

• Customer and rate data. Customer IDs, units, weight or cube, rates, minimums and surcharges.
• Extra charges. Waiting time, extra stops and redeliveries are billable only where the customer terms allow them and the event was captured.
• Tax and corrections. GST treatment, credits, corrections and duplicate prevention.
• Reconciliation. How invoice totals are checked against the accounting record after transfer.

An integration does not by itself keep the books accurate. Agree who owns each record, how a failed or duplicate transfer is handled and how the two systems are reconciled.

Sending invoices is a separate question. Exporting an invoice to your own ledger is different from sending a Peppol eInvoice to a customer. Inland Revenue describes eInvoicing as exchanging invoice information between buyer and supplier financial systems through the Peppol network, so emailing a PDF is not eInvoicing. Confirm the supported software or access-point route rather than assuming a freight platform includes it. Our guide to eInvoicing explains the detail.

What should a customer portal show?

A customer portal can reduce phone calls about where a consignment is, but only if customers see accurate, timely information about their own freight and nothing else. Test it with a customer account during the demonstration.

Check that each customer sees only its own consignments, that bookings arrive with the details needed to rate the job, and that proof of delivery can be retrieved once it has synchronised. Ask how the portal shows the time of the latest update, so a customer can tell a delivered consignment from one whose driver has not yet reconnected. Agree who sets up customer users, who removes them when staff leave the customer business and what exports customers can take.

What should you test in a freight software demo?

Use examples from your own operation. Ask the supplier to show a normal consignment and the exceptions that create extra work, and record what is standard, configured, integrated or outside the proposed scope.

Bring real rate cards, a sample of last month’s dockets and the exceptions your team handles every week. A demonstration built on your data shows far more than a polished standard run.

What should the full cost of freight software include?

Compare the same scope over the same period. Separate one-off costs from recurring charges, and state whether GST is included.

• Platform. Licences, modules, users or volume limits, portal and storage charges.
• Project. Configuration, migration, integrations, devices and training.
• Running. Support, future changes and the contract term.
• Exit. Data export, access to history and any exit costs.

Estimate benefits from work that will change. If 80 jobs a day each lose one 90-second re-entry step, that is two hours of capacity a day under those assumptions. Released time is useful, but it is not automatically a cash saving, and a pilot shows what is removed and what checking remains.

Missed charges can be estimated the same way. As a hypothetical, five missed charges a day over 250 working days add up to 1,250 charges a year, but only charges that are valid under the customer terms, captured and collected count. Compare measurable benefits with the implementation and ongoing costs rather than assuming a payback period.

How should a freight software implementation be checked?

Agree the required workflows and acceptance checks first. Then configure, connect and migrate, pilot with the people who will use the system and check the results before cutting over.

Clean and trial the customer, rate and open-job data before it moves, then reconcile sample charges and totals. A rate card that was wrong in a spreadsheet is still wrong in a new platform, and fixing it during configuration is far easier than after go-live.

Training depends on the role. Dispatchers learn a new board and a new way of building runs, drivers learn the capture steps on their device, and the accounts team checks invoices and transfers. Agree role-based training and a representative pilot rather than a fixed number of hours. Driver devices matter too, and mobile device management keeps them set up and recoverable.

Confirm the cutover window, the fallback process, support contacts and the point at which the old system can be retired, and keep access to the history you need. A staged rollout reduces risk but cannot promise an uninterrupted operation.

Where do Zinform Logistics and Transsend fit?

Exodesk builds and supports Zinform Logistics for freight management and Transsend for mobile capture. The Zinform Logistics page explains the product, its modules and how a demonstration is set up around your operation. The Transsend page covers mobile forms, signatures, photographs and offline capture.

Existing platforms can sometimes be kept and connected rather than replaced, depending on the products, the available interfaces and the data that needs to move. Each connection is scoped before it is promised. Where a confirmed requirement is not met by configuration, custom software development can extend a platform. The devices, accounts, depot networks and hosting around the software are covered by transport and logistics IT support.

Freight software support from Exodesk

Software selection, configuration, integration and ongoing support are agreed for the proposed setup, along with support hours and escalation arrangements. If you are comparing platforms, the checklist above works whether or not Zinform Logistics is on your shortlist.

Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide.

Contact us or call 0800 396 337 to talk through your dispatch and billing requirements.