Written by DROPS.ST.
For transferred cannabis-shop or nicotine-vape buyer records, identify who performed the earlier check, what it covered and whether its evidence supports the proposed current relationship. An imported “approved” value does not automatically establish today’s buying authority.
DROPS connects Customer Accounts with orders and items, giving the destination workflow identifiable relationships to inspect. That is useful operating context, not proof of a native customer importer, buyer-verification engine or automatic revalidation.
This guide retains a Canadian nicotine-vape context. It approves no recurring-sales model, provider, product, jurisdiction or transfer.
Separate the old outcome from the new decision
Record the actual source and meaning of the earlier status. Software access, a provider decision and permission for a particular buyer relationship can be different outcomes.
Identify what changed: entity, contact, destination, product, channel, process or time. Do not assume every change invalidates evidence, or that no change matters. Obtain the appropriate actual review.
Keep required history distinct from information the new task does not need.
Use a transferred-evidence review
This original worksheet evaluates the evidence; it is not a native migration or activation screen.
| Review entry | What to establish | Current decision |
|---|---|---|
| Earlier check | Actual issuer, process, date and outcome | Explain what the old status meant |
| Evidence scope | Person/entity/product/channel or destination covered | Identify relevant limits |
| Permitted transfer | Actual authority, purpose and required fields | Do not copy a dossier by default |
| Changed circumstances | Known differences and unresolved facts | Determine the actual recheck needed |
| Portability | Whether the responsible process accepts the evidence | Keep assumptions open |
| Retention treatment | Required source/copy handling and owner | Preserve or dispose through the approved process |
| Activation outcome | Actual authorized decision and conditions | Separate access from current eligibility |
A field arriving successfully can be a transfer result while the eligibility decision remains pending.
Inspect the output without upgrading its meaning
Check identifiers, field definitions, source dates and exclusions through the approved process. Use synthetic cases for a rehearsal rather than generating unnecessary real customer exports.
The pre-migration export guide checks usable output. This worksheet asks what transferred verification evidence supports, which is a different acceptance question.
A catalogue move or reviewed AI product-change plan does not establish migration of customer, identity, financial or regulatory history.
Hypothetical example: the receiving relationship changed
A fictional record contains an earlier approved buyer status for a stated relationship. The proposed new relationship has a different receiving contact and destination.
The reviewer preserves the earlier source and asks the responsible process which evidence remains relevant, what may be transferred and which current checks are required. They keep the unresolved activation condition separate from the successful file receipt.
This example establishes no legal portability, native revalidation or actual buyer approval.
Review necessary information and actual authority
OPC’s Canadian PIPEDA collection guidance connects information requests with an identified need. Use that principle within the actual applicable requirements, without removing mandatory records or checks. OPC collection guidance.
Ask the qualified reviewer about actual lawful retention, permitted disclosure and the new use. A customer’s past order or a copied flag does not answer every question.
Nicotine, cannabis-filled products and empty hardware need their own actual product, province and provider scope. Do not copy a vendor’s subscription example as permission for a regulated sales model.
Keep activation and commercial terms separate
The verification-layer guide separates software, provider and buyer decisions. Buyer eligibility does not automatically approve credit terms, a payment service or another transaction.
Record who accepts the current outcome and who applies any supported account change. Broad catalogue editing also permits customer-account and wallet changes; it is not a restricted migration-review role.
No source snapshot freezes ongoing activity. Assign changed-source reconciliation and unresolved copies to their responsible owners.
Choose DROPS when connected customer and order-item context should give the current relationship a clear operating foundation. Explore DROPS.ST and the shop demos with a fictional earlier status and changed circumstance. Identify what the old evidence supports before treating imported access as today’s permission.