Treadstone Associates
Article · 11 min read

Last-mile delivery software: what it adds

A route planner sorts addresses. Delivery software produces the evidence and the exceptions — which is where the money actually leaks.

Treadstone Associates · Updated 2026

Key takeaways

  • • A route planner outputs a stop sequence; delivery software outputs proof of delivery, recipient notifications, exception codes and an audit trail.
  • • Ontario requires a CVOR only for trucks over 4,500 kg, and the federal hours-of-service rules apply above the same weight — most last-mile vans sit below both.
  • • An AI voice notification is an ADAD under the CRTC’s rules, which set calling hours, identification and disconnect conditions.
  • • Delivery photos are personal information under PIPEDA, so retention has to be a setting you chose, not a default you inherited.

The short answer

A route planner produces a sequence of stops. Last-mile delivery software produces evidence and exceptions — a time-stamped record of what was delivered, to whom and when, plus the dispatch, customer notification and failed-delivery handling that a sorted list of addresses cannot give you.

The distinction matters commercially because the disputes that cost a courier money are almost never routing disputes. They are “it never arrived”, “it arrived broken”, “nobody told me it was coming” and “you charged me for a second attempt I did not authorise”. A route planner has nothing to say about any of them.

Four things a route planner does not do

If you are comparing tools, these are the four capability gaps that separate the categories. Everything else is packaging.

  • Proof of delivery. A signature, a photo, a scan, a geotag, a timestamp — captured on the device, attached to the stop, and retrievable months later by consignee name or waybill number.
  • Recipient notification. Automated messages on dispatch, on approach, on delivery and on failure. This is the part with Canadian regulatory constraints attached, covered below.
  • Exception handling. A structured outcome for every stop that is not a clean delivery — not home, refused, wrong address, access denied, damaged on arrival — with the reason code that drives the rebill or the re-attempt.
  • The audit trail. Who changed the route, who reassigned the stop, when the driver marked it complete and where the device was at the time.

Where the Canadian compliance line actually sits for a last-mile fleet

Most last-mile operators run vehicles that sit below the thresholds that trigger heavy-truck regulation, and this shapes what software you need. Ontario requires a Commercial Vehicle Operator’s Registration for trucks with a registered gross weight or actual weight over 4,500 kg, and states that you do not need one for trucks (other than a tow truck) with registered gross weight or gross weight of 4,500 kg or less, whether towing a trailer or not.

The federal hours-of-service rules draw the line in the same place. The Commercial Vehicle Drivers Hours of Service Regulations define a “commercial vehicle” as a truck, tractor, trailer or combination of them with a registered gross vehicle weight in excess of 4,500 kg, or a bus designed to seat more than 10 people including the driver. A cargo van under that weight is outside those regulations, and therefore outside the electronic logging device requirement that attaches to them.

Fuel tax is a third line again, and higher. Ontario’s IFTA guidance says light trucks and vans at or below 11,797 kg — expressly including delivery vans and courier services — are not required to register under IFTA, even when carrying goods commercially in and out of the province.

What this means when you shop

A vendor that leads with ELD integration and IFTA reporting is selling you a carrier product. If your fleet is sub-4,500 kg vans, you are paying for compliance modules that do not apply to you and getting a weaker proof-of-delivery and notification stack in return. Buy for the obligations you actually have.

Customer notifications: the rule most last-mile operators have never read

Automated delivery notifications are the single most valuable feature in this category and the one with the most Canadian regulatory exposure, because the CRTC’s Unsolicited Telecommunications Rules define an Automatic Dialing-Announcing Device (ADAD) as equipment that conveys a pre-recorded or synthesized voice message. A synthesised voice is exactly what an AI calling agent produces. If you are considering one to call recipients, you are considering an ADAD.

The rules split by purpose. Where the call is a solicitation, the CRTC requires express consent to receive a telemarketing telecommunication via an ADAD from that specific person, naming the number to be called. Where there is no attempt to solicit — a pure “your parcel arrives between 2 and 4” — the CRTC sets conditions rather than requiring consent, and they are specific:

SMS and email notifications sit under separate anti-spam rules, but the practical design point is the same: a notification engine that cannot record consent, honour a stop request and prove what was sent to whom is a liability wrapped in a convenience.

The privacy layer nobody quotes in a demo

Photo proof of delivery captures a doorstep, a hallway, sometimes a person. Under PIPEDA, “personal information” means information about an identifiable individual and the statutory definition of “record” expressly includes a photograph. So delivery photos are personal information held in the course of commercial activity, and the retention principle applies: personal information shall be retained only as long as necessary for the fulfilment of the purposes for which it was collected, with the same schedule setting out that organisations should develop guidelines covering minimum and maximum retention periods and should destroy, erase or anonymise information no longer required.

That is not an argument against photo POD — it is the best evidence a courier has. It is an argument for a retention setting in the software, and for knowing what that setting is before you sign.

If your operation crosses a provincial boundary it is a federal undertaking, and PIPEDA then also reaches your employee information: the Act applies to personal information about an employee that an organisation collects, uses or discloses in connection with the operation of a federal work, undertaking or business. The Privacy Commissioner’s workplace guidance is explicit that PIPEDA applies to employee information in federal works, undertakings and businesses, naming transportation companies, and that employers must limit collection to what is necessary for identified purposes. Driver location history is employee information.

A worked example

A 14-van courier in the Greater Toronto Area runs 90 to 130 stops per van per day, all vehicles under 4,500 kg. It has no CVOR obligation, no ELD obligation and no IFTA registration. Its costs are re-attempts, “where is my parcel” calls, and monthly credits to two retail clients for stops the clients say were never made.

A route planner fixes none of those. What fixes them is: a scan-on-load event so a missing parcel is caught at the depot rather than at the door; a photo and geotag on every completion; a structured reason code on every failure, which turns the re-attempt argument into a data question; and an automated notification on approach, which is the single biggest lever on the not-home rate. The routing itself is the least valuable part of the purchase.

Selling or buying a book of business like this? The evidence trail is also the asset. Treadstone’s sister law firm covers the diligence angle in its note on buying and selling a courier or last-mile delivery business.

Where AI genuinely helps, and where it does not

AI is useful in last mile for three unglamorous jobs: reading addresses and unstructured delivery instructions into structured fields, predicting a stop’s service time from your own history so the plan reflects reality, and triaging the exception queue so a human sees the twelve stops that need a decision instead of all ninety.

It does not decide whether a delivery counts as complete, whether a client is credited, or whether a driver is disciplined. Those are commercial and employment decisions. The software assembles the evidence; a person reads it and signs.

Common questions

Do I need an ELD for a cargo van?

Not under the federal hours-of-service regulations, if the van’s registered gross vehicle weight is 4,500 kg or less — those regulations apply to commercial vehicles above that weight. Provincial requirements for other purposes are separate; check the province where the vehicle is plated.

Is a photo enough to prove delivery?

It is strong evidence, not conclusive proof, and what governs the liability question is the conditions of carriage. For interprovincial trucking, the federal Conditions of Carriage Regulations apply the conditions and limitations of liability of the province in which the transport originates. Read that province’s rules before you design your evidence set.

Can I use an AI voice agent to call recipients?

It is an ADAD under the CRTC’s definition, which covers a synthesized voice message. Purely informational delivery calls are permitted subject to the calling-hours, identification and disconnect conditions above; anything that promotes a service needs express consent first.

How long should I keep delivery photos?

Long enough to answer a claim under your conditions of carriage, and no longer — PIPEDA requires that personal information be retained only as long as necessary for the purposes it was collected for. Set the period deliberately, write it down, and make sure the software enforces it.

Stop losing hours to paperwork you already have the data for.

A 30-minute call is enough to tell you whether AI pays for itself in your back office.