Transport Logistics Software: Which Half Are You Actually Buying?

Transport logistics software covers two different products. A transportation management system (TMS) handles freight procurement: tendering loads to third-party carriers, rating, and freight audit. Own-fleet delivery management software handles execution: route optimisation, dispatch, a driver app, live tracking and electronic proof of delivery for vehicles you control. Most buying mistakes come from confusing the two.

The Four-Month Procurement Mistake: Freight TMS vs Own-Fleet Software

Picture an operator running 14 vans and a pickup workload that has quietly doubled over two years. They spend four months evaluating "transport logistics software". Demos, security questionnaires, a procurement committee, a signature. Week three of go-live, the dispatcher works out that the platform has no driver app worth opening, no way to resequence a route once a van is already moving, and no mechanism for capturing a photo at the door.

The software was not broken. It was the other half of the category. They had bought a freight procurement platform, built for a shipper who hands loads to third-party carriers and needs to compare rates, tender the load and audit the invoice afterwards. Excellent product. Wrong problem entirely.

This happens constantly, and it happens because the phrase "transport logistics software" is doing too much work. It describes both the buying of transport and the doing of transport, and those are separate disciplines with separate software, separate data models and separate users. A freight manager lives in rate tables. A dispatcher lives in a map and a phone.

The distinction matters most for own-fleet operators because that is where the money sits. Last-mile delivery accounts for roughly half of total parcel delivery cost. If you own the vehicles and employ the drivers, execution software touches your margin far more directly than procurement tooling ever will.

What "Transport Logistics Software" Actually Means (And the Three Terms It Gets Confused With)

Transport logistics software is the umbrella term for any system that plans, executes or records the movement of goods. Underneath it sit three narrower categories that vendors, analysts and RFPs use interchangeably, which is where the confusion starts.

Transportation management system (TMS). Gartner defines a TMS as software that plans, executes and settles the physical movement of goods, including carrier selection, rating, tendering and freight audit. Read that list again: it is a procurement function. A TMS is at its strongest when the assets belong to somebody else. If you want the full definition and the freight workflow behind it, our guide to transport management systems owns that ground.

Delivery management software. The execution layer for vehicles you control. Dispatch, driver app, live tracking, recipient notifications, exception handling and electronic proof of delivery. The unit of work is a stop, not a load.

Route optimisation software. The planning engine that sits inside delivery management. It converts a list of addresses, time windows, vehicle capacities and driver shifts into a sequenced run. Sold standalone it is a planner. Sold as part of a platform it is the thing that makes dispatch and tracking accurate.

Large shippers frequently run both, with the TMS handling linehaul and the delivery platform handling the final leg out of the depot. Own-fleet operators usually only need the second, and paying enterprise freight pricing for functionality you will never open is the most avoidable line item in transport IT.

Core Capabilities Own-Fleet Operators Should Expect in 2026

Feature lists all look the same on a website. What separates a platform that survives contact with a Monday morning from one that gets abandoned by March is how these capabilities behave under pressure.

• Route and load optimisation with real constraints. Time windows, vehicle capacity by weight and volume, driver shift length, skill or licence requirements, service duration per stop, and vehicle access limits. An engine that only sequences by distance will happily send a rigid truck down a street it cannot turn out of. See how route optimisation handles constraint stacking rather than plain distance sorting.
• Dispatch and mid-route reassignment. A van breaks down at 9:40am with 22 stops left. The question is not whether the software can build a plan, it is whether it can rebuild one with the remaining fleet, notify the affected recipients and push the change to the drivers' phones before the first complaint arrives.
• An offline-capable driver app. Basements, loading docks, industrial estates and regional dead zones are where evidence gets captured and where connectivity disappears. The app must queue photos, signatures and status updates locally and sync when signal returns, without the driver having to think about it.
• Predictive ETAs and recipient notifications. An ETA calculated once at 6am is a guess. An ETA that recalculates from live position, actual service times and traffic is an operational tool, and it is the single biggest lever on inbound "where is my delivery" calls.
• Exception handling. Failed delivery reasons, redelivery workflows, partial deliveries, refused goods and returns to depot need to be first-class states in the system, not free-text notes that nobody reads.
• Electronic proof of delivery. Covered in depth below, because most platforms treat it as a signature box and that is not enough.
• Reporting on drivers, vehicles and stops. Planned versus actual stop times, distance travelled, on-time performance by route and by driver, and time spent at each stop. Without actual service durations feeding back into the planner, your optimisation slowly drifts away from reality.
• An integration surface that matches your stack. Native connections into ecommerce and order sources such as Shopify, WooCommerce and ShipStation, accounting through Xero, field service through ServiceM8, plus Zapier and an open API for the WMS or ERP that will never have a prebuilt connector. Locate2u carries this breadth natively, which matters because the alternative is a middleware bill and a fragile CSV import that breaks the first time someone renames a column.

One structural point worth being blunt about. Dispatch, route optimisation, customer communications, the driver app and proof of delivery are five capabilities that most tooling covers two or three of. Buying them separately means five logins, three sources of truth about where a vehicle is, and a reconciliation job nobody wants. Locate2u runs all five on one platform, and scales from a single-vehicle operator through to enterprise fleets without a re-platform partway up. Micro-fleets of one to five drivers are ordinary customers here, not an awkward edge case squeezed into an enterprise pricing model.

Handling Mixed Operations: Deliveries, Pickups and Service Routes on One Run

Here is the gap almost nobody in this category writes about honestly. Routing engines are usually built around a one-directional assumption: goods leave the depot, goods arrive at customers, the van comes back empty. Real transport operations do not look like that.

A real run interleaves drop-offs, scheduled collections and on-site service visits, and each of those has different constraints. A collection consumes capacity rather than freeing it, so sequencing matters: schedule the pickups too early and the vehicle is full before the last delivery. A service visit has a duration measured in tens of minutes rather than a two-minute door drop, and it often has a hard appointment window that the customer has already been told about. A return leg has to route back through a depot or a processing point at the right moment.

When an engine models these as separate job types that cannot share a route, the dispatcher ends up planning the mixed work by hand in a spreadsheet, which is exactly the task the software was bought to eliminate.

Containers for Change runs scheduled collection routes where the pickup is the job, not an afterthought bolted onto a delivery plan. PTSQ runs scheduled maintenance and service visits, where the constraint set is closer to field service than to parcel delivery: the right technician, the right window, a realistic on-site duration. Both operate on the same platform, which is the point. Parcel work and heavy or service-oriented work are usually a fork in the road for software vendors. Locate2u handles both.

When you evaluate, put this on the demo agenda explicitly: build a single route containing four deliveries, two timed collections and one 45-minute service visit, with a capacity limit that the collections will push against. If the engine cannot sequence that in one trip, it will not survive your actual week.

What Your Records Need to Prove: ePOD, GPS Breadcrumbs and Audit Trails

A signature scrawled on a phone screen proves almost nothing. Anyone can draw a squiggle. Once a customer disputes a delivery, a supplier lodges an insurance claim, or an auditor asks for chain of custody, the question stops being "did the driver mark it delivered" and becomes "what can you produce".

An electronic proof of delivery only functions as evidence when four attributes travel together:

1. A photo of the goods in place, showing the location as well as the item.
2. A signature or barcode scan tying the handover to a named person or a specific item identifier.
3. A GPS geo-stamp recording where the capture happened, not where the order said it should happen.
4. A server-side timestamp, because a device clock can be changed and a device clock will be challenged.

Any one of those alone is contestable. Together, backed by GPS breadcrumbs showing the vehicle's actual path and dwell time at the stop, they form a record that closes a chargeback in one email. The World Bank Logistics Performance Index scores tracking and traceability as a standalone competency alongside customs and infrastructure, which tells you how the wider industry rates visibility: not a nice extra, a core capability.

Configurability matters as much as capture. Different goods need different evidence. A refrigerated drop may need a temperature reading. A restricted item may need an ID check and a recipient name. A construction site may need a photo of the unload zone. SuperPharmacy operates in pharmaceutical delivery, where chain of custody is a compliance obligation rather than a customer-service preference, and the evidence fields have to reflect that. Locate2u treats proof of delivery as a first-class part of the platform with configurable capture fields, not a checkbox at the end of a route.

Pressure Tests: Cold Chain, Heavy Goods and Long-Distance Regional Runs

Generic routing works fine until physics gets involved. Two constraint types break more implementations than anything else.

Cold chain and dwell time. Chilled and frozen goods put a hard ceiling on how long a stop can take and how long the load can sit in a warm van with the door open. That converts service duration from an estimate into a safety limit, and it changes sequencing: temperature-sensitive stops need to cluster early, and a route that looks efficient on distance can be unusable on dwell time. Madam Seafood operates in exactly this envelope, where the plan has to respect product integrity before it respects kilometres.

Heavy goods and site access. Building materials do not arrive at a front door. They arrive at a site with a crane window, a gate that opens at a set hour, a surface the truck can or cannot drive onto, and an unload that takes far longer than a parcel drop. Vehicle-specific routing, generous and accurate service times, and photographic evidence of where the goods were placed all become mandatory. Franz Building Supplies runs this kind of work, and it is the clearest example of why parcel-only routing logic falls over.

Long-distance regional runs. Big legs between stops change the maths. A single mis-sequenced stop costs an hour instead of six minutes, connectivity drops out for long stretches so the driver app has to work offline, and multi-day or multi-depot planning becomes relevant. Any platform that assumes a dense metropolitan drop pattern will underperform badly outside the city.

A 7-Point Checklist for Choosing Your Transport Logistics Platform

Take this into the demo and refuse to be shown a canned dataset. Use your own stops.

The honest callout. If your core problem is tendering loads to third-party carriers, comparing carrier rates across lanes, planning multi-modal movements and auditing freight invoices, you probably need a freight TMS instead, and none of the seven points above are the right test. Buy the procurement product. Own-fleet execution software will frustrate you for the same reason a freight platform frustrates a dispatcher: it is answering a question you are not asking. If you run your own vehicles and your pain is sequencing, dispatch, visibility and evidence, you are in the right half of the category. Once you have chosen, our logistics management guide covers the rollout side: data preparation, driver adoption and the first 90 days.

FAQs

What is transport logistics software?

Transport logistics software is the umbrella term for systems that plan, execute and record the movement of goods. It splits into freight-side tools that tender loads to third-party carriers and audit freight invoices, and own-fleet tools that optimise routes, dispatch drivers, track vehicles live and capture electronic proof of delivery.

What is the difference between a TMS and delivery management software?

A TMS manages freight you hand to other carriers: rate comparison, tendering, multi-modal planning and freight audit. Delivery management software manages vehicles you own: route optimisation, dispatch, a driver app, live tracking, recipient notifications and proof of delivery. Large shippers often run both; own-fleet operators usually only need the second.

Do small fleets need transport logistics software?

Yes, once manual planning costs more than the software. Practical triggers are five or more vehicles, routes over 30 stops per driver, or recurring disputes about whether a delivery happened. Look for per-driver or per-vehicle pricing, an offline-capable driver app, and setup measured in days rather than a multi-month project.

Can transport logistics software handle pickups and service jobs, not just deliveries?

Good systems can. Many routing engines assume one-directional delivery, so mixed runs break their sequencing. Confirm during evaluation that the engine treats pickups and timed service visits as first-class stop types with their own duration, capacity and time-window constraints, and can put them on the same route as deliveries.

What should an electronic proof of delivery capture?

Four things together: a photo of the goods in place, a signature or barcode scan, a GPS geo-stamp and a server-side timestamp. Combined with GPS breadcrumbs from the route, that record survives a chargeback, an insurance claim or a compliance audit. Any single element on its own is easy to dispute.

How much does transport logistics software cost?

Pricing is normally per driver, per vehicle or per stop, billed monthly, with freight-procurement systems priced far higher than own-fleet execution tools because they carry carrier-network and settlement functionality. Model your cost against your busiest month, not your average, and check whether driver seats, API access and ePOD storage are included.

If you own the vehicles, the decision is narrower than the category makes it look: you need routing that respects real constraints, dispatch that survives a breakdown, a driver app that works without signal, and evidence that closes disputes. Locate2u runs all of that on one platform across Australia, New Zealand, the United States, the United Kingdom and Canada, for fleets of one van and fleets of hundreds. Book a demo and bring your worst route; that is the one worth testing.