Written by DROPS.ST.
Define what a referral code identifies, which event would qualify for a reward and who approves that reward before presenting an offer. A shared code, new account and completed order are different events. None alone proves that a reward is owed or that the programme is permitted.
DROPS provides identifiable products, units and customer-linked order items in a common website and connected Telegram shop. Those records give the review a concrete commercial reference. Demonstrate any referral attribution, code rules or wallet-reward tools separately in the package and configuration you intend to use.
Decide whether the proposed offer belongs in the business
Begin with the intended product, audience, jurisdiction and communication channel. Review the actual offer with the responsible owner before designing its reward calculation.
For Canadian cannabis activity, Health Canada's promotion guidance describes limited permissions and a specific prohibition, unless authorized under the Act, on certain inducements, including providing a thing or service as an inducement for a cannabis purchase. A referral worksheet or private shop does not approve a reward arrangement. Health Canada promotion guidance.
Other products and countries need their own current review. Keep an unresolved offer on hold; do not simply rename a discount as wallet value and assume its treatment changes.
Define the referral relationship
Identify the referring person, referred account and relevant business event using the actual supported references. A customer-entered code may be a claim to investigate rather than conclusive proof of an introduction.
Specify what happens when two people claim the same introduction, the account already existed or the referenced order is cancelled. Define exceptions before staff face a disputed reward.
Keep only the information needed for that relationship. Do not collect a friend's personal details merely because the existing customer supplies a code; review the actual collection and contact authority separately.
Use a referral decision register
This original aid records the business rules and evidence. It is not a native DROPS referral ledger, fraud detector or automatic reward workflow.
| Decision entry | Evidence to establish | Owner action |
|---|---|---|
| Permitted offer | Actual product, market, audience and approved terms | Hold unresolved eligibility |
| Referral reference | Supported code and claimed relationship | Resolve ambiguous attribution |
| Qualifying event | Precisely defined order or other approved event | Distinguish signup from completion |
| Exclusions | Existing account, duplicate claim or changed order | Apply the approved exception process |
| Reward meaning | Amount, unit, limits and permitted treatment | Explain the actual value |
| Decision authority | Named reviewer and supported execution route | Separate preparation from granting value |
| Outcome record | Approved, rejected or still unresolved with evidence | Keep the decision attributable |
Do not put account credentials or wallet secrets in the register. Keep access appropriate to the record's purpose.
Distinguish shop value from money received
A displayed customer balance does not by itself establish a transferable asset, refundable deposit or cash withdrawal right. Explain the proposed reward's actual contractual meaning, supported use and applicable treatment.
Current DROPS catalogue-edit access also includes customer-account edits and wallet adjustments. A staff member preparing a referral case therefore should not receive that broad grant merely to review a code.
Use the manager permissions checklist to assess actual powers. There is no referral-review-only role established by this guide.
Hypothetical example: a code appears on two requests
In a fictional evaluation using an already approved nontransactional scenario, two request records contain the same code. One refers to an existing account; the other has an unresolved order reference.
The reviewer preserves both facts and applies the written eligibility process. They do not grant two rewards because two code entries exist, or treat the unresolved order as completed.
This example illustrates evidence classification. It authorizes no cannabis incentive, actual wallet adjustment or automatic duplicate detection.
Check the result and the measurement basis
Rehearse the rules with fictional records in an agreed demonstration. Inspect an ordinary qualifying case and an excluded or disputed case. Verify what the actual tool records and which decisions remain with staff.
Keep code uses, eligible events, approved value and resulting orders as separate counts. Explain exclusions and the review period. An order carrying a code does not establish that the programme caused an additional purchase or produced a profit.
Choose DROPS when customer-linked orders and a common web and Telegram catalogue should anchor your business review. Explore the shop demos with the register, then demonstrate the available attribution and value controls before relying on an approved referral arrangement.