Skip to content

Cannabis delivery software: orders, drivers and customer tracking

Delivery adds a moving part to the retail day: the order leaves the counter, but the customer still needs a clear answer. Plan the handoffs between store, dispatcher and driver so everyone knows what happens next.

PURP makes cannabis retail software. Delivery is a PURP+ add-on; confirm your country, business model and local delivery requirements before launch.

Build one clear handoff from prepared order to assigned driver, customer update and recorded outcome. Practise the exceptions before the first busy delivery shift.

Define where and how you deliver

Start with the operation you are permitted to run: eligible products and customers, service area, delivery windows, order cutoff, charges and approved payment arrangements. Requirements depend on the country, jurisdiction and business model. A retail delivery operation and a prescription delivery service need different reviews; choosing software does not establish permission for either.

PURP delivery is a PURP+ add-on. Confirm the relevant locations and workflow during setup, including how orders enter the operation and which staff prepare, assign and complete them. Separate the customer’s requested window from the team’s planned route. Neither should be mistaken for proof that an order has left the store.

Make each handoff visible

Use an explicit sequence: receive the order, prepare it, assign a driver, start deliveries, then record delivery or an attempted delivery. In PURP, putting an order on a route does not itself mean it is out for delivery. Departure and completion are distinct events, which helps the store answer a customer’s question without guessing.

For example, a dispatcher sees three prepared orders for the afternoon. One has an incomplete apartment number. The team resolves that address before departure, assigns the ready orders to an active driver and confirms their sequence. The driver starts deliveries; the customer can then follow the applicable tracking updates. When the stop finishes, the recorded outcome gives the dispatcher a clear next action.

Agree who owns each correction. A driver should know whom to contact when the parcel, destination or customer instructions differ from the assigned work. The dispatcher should know which unfinished orders still need attention when a shift ends. Avoid treating a verbal “done” as the only record of a handoff.

Set honest customer tracking expectations

Customer tracking can communicate delivery progress and estimated arrival. An ETA is an estimate, not an appointment guarantee: traffic, route changes and time at an earlier stop can affect it. Explain the delivery window and support contact in language the customer can use.

PURP lets the business configure whether customers see the driver’s live location and how close their stop must be before that location becomes visible. ETA information can remain available when the driver pin is hidden. Choose the visibility policy deliberately, balancing useful updates with driver and customer privacy.

Phone permissions, connectivity and GPS quality affect live location. PURP checks location freshness and accuracy before exposing a driver position; a moving map is not guaranteed throughout every route. Rehearse a location-unavailable case and decide how staff communicate a delay. Do not train customers or dispatchers to interpret an absent pin as a cancelled order or a completed delivery.

Rehearse the stops that do not go to plan

The most useful delivery rehearsal includes an unsuccessful stop. Write down the permitted action, required evidence, customer communication and store follow-up for each situation:

  • No answer: approved contact attempts, waiting guidance and the next decision.
  • Wrong address: who verifies a correction before the driver proceeds.
  • Identification issue: the locally approved check and when handover must stop.
  • Payment issue: the approved recovery path without assuming payment succeeded.
  • Return to store: custody, order follow-up and stock handling responsibilities.

These are planning prompts, not universal legal rules. Configure PURP’s delivery proof requirements for your operation and confirm the staff can capture the required outcome. A delivery attempt needs its own reason; it should not be reported as a successful handover.

Run a complete shift rehearsal

Use approved test orders to walk through preparation, assignment, departure, customer tracking, delivery proof and one failed attempt. Check what the dispatcher, driver and customer each see at every stage. Repeat with GPS unavailable and an order requiring store follow-up.

Finish by reviewing unfinished work and confirming ownership of every exception. Staff access matters too: Admin, Delivery Dispatch and Driver App use employee accounts with the company’s MFA and permissions; a POS PIN does not open those products. Explore PURP+ delivery and the staff permissions guide before assigning the team.