Logistics Software Development in Australia: Dispatch, Visibility and Proof of Delivery
Planning logistics software in Australia: dispatch, driver apps, proof of delivery, shipment visibility, HVNL and NHVR records and carrier integrations.
What should logistics software do?
Logistics software should turn orders and consignments into planned runs, get clear instructions to drivers, capture pickup and delivery with proof of delivery, publish honest status to customers, and feed accurate data to billing and reporting. In Australia it may also need to support Heavy Vehicle National Law record-keeping where it applies and integrate with carriers such as Australia Post and StarTrack. Most operators buy core systems and build integrations and customer-facing layers.
This guide is for transport operators, distributors, 3PLs and businesses running their own delivery fleets. It covers dispatch planning, driver apps, proof of delivery, shipment visibility, route data, integration architecture, regulatory record-keeping and reporting.
For AI uses in logistics, see AI agents in logistics and supply chain. We do not quote fuel or time savings: they depend on your operation. Nothing here is legal or transport-compliance advice.
Key takeaways
- Clean addresses, time windows and consignment data matter more than any optimisation algorithm.
- The driver app must work offline and capture proof of delivery every time.
- Publish status as events so customers, portals and finance see the same truth.
- Know where the HVNL applies (not WA or the NT) and use NHVR-approved EWDs for fatigue records.
- Chain of responsibility means scheduling and loading data can matter for safety, not just efficiency.
- Buy core TMS, routing and telematics; build integrations and customer-facing layers where you differ.
Dispatch planning
Dispatch turns a day's consignments into runs. Good planning considers vehicle capacity (weight, volume, pallets), vehicle type and access, driver hours and licences, customer time windows, pickup and delivery order, and depot locations.
Route optimisation tools can help once data is reliable, but they cannot fix wrong addresses, missing time windows or unrealistic service times. Keep dispatchers able to override plans, record why, and feed actual service times back into planning so estimates improve.
Driver apps and proof of delivery
- Run sheet with stops, instructions, contacts and access notes, available offline.
- Scan consignments at pickup and delivery to confirm the right goods.
- Proof of delivery: time, GPS, recipient name, signature, photos and exception notes.
- Exception flows for failed deliveries, damage, refusals and partial deliveries.
- Navigation hand-off to the driver's preferred maps app.
- Minimal interaction while driving; designed to be used when stopped.
- Reliable background sync when coverage returns, especially in regional areas.
Worth noting
Driver safety comes first: design the app so drivers do not need to interact with it while driving, and follow road rules on mobile phone use in each state and territory.
Australian regulatory records: HVNL, EWDs and chain of responsibility
Where the HVNL applies. The Heavy Vehicle National Law regulates heavy vehicles over 4.5 tonnes gross vehicle mass and is in force in Queensland, New South Wales, the ACT, Victoria, Tasmania and South Australia; Western Australia and the Northern Territory are not participating jurisdictions (National Transport Commission). Operators crossing borders must follow the rules where they operate. Software that schedules heavy vehicle work should know which jurisdiction each trip is in.
Electronic work diaries. The National Heavy Vehicle Regulator approves electronic work diaries for recording work and rest under fatigue rules, and drivers, operators and record keepers have the same obligations using an EWD as with a written diary (NHVR). Most businesses integrate with an approved EWD provider rather than building one. Check the NHVR's current list of approved EWDs.
Chain of responsibility. Under the HVNL, responsibility for heavy vehicle safety extends beyond drivers to parties ranging, in the NHVR's words, "from the business that employs a driver or owns a vehicle, to the business that sends or receives goods", and each party has a primary duty to ensure, so far as is reasonably practicable, the safety of its transport activities (NHVR). Scheduling that ignores driver fatigue limits or loading data that is inaccurate is a safety issue, not just an efficiency one. Software can help by flagging schedules that conflict with rest requirements and keeping accurate load records, but it does not discharge anyone's duties. Get advice from a transport compliance specialist.
Shipment visibility for customers
Build visibility on events, not on screens. Each meaningful change (booked, picked up, in transit, out for delivery, delivered, exception) becomes an event that updates tracking pages, notifications, customer portals and APIs at the same time.
Give business customers a portal or API with consignment status, proof of delivery and invoices, and consumers a tracking page with an honest delivery window. Keep notifications factual; marketing needs consent under the Spam Act. See customer portal development and delivery tracking for patterns.
Integration architecture
Logistics software rarely stands alone. A typical architecture connects order sources (ecommerce, ERP, B2B portals, EDI), a transport management or dispatch system, telematics and EWD providers, driver apps, carriers for outsourced legs, the warehouse system, and accounting for billing.
Orders: ecommerce / ERP / portal / EDI
-> consignment created
Dispatch/TMS -> run planned -> driver app
Driver app -> picked up / delivered / exception
-> event bus
Event bus -> tracking page, notifications,
customer portal / API,
billing (accounting), reporting
Carriers <-> labels and tracking (API)
Telematics/EWD -> location and fatigue dataCarrier integrations in Australia
If you use carriers for some legs, integrate for labels, manifests and tracking. Australia Post's developer centre provides shipping and tracking APIs, which are available to businesses with eParcel or StarTrack contracts (Australia Post). Other carriers and aggregators offer their own APIs. Normalise carrier statuses into your own event model so customers see consistent tracking regardless of who carries the goods.
Operational reporting
Report on what drives cost and service: on-time delivery against promised windows, failed and repeat deliveries by reason, stops per run, kilometres per drop, vehicle utilisation, proof-of-delivery completeness and time from delivery to invoice. Define each measure precisely and capture data at source. See business intelligence dashboards.
Build or buy
| Component | Usually best | Build when |
|---|---|---|
| Transport management and dispatch | Buy a TMS or routing product | Planning rules are unusual and central to your service |
| Telematics and EWD | Buy; EWDs must be NHVR-approved | Rarely; integrate instead |
| Driver app | Use the TMS app | You need workflows the TMS app cannot support |
| Customer portal and API | Use the TMS portal if adequate | Customers need a combined view across systems |
| Integrations and event layer | Integration platform or custom service | Most operators need some custom work here |
Hypothetical example: a regional distributor's own fleet
This example is hypothetical. A building supplies distributor in regional Victoria runs twelve trucks, some above 4.5 tonnes, delivering to building sites with narrow time windows. Drivers carry paper run sheets; customers phone to ask where deliveries are.
The distributor adopts a routing and dispatch product with a driver app, integrates an NHVR-approved EWD for drivers who need one, and builds a small event service that pushes delivery status and photo proof of delivery into its customer portal and sends factual SMS updates. Schedules that would breach driver rest requirements are flagged to dispatchers. The business measures failed deliveries and customer calls about delivery status before and after.
Common mistakes
- Buying route optimisation before cleaning address and time-window data.
- Driver apps that require interaction while driving or fail offline.
- Proof of delivery that is optional, then disputes that cannot be resolved.
- Building a custom EWD instead of integrating an approved one.
- Tracking pages built on screens rather than events, so they disagree.
- Quoting savings to the board before measuring a baseline.
Related guides
For stock and warehouses, see inventory management software. For technicians rather than drivers, see field service management software. For integration patterns, see API integration for Australian businesses, and for offline apps, offline-first mobile app development.
Fleet management and telematics
Fleet software tracks vehicles, drivers and jobs: GPS location, trip history, maintenance schedules, fuel, and driver hours. Most Australian operators buy telematics hardware and a platform rather than build them, then integrate that data with dispatch, customer portals and accounting.
- Check heavy vehicle obligations under the Heavy Vehicle National Law with the NHVR, and Western Australian and Northern Territory rules where they differ; this is not legal advice.
- Tell drivers what is tracked and why. Workplace surveillance laws apply in some states, such as New South Wales, and privacy obligations may apply to driver data.
- Prefer providers with documented APIs, webhooks and data export.
- Plan for coverage gaps in regional areas: buffer data on devices and sync later.
- Keep location history only as long as you need it.
| Need | Typical approach |
|---|---|
| Vehicle location and trips | Telematics provider platform and API |
| Driver fatigue and work diaries | Electronic work diary approved by the NHVR where required, or compliant written records |
| Maintenance | Odometer or engine-hour based schedules from telematics data |
| Customer ETAs | Location data feeding a tracking page or portal |
| Job and dispatch | Custom or packaged dispatch software integrated with telematics |
Sources
Transport regulation: National Transport Commission, Heavy Vehicle National Law; NHVR, electronic work diary; NHVR, chain of responsibility.
Carriers: Australia Post developer centre.
Regulatory points were confirmed via search summaries where fetches were blocked; check current NHVR and state guidance. The architecture, tables and example are ours. Nothing here is legal or compliance advice or ZSpace client data.
Conclusion
Logistics software pays off when data is clean, drivers have a dependable app, every delivery has proof, and customers and finance see the same events. Respect Australian regulatory records where they apply, integrate approved EWDs rather than building them, and invest custom effort in the integrations and customer-facing layers that make your service different. For planning efficient runs, see route optimisation software. For waste receipt reporting in the UK, see digital waste tracking software in the UK.
Planning logistics software?
ZSpace Labs is an India-based, remote-first technology studio working with Australian and international businesses on logistics integrations and customer portals and driver apps. If it would help to map what to buy and what to build, we are happy to talk it through.
Common questions.
Only for the parts that set it apart. Transport management systems, route planning tools, telematics and carrier platforms cover standard dispatch, tracking and proof of delivery well. Custom software makes sense for distinctive operations, a customer portal that combines several systems, or integrations between telematics, warehouse, accounting and customer systems that products do not provide.