Written by DROPS.ST.
For cannabis retail buying notes, record the product request and the decision it might inform. Leave unrelated personal stories out, and keep an individual support task separate from a general assortment question.
DROPS gives the team product, unit, package and stock context, with customer-linked order items when relevant. Use those records to identify what the customer means before adding another note. The useful buying signal may be a missing pack option or unclear description, not a detailed profile of the person who mentioned it.
State why the note is needed
Ask what the buyer or owner will do with the information. Are they considering a package option, clarifying a unit or investigating repeated confusion about an item?
The OPC recommends limiting personal-information collection to an identified purpose. Apply that question before saving a conversation as feedback. OPC collection guidance.
If the note instead concerns a specific unresolved order, route it through the approved support process. A buying summary should not become the place where that customer’s case is managed.
Use a feedback classification sheet
This original aid belongs in the business’s approved record process; it is not a native DROPS note form.
| Information | Useful buying note | What to omit or separate |
|---|---|---|
| Product reference | Relevant item or defined category | Unrelated purchase history |
| Requested option | Package, quantity meaning or factual information requested | Speculation about personal motivations |
| Current context | Approved unit, availability or description checked | Unsupported product or health claims |
| Evidence status | Individual request or reviewed recurring pattern | Assumed market demand |
| Buying decision | Question for the responsible buyer | An unapproved promise to obtain stock |
| Individual follow-up | Separate permitted support task if needed | Contact details copied into broad summaries |
Keep uncertainty visible. “Customer asked about a smaller pack” is a request; “customers will buy smaller packs” is a prediction that needs different evidence.
Capture the meaning without copying the story
Use concise factual language. Identify the requested product option and any ambiguity the team needs to resolve. Do not retain a health narrative, household information or a judgment about the customer merely to make the note feel complete.
If a sensitive question requires another approved process, route it there. Do not convert it into a consumer recommendation or medical inference for the buying team.
Where current product wording caused the confusion, the description consistency guide may address the issue without adding a new assortment item.
Hypothetical example: a smaller package request
A customer asks whether a product comes in a smaller package and gives personal background while explaining the request. The staff note records the product reference, requested package option and uncertainty about current availability. It does not reproduce the background.
The buyer checks the catalogue and discovers the immediate issue is an unclear package label. That is a description decision, not yet evidence that a new product should be purchased.
This hypothetical example shows how the buying question can change after checking facts. It is not measured demand or an actual customer conversation.
Summarize cautiously for the buying review
Group comparable requests only after checking their meaning. Similar words can refer to different units, packages or tasks. Distinguish confirmed recurring confusion from a collection of unrelated comments.
A small summary can still reveal personal information through context; removing names does not guarantee anonymity. Review what is necessary and who receives it.
Keep follow-up contact separate and appropriately authorized. The purpose of buying analysis does not automatically authorize a new message or unrelated use of customer information. OPC use and retention guidance.
Retailer visits, regional sales conversations and business-partner responses can use the same classification. Record the source, comparable-unit basis and sample limits, then choose clarify, investigate, retain for later or no change. A request to expand a one-item assortment is interest to review, not an order or national demand.
Give the note a decision and review point
Name who reviews the feedback and what outcome will be recorded: clarify information, investigate supply, retain the question or take no further action with a reason. Do not keep collecting personal detail because the buyer has not decided.
Use the approved retention treatment for these notes. This guide sets no universal disposal date and promises no automated deletion or profiling controls.
DROPS keeps the product and order facts connected. Use that context to make feedback precise enough for a buying decision without turning ordinary questions into unnecessary personal records.
Explore DROPS.ST and the shop demos. Bring a fictional product request and identify the smallest note that lets the buyer understand the question, its evidence and the next decision.