Written by DROPS.ST.
For cannabis shop operators, a proposed designation needs a clear meaning, an actual source and wording that stays within that evidence. Record those elements before placing the claim in a product description. A supplier's label or an attractive badge does not, by itself, establish what the designation proves.
DROPS holds names, descriptions and images in one catalogue shared with connected Telegram shopping. That gives approved product wording a common place to maintain. Where the configured AI shop assistant is included, it can help inspect records and prepare reviewed catalogue changes; the evidence decision remains separate.
Write down the exact claim
Record the proposed words and which product or business they describe. State the definition being relied on, who issued it and when it was checked.
Distinguish a documented fact from a designation's wider meaning. Evidence of one geographic fact should not silently become proof of a quality standard, certification or every part of a supplier's marketing description.
Ask for missing information rather than filling it with a plausible interpretation. Keep the source document's scope and date visible to the reviewer. Use appropriate qualified review for business credentials or environmental wording. Keep future plans separate from verified current availability and omit unnecessary private identifiers.
Use a claim-evidence card
| Card field | What to record | Review question |
|---|---|---|
| Proposed wording | Exact claim and affected reference | What would a reader understand? |
| Definition or criteria | Issuer, version and scope | Is this the actual standard being invoked? |
| Supporting evidence | Relevant document and checked fact | Which part of the wording does it support? |
| Limits | Missing, expired or narrower information | What remains unproved? |
| Intended use | Audience, channel and placement | Has this use been reviewed? |
| Decision and next review | Named factual reviewer, publishing approver, approval date and next review | Approved wording, held claim or evidence request? |
Keep this in the approved business process. It is an evidence aid, not a native certificate or automatic approval screen.
Check whether the source states a rule or proposes one
The research includes a February 2024 co-op response to a survey containing suggestions for a BC craft designation. That document is useful historical context, but it does not establish current official programme requirements. Check the actual current issuer and criteria for the proposed claim. Co-op survey response.
Use the same distinction for a supplier statement, association discussion or earlier interview. Record what it establishes, without upgrading it into independent certification.
Review the wording and its use
Keep the proposed description no stronger than the evidence. Do not add a safety, health or quality conclusion merely because the source supports a narrower production or business fact.
Health Canada's guidance addresses false or misleading cannabis promotion and the purpose, content and context of communications. Review the actual audience and placement alongside the evidence; a complete claim card does not determine whether publication is permitted. Health Canada promotion guidance.
Use the brand touchpoint guide for presentation after the wording decision. Design cannot supply missing proof.
Hypothetical example: a narrow fact, a wider badge
A fictional source document confirms one geographic fact about a proposed item. The planned description also calls it part of an official craft designation, but no current criteria or designation evidence is supplied.
The reviewer records the narrower supported fact and holds the wider claim while requesting the missing source. Any proposed public wording then receives the review appropriate to its use.
This invented case illustrates an evidence limit. It identifies no real producer, certifies no product and makes no quality or health claim.
Keep later changes tied to the approved record
When source information changes, identify the affected product wording and independent copies. Record what needs review before preparing edits.
Use the consistent product-record guide to keep the resulting fields aligned. In a configured DROPS AI workflow, ask for a plan affecting the identified records, then review the matches and proposed text before supported approved changes are applied.
Make product wording reviewable in DROPS
Choose DROPS when you want catalogue records and connected shopping views built around the same product information. Its configured AI catalogue support can help prepare the work while your team keeps the evidence and wording decisions clear.
See DROPS and explore the demos. Bring one proposed claim and its source. Establish what the document supports, decide the reviewed wording and use the common catalogue to maintain that decision consistently.