Written by DROPS.ST.
For a cannabis brand or authorised wholesale operator, record shipment, receipt and retailer listing as separate events. A distributor shipment establishes neither that a particular retailer received the item nor that its customer-facing menu currently shows it.
DROPS gives the operator's own shop a useful foundation for this review: identifiable products, units, stock and customer-linked order items, with one catalogue used by the website and connected Telegram menu. That is concrete evidence for checking your own menu and recorded selections; a partner's listing needs its own source.
The partner evidence register below is external: DROPS' confirmed catalogue and order records do not establish distributor tracking, partner POS integration or automated listing alerts.
State which event the question concerns
“Is it available?” may mean dispatched, received, entered into a retailer's records, visible on its menu or actually orderable. Write the question precisely before recording a positive answer.
An interview with Valens' CEO published in July 2020 explicitly described products shipped to provinces while retailer listing was still pending. That historical example illustrates the distinction; it does not establish today's distribution route, market availability or permissions.
Identify the exact item, package and retailer or location under review. A company-wide statement may not describe every site, and a familiar product name may refer to a different unit or revision.
Keep a milestone evidence register
Use one row per item and partner context. This original aid describes review states, not native platform status names.
| Milestone | Evidence to keep | What it does not establish |
|---|---|---|
| Dispatch reported | Shipment reference, item, quantity and report date | Receipt at the intended destination |
| Receipt confirmed | Receiving source, date and matching item/unit | Entry into a retailer's selling system |
| Listing reported | Partner statement or checked listing source and scope | Current orderability in every location |
| Customer view checked | Relevant menu/context, item and observation time | A guaranteed future stock position |
| Unresolved or stale | Missing fact, last source and next review owner | A completed milestone |
Include the source's date and the time your team checked it. A newly received message may describe an event from an earlier week. Preserve that distinction when deciding whether the evidence is still useful.
Use permitted partner information and approved communications. A register of observed commercial milestones is not product certification, market approval or authority to distribute regulated goods.
Do not force a neat sequence
Events can be reported late or in a different order. A listing may be visible before a receipt report reaches your team. Record the observation with its scope rather than inventing the missing earlier events.
Separate confirmed, reported and unknown facts. If a partner says an item is listed but the relevant customer view cannot be checked, retain the statement and the unresolved question. Do not convert missing evidence into “not listed.”
For shipment discrepancies, use the delivery reconciliation guide. It compares requested, confirmed, shipped and received quantities. This register answers a later, different question: what evidence establishes the retailer's current listing position?
Hypothetical example: three sites, different evidence
A fictional distributor reports dispatch of SKU A. Site North later confirms receipt. A partner contact says the product is “live across the group,” but the statement gives no location or package details.
The reviewer finds the intended item on Site North's permitted customer-facing menu. Site South's relevant view is not available for review, and no evidence has arrived for Site East.
The register records dispatch, North's receipt and North's observed listing separately. South's listing remains reported but unverified; East remains unknown. It does not mark all three sites complete or interpret the missing views as proof of a failure.
These fictional milestones demonstrate evidence classification, not a sales result or an automated DROPS partner workflow.
Give stalled questions a useful next action
Set a review point appropriate to the approved partner process. Do not choose an arbitrary countdown and describe it as a contractual listing deadline.
For an unresolved case, record one question the responsible person can answer: which item revision, which location, which observation date or which menu context? Assign the next step rather than sending an undirected “any update?” to several contacts.
If the issue is your own shop's product visibility, use the priced-but-missing menu check. That diagnoses active, category and customer-context conditions in the operator's shop; it does not establish a partner's system behaviour.
Make your own product context dependable with DROPS
Choose DROPS when the team's commercial review needs a clear item, unit and recorded customer selection behind it. The connected website and Telegram catalogue gives your own channels a common product foundation while the external register keeps partner evidence distinct.
Explore the DROPS demos with one item and two different milestone claims. Inspect your shop-side catalogue and order context, then identify the separate evidence required for a partner listing. A reliable answer states the checked event and its scope instead of treating shipment as the end of the review.