Dispensary Operations Research

Measuring Online Order Readiness Time in a Dispensary Pickup Queue

A study protocol for measuring how long a dispensary pickup order takes to become ready after the customer submits it, with separate stages for acceptance, picking, verification, and handoff.

Measuring Online Order Readiness Time in a Dispensary Pickup Queue

Key takeaways

  • Measure acceptance, picking, verification, and handoff as separate intervals.
  • Report the customer wait after arrival separately from store preparation time.
  • Keep cancelled and changed orders in the sample so the result is not flattered.
  • Test one queue change against the same stage definitions and window.

Question and scope

This study asks how long a dispensary pickup order takes to move from customer submission to a verified handoff. The unit is one online order tied to one customer and one pickup window. The review follows the order through acceptance, picking, verification, and handoff, and records the reason for any delay. It does not judge whether the customer should have been sold the product or whether the product was clinically appropriate.

Set the scope to one store, one ordering platform, and a fixed period. Record the pickup hours, the staffing model, and the order types included. If the store changes its menu provider or its verification procedure inside the window, separate the periods. A platform change can alter what the timestamps mean more than a change in staff behavior. Name the order volume before sampling.

What the sources establish

The Virginia Cannabis Control Authority sets the licensed retail context in which these orders occur but does not publish a local readiness benchmark. NIST privacy guidance is relevant because an order record links a customer to a product and a pickup time. GAO data-reliability guidance describes how to assess records that were created for operations rather than research. Together the sources support a narrow process review.

The sources do not establish a target number of minutes or prove that a faster handoff improves the customer experience. A fast order can still be wrong, and a slower order can be accurate and respectful. The study therefore measures the stages and the exceptions, not a single speed score. It reports the local result with its window and exclusions.

Definitions and measures

Define submission as the time the customer completes the online order. Define acceptance as the time the store confirms the order and the pickup window. Define picking as the time the product is retrieved and staged. Define verification as the completion of the store's identity, age, and order checks. Define handoff as the time the customer receives the order.

Measure the interval between each stage, the number of orders that wait at each stage, and the number that are cancelled or changed after submission. Record whether the customer arrived before the order was ready. Report the median, the interquartile range, and the slowest orders. Keep the order type and the item count beside each interval.

Record the pickup window the customer was promised at submission, because readiness against an undefined promise cannot be evaluated. Note whether the window was changed after the order was accepted and who told the customer. A store that moves the window without recording the change will look faster than the customer's experience. The promised window should be recorded before the order is picked, not reconstructed after the customer complains.

Sampling and collection

Sample orders rather than customers. A single customer may place several orders with different readiness paths. Include small and large orders, orders with age-restricted items, and orders that required a substitution. Record the channel, the staff role, and the time of each stage. A sample drawn only from small orders will miss the verification work that creates the queue.

Collect the order platform log, the picking record, the verification check, and the handoff timestamp. Mask customer details that are not needed for the analysis. If a timestamp is missing, record the gap and keep the order in the sample. Dropping the slowest or least documented orders would make the result look better than the customer experience.

Include orders placed outside the store's busiest hours, because a small queue can hide a verification step that only appears at peak. Record the order volume and the number of open pickup stations for each sampled hour. A comparison that ignores the load may credit a process change for a quiet week. The quiet and peak hours should be compared as separate strata.

Calculating readiness time

Calculate the total readiness time and each stage interval separately. Do not combine picking and verification into one step, because they may be performed by different people and fail for different reasons. Report the stages that account for most of the total. A single average can hide a long verification queue behind a fast pick.

Report the customer wait after arrival separately from the store's preparation time. A customer who arrives early and waits is not the same as an order that was not ready when promised. Use the promised pickup window as the reference and record whether the order met it. The comparison should include the orders that were cancelled before pickup.

Report the orders that were ready before the customer arrived separately from those that were ready during the pickup window. An order that is ready early is a different result from one that is ready on time after a long preparation. The customer wait should be measured from arrival, not from the promised time. The two results should be shown side by side rather than collapsed into one completion rate.

Separating cause from delay

Classify each delay by stage and cause. A delay may come from order volume, a missing product, a verification question, a staffing gap, or a customer change. These causes require different fixes. A single readiness percentage cannot tell the manager whether to add a picker, change the menu, or adjust the pickup promise.

Review a small number of slow orders in detail. Look for orders that were picked but not verified, verified but not staged, or staged but not handed off. Check whether the customer was told about the delay before arrival. Do not infer that the staff were careless from a timestamp alone. The record should show what happened.

Check whether the order was picked from a shelf location that matched the menu record. A pick delay may come from a product that was stored in the wrong place rather than from staff speed. Record the location and the correction so the inventory lead can fix the source. A shelf-location correction should be assigned to the inventory owner with a date.

Analysis and reporting

Report the number of orders, the share ready within the promised window, the median and tail of each stage, and the cancellation rate. Break the results down by order type, item count, channel, and shift. Report the orders with a missing timestamp separately. A completion rate that excludes them is not a full picture.

Compare the results with the store's own prior period rather than an external benchmark. If the store changes its pickup promise or its verification step, keep the definitions stable and use a comparable order mix. A before-and-after comparison is more credible when the sample size and the exceptions are visible. The report should name the uncertainty beside the result.

Limits and next action

The study cannot prove that a particular readiness time caused a better customer outcome or that the order record captures the full customer experience. It also cannot explain why a customer cancelled without telling the store. A missing timestamp may mean the step happened elsewhere. The analysis should distinguish a documentation gap from a process delay.

Choose one change and assign an owner. The change might be a separate verification station, a clearer pickup promise, or a menu check before the order is accepted. Set a repeat sample date and keep the definitions stable. A useful result is a pickup pathway that the next busy shift can follow without rebuilding the routine.

Keep the readiness definitions in a short procedure beside the pickup counter so a new shift can apply them without asking. Review the procedure after the next menu or platform change. A definition that lives only in the audit file will not survive staff turnover. The procedure should name the owner who updates it.

Sources

The sources below support the operational, privacy, and consumer-protection context for this review. They do not measure this store, and no source is presented as a local benchmark. Check each link for its date and scope before reuse. The operational finding comes only from the store records described in the method.

This article describes a measurement method rather than legal or compliance advice. Confirm current requirements with the applicable authority and qualified advisers. Keep the local evidence separate from those requirements. Record the review date and the owner who accepted the interpretation.

Reviewed by the DispensaryVA editorial team on 2026-11-08.