Written by DROPS.ST.
When an authorised cannabis wholesaler shares a revised commercial document, record which retailer should receive it and which version they acknowledge. “Sent” is a useful event, but it does not establish that the intended person has the current file or understands the required next step.
DROPS supplies the commercial context for that check. Product references, units and packages identify the selection, while customer-linked order items identify the relevant purchase. Staff can connect a document question to a specific shop record instead of a general attachment circulated without context.
Document distribution and acknowledgement remain in the approved business process; those records do not establish native file delivery, read receipts, regulatory traceability or document approval.
State what the revision affects
Identify the document reference, revision and intended use. Specify whether it changes a commercial instruction, clarifies a package meaning or needs a separate authorised review.
Keep the issuer's facts distinct from the message explaining them. Do not rewrite a technical, certification or lot-specific document to make it appear to cover another item.
This guide checks receipt of the intended revision. It does not decide whether the document proves product safety, certification, lawful supply or acceptance of terms. Those questions keep their own evidence and decision owner.
Distinguish the receipt stages
| Stage | Evidence | What remains open |
|---|---|---|
| Prepared | Approved file/reference and recipient scope | Has it been sent through the permitted route? |
| Sent | Recorded sending event | Did the intended recipient receive that version? |
| Technical indication | Available delivery or opening signal | Which person and file does it establish? |
| Recipient acknowledgement | Confirmation identifying the revision | Any required review or action? |
| Issue resolved | Checked outcome from the responsible person | Any remaining condition? |
These are business review stages, not DROPS status labels. Choose evidence suitable for the document's actual purpose.
Microsoft's Outlook guidance distinguishes mailbox delivery from reading and notes that recipients may decline read receipts. That illustrates the limits of technical signals; it does not establish Outlook tracking inside DROPS. Microsoft: delivery and read receipts.
Keep a short distribution record
Record the document/revision, affected item or order, intended business contact, permitted channel, sending time, acknowledgement and next owner.
Use only the recipients appropriate to the purpose. An earlier contact list should not automatically receive every revision. Confirm the channel and provider permission for the actual content; an account record alone does not supply it.
Ask for acknowledgement of the reference and revision, not just “got it” when several files exist in the conversation. Use the business's approved process where a specific form of notice or acceptance is required; this worksheet does not certify legal service.
Hypothetical example: the message arrived, the wrong file remained
A fictional wholesaler sends commercial instruction revision 3 to a retailer. The contact acknowledges receipt but refers to revision 2.
The owner clarifies the intended reference and preserves that discrepancy. After the permitted follow-up, the contact identifies revision 3 and its relevant order. The owner records the acknowledgement and any separate action still required.
A delivery signal for the earlier message would not have resolved the version mismatch. Nor does receipt of revision 3 prove approval of changed terms or a technical claim inside it.
Assign unanswered acknowledgements
Give each unresolved case an owner, specific question and review time. Do not repeatedly resend a whole bundle when the problem is one missing reference or an unavailable contact.
If an order decision depends on the document, keep that decision visibly unresolved until the appropriate evidence is available. Avoid inventing a deadline, statutory receipt rule or automatic approval.
The quote-version guide checks which commercial revision was accepted. The vendor escalation guide helps transfer an unanswered issue to someone who accepts responsibility. Receipt and those later decisions are related but distinct.
For staff instructions, use the internal version-control guide. Sending to an external retailer has a different recipient and confirmation task.
Give the document its order context with DROPS
Choose DROPS when identifiable products, package choices and customer-linked order items should ground your wholesale communications. Those records help explain which selection the document concerns while your business retains responsibility for its distribution and required review.
Explore DROPS and open the demo shops. Bring a fictional document revision and relevant order. Inspect the item context, then define the separate receipt evidence and next action your team needs.