Written by DROPS.ST.
Express pickup should reduce repeated work while preserving the checks for the correct handover. Match the customer and current order, compare prepared items, assign required checks and give exceptions a clear destination.
DROPS keeps selected items linked to the customer’s order. Separate order-action controls help you evaluate responsibilities, while the website and connected Telegram shop share catalogue and order data.
Order matching is not legal age or identity verification; assess required eligibility checks and supported completion actions separately for your authorised operation.
Define the improvement you want
A practical objective is: “Staff can locate the correct prepared order without reconstructing its contents from a conversation.”
A separate queue or sign does not identify the right record or completion owner. Establish which information should be available: reference, customer association, current quantities, preparation state and unresolved instructions.
Do not promise a fixed pickup time before measuring the work.
Assign four responsibilities
These are work responsibilities, not native app-role claims. A small team can combine them while preserving each check.
| Responsibility | Task | Escalation |
|---|---|---|
| Arrival contact | Locate the candidate order discreetly | Customer or reference mismatch |
| Preparer | Match items to the current record | Changed quantity or missing item |
| Handover checker | Complete required business checks | Eligibility or instruction unresolved |
| Order closer | Record supported completion outcome | Payment or status ambiguity |
Identify who takes over when someone leaves the station. “Someone checked it” is insufficient if the next worker cannot tell which check occurred.
Use the permissions guide to assess the needed order action instead of giving everyone administrative access.
Name who may apply the supported completion action, and test allowed and refused accounts. Performing the physical handover check does not itself grant that software permission.
Match the current order
Use the approved process to establish the customer and reference. One customer may have several orders, and names may be similar.
Check for changes, replacement, cancellation or earlier completion. Compare prepared items, units and quantities against the current actionable record.
A paper slip can reflect an earlier version. Hold a discrepancy for the authorised person rather than resolving it informally at the counter. Use the customer-approved correction process.
Keep readiness, payment and completion distinct
Preparation can be finished while another requirement remains unresolved. A payment indicator does not prove the right items reached the right person.
Define the evidence staff review before the final action. Do not make “ready” unofficially mean prepared, paid, verified and collected.
For an unclear financial state, use authorised reconciliation. Do not change status just to move the queue.
Health Canada identifies provincial and territorial responsibility for cannabis sales and store operation. This is therefore not a nationwide collection or age-check protocol. Health Canada: local responsibilities.
Give exceptions a destination
| Exception | Immediate response | Owner |
|---|---|---|
| Wrong candidate order | Locate the correct record | Arrival contact or supervisor |
| Items differ | Hold handover; compare versions | Correction owner |
| Required check incomplete | Keep pending under the procedure | Responsible checker |
| Payment unclear | Avoid unsupported status changes | Reconciliation staff |
| Customer requests change | Record the request | Correction owner |
The resolver needs to know which checks occurred and which remain open. Keep the ordinary process short by routing exceptions, not skipping them.
Share only the details the next person needs. Avoid open counter displays of full customer information. OPC’s PIPEDA guidance limits collection to the identified legitimate need; preserve records required by your applicable rules. OPC: limiting collection.
Hypothetical example: correct customer, outdated package
A fictional customer’s earlier order was corrected. The prepared package still carries the old reference and two-unit quantity, while the current record requires one unit.
The checker identifies the mismatch, holds handover and refers it for authorised reconciliation. They then repeat the item and quantity comparison before completion.
Finding the exception early is success. Quickly handing over the old package would not be.
Rehearse ordinary orders, multiple candidate orders, corrected quantities and unresolved conditions with fictional records in an approved environment. Use no funds, messages, real fulfilment or identity documents. Record the checks and exception owner.
Run an organised handover with DROPS
Choose DROPS when customer links, order references and items need to stay together for the handover team, including connected Telegram orders. Staff have concrete records to compare with preparation.
Explore DROPS and open the demo shops. Bring the responsibility table and an exception. Demonstrate the order views and permitted completion actions your staff will use.