WhatsApp Is Not a Dispatch System: The Hidden Compliance Risk in Cannabis Delivery

Walk into the back of almost any BC cannabis retail store that runs delivery, and you will find the same setup. A dispatcher with a phone, a group chat with the drivers, and orders being coordinated through WhatsApp, iMessage, or some equivalent messaging app.

It works, in the sense that orders get assigned and deliveries get made. The problem is that it does not produce the records the LCRB requires, and that gap carries real enforcement risk for the retailer.

Why Retailers Use Messaging Apps for Dispatch

The appeal is obvious. Messaging apps are free, familiar, and already on everyone's phone. Setting up a group chat takes thirty seconds. There is no software to learn, no subscription to manage, and no onboarding for drivers.

For a retailer who launched delivery quickly or who runs a small volume of orders, it feels like a practical solution. And in terms of getting orders out the door, it often is.

The compliance problem is not with the coordination itself. It is with what the coordination does and does not produce as a documented record.

What a WhatsApp Thread Actually Produces

When a dispatcher sends an order to a driver via WhatsApp, several things happen and several things do not happen.

What happens: the driver receives the order details. The dispatcher knows who was assigned. The conversation exists as a message thread.

What does not happen: a timestamped, structured delivery record is not created. The driver's identity is not linked to that specific order in any system. Age verification at the door is not captured. The outcome of the delivery is not formally recorded. A delivery manifest is not generated.

If an LCRB inspector asks for your delivery records for a specific date, a WhatsApp thread is not what they are looking for. It is not formatted as a delivery log. It does not contain all the required fields. It cannot be exported in a form that demonstrates compliance. And if the dispatcher or driver ever changes phones, leaves the company, or deletes their messages, those records may not exist at all.

The Specific Records That Messaging Apps Cannot Produce

The LCRB requires specific documentation for every delivery a licensed retailer completes. A messaging-based dispatch system does not reliably produce any of the following.

Driver identity linked to a specific delivery. A group chat may show who was online, but it does not create a structured record tying a specific driver to a specific completed order.

Timestamped delivery completion. A driver sending "done" in a chat is not a timestamped delivery record. The time shown on the message is the time the message was sent, which may or may not correspond to when the delivery actually occurred.

Age verification documentation. There is no structured field in a messaging app for capturing what ID was presented or confirming that a 19-plus check was conducted.

Failed delivery documentation. A driver texting "no one home" does not constitute a documented failed delivery with the reason code and return confirmation the LCRB requires.

A delivery manifest. A manifest is a consolidated document covering all stops in a run. A message thread is not a manifest.

The Risk Is Not Theoretical

Retailers sometimes treat the documentation gap as a theoretical risk, something that would only matter if they were unlucky enough to be inspected on a bad day. The inspection data suggests a different framing.

Over the past couple of years, the LCRB has conducted hundreds of inspections of BC cannabis retailers, and delivery records are part of the standard review for stores operating a delivery service. The question is not whether an inspector will eventually ask for your delivery records. It is whether those records will exist when they do.

What a Compliant Dispatch System Produces

A purpose-built delivery dispatch system creates the records that messaging apps do not. When an order is dispatched, a structured record is created with the driver's identity, the order details, and the timestamp. When the driver completes age verification at the door, that check is captured as part of the delivery record. When the delivery is marked complete, a timestamped proof of delivery is generated. When a delivery fails, the reason code and return confirmation are documented.

At the end of the run, a delivery manifest is produced automatically covering every stop the driver completed.

None of this requires additional administrative work from the dispatcher or the driver. It happens as a byproduct of using the system to run the delivery.

Making the Transition

Switching from a messaging-based dispatch workflow to a purpose-built system is a smaller operational change than most retailers expect. The core workflow, dispatcher assigns order, driver picks up, driver delivers, dispatcher sees status, does not change. What changes is that the system creates records at each step automatically.

For most retailers, the adjustment period is a few deliveries. Drivers learn the app quickly because the workflow mirrors what they were already doing, with a documentation layer built in.

The more meaningful change is for the retailer. The difference between running an inspection-ready delivery operation and running an undocumented one is not effort. It is tooling.

This guide is based on publicly available LCRB documentation and inspection data current as of October 2026. Cannabis regulations change — always verify current requirements with the LCRB directly at gov.bc.ca/lcrb.

Grably is a brand of Grably Technologies Inc.
grably.ca · hello@grably.ca · 778-900-8886