Written by DROPS.ST.
For cannabis-shop teams or nicotine-vape staff reviewing an actual age check, identify the failed step, appropriate reviewer and necessary evidence. Give ordinary support enough information to route the question without copying a complete identity document by default. An unresolved check should not become a staff workaround.
DROPS supplies product and customer-linked order context for the underlying shop request. That helps identify which task is being discussed. It does not establish a native identity-verification service, age-review role or status-only masked view.
This guide retains a Canadian nicotine-vape context. Cannabis and other product, province and provider requirements need their own current review.
Establish what the result means
Record the actual check and reported outcome. A missing input, unclear evidence and an unresolved provider decision can require different next steps.
Do not infer a person’s age or legal eligibility from a cart, profile, familiar name or successful page view. An access prompt and an authorized verification decision are different evidence.
Name the actual process owner and which person may review the issue. A worker’s ability to open a customer record is not qualification to settle every identity question.
Use a review-evidence card
This original card is a business review aid, not a native age-check interface.
| Review entry | What to establish | Boundary question |
|---|---|---|
| Underlying task | Product/service and necessary permitted reference | Which activity needs the check? |
| Actual result | Failed or unresolved step and source/time | What is known rather than inferred? |
| Authorized reviewer | Qualified person/process and accepted handoff | Who may decide the question? |
| Necessary evidence | Actual required category and purpose | Does ordinary support need the document itself? |
| Submission route | Approved method and actual recipients | Is sensitive evidence handled appropriately? |
| Copies and retention | Applicable treatment and responsible owner | Are unnecessary copies being created? |
| Outcome and limits | Reviewed decision or remaining question | What does the result actually authorize? |
Use categories and approved references in the card. Keep identity values and credentials out of a broadly circulated worksheet.
Separate examining from copying
The OPC’s retailer guide distinguishes examining identification, recording information and copying a document. Use that distinction to question unnecessary collection; the guide does not settle every current age-check requirement for every product or province. OPC retailer identification guidance.
Determine the actual lawful and provider requirements with the responsible reviewer. Do not omit required evidence or impose a universal no-copy rule from this card.
Explain the approved route without asking customers to send sensitive documents into unrelated chats or general notes. Separate unrelated routine enquiries from actual verification tasks; justify their minimum evidence independently. Review existing copies under the actual policy. Outside Canada, have the responsible local reviewer establish necessary evidence and approved routes.
Hypothetical example: support can identify the open question
A fictional case has an unresolved verification result. The support worker can identify the relevant task and receiving reviewer but is not authorized to resolve it.
The card records the missing decision and necessary evidence category. The reviewer uses the approved process to obtain what is required; the general support summary does not reproduce the whole document.
This example establishes no valid age, required document list, native masking or permission to bypass the check.
Verify actual views and permissions
Use written cases or an agreed contained demonstration. Check what the worker, reviewer and other roles can actually retrieve, including permitted direct requests and copied output.
Current catalogue-edit access includes customer-account edits and wallet adjustments. A job title does not narrow that grant. Use the staff permissions guide to review the full scope.
If the desired boundary is finer than the demonstrated view, keep the gap unresolved and obtain an appropriate supported process. Do not rename the role and assume the restriction exists.
Close only the decision that was reviewed
Record the actual outcome, conditions and responsible person. A successful check in one process does not automatically approve another provider, transaction or receiving relationship.
Review copied evidence and access when duties change. Apply the actual retention policy and obligations rather than inventing a standard deletion period.
Choose DROPS when identifiable product and order context should help route a shop question accurately. Explore DROPS.ST and the shop demos with a fictional unresolved result. Identify the authorized receiver and necessary evidence before assuming the system has implemented the intended boundary.