Written by DROPS.ST.
Define a welcome bonus by its actual trigger, eligible recipient, recorded outcome and approved terms. Check those elements before presenting it to customers. A credited entry and a later purchase are separate events; neither proves that an incentive caused another order.
DROPS includes configured welcome-credit logic linked to Customer Accounts and wallet transaction records. Its source requires the wallet and welcome feature to be enabled with a positive configured amount, and applies duplicate-credit controls across supported registration paths.
That is a specific capability to evaluate alongside the common product and order system. It is not permission for a cannabis offer or a guarantee that every registration receives credit.
Name the actual event
The implemented welcome-credit path concerns new account registration. Do not describe it as an automatic reward on every first paid order.
Record which actual process is being reviewed and what outcome it should produce. Feature settings, recipient history and other guards can change whether the result is credited, skipped or needs investigation.
A visible promotional statement should not promise a result broader than the demonstrated rule. Keep a registration acknowledgement separate from payment-provider or buyer approval.
Keep a welcome-rule acceptance card
This original aid explains the review; it is not a native bonus-approval workflow.
| Rule entry | What to establish | Evidence before describing the offer |
|---|---|---|
| Trigger | Actual supported registration event | No invented purchase or repeat-order trigger |
| Availability | Included and configured feature | Actual setup can demonstrate it |
| Recipient | Applicable account and reviewed conditions | No assumed universal eligibility |
| Credit outcome | Credited, skipped or unresolved | Customer explanation matches the result |
| Duplicate case | Repeat request through permitted test fixtures | No unsupported promise of perfect abuse prevention |
| Terms and help | Approved use, material conditions and support owner | Unverified policies are not advertised |
| Later observation | Defined follow-up outcome and counting basis | Credit creation is separate from commercial impact |
Keep sensitive identity information out of the card. It needs the decision and permitted reference, not credentials or copied customer records.
Review the offer before activating its message
Health Canada explains that benefits tied to loyalty programmes can be prohibited cannabis purchase inducements. A welcome-credit label does not make an incentive permissible. Review the actual product, benefit, audience and communication through the appropriate qualified process. Health Canada guidance.
Do not offer an unauthorized cannabis reward or substitute another label to evade that review. Requirements for another jurisdiction, product or provider need their own evidence.
Explain actual spending terms, expiry and exceptional treatment only after they are documented and demonstrated where relevant. Do not promise banking protection, automatic refunds or cash-out from the presence of wallet credit.
Hypothetical example: registration succeeded, credit needs explanation
A fictional review case shows a successful registration and a skipped welcome-credit outcome. The reviewer checks the actual configured rule and relevant guard rather than announcing that every new account must receive the offer.
The approved explanation identifies the applicable outcome and support route without exposing private identity or operational security details. A duplicate-case fixture is reviewed separately.
This is an unfunded test specification, not a new production account, actual credit adjustment or guarantee that duplicate controls defeat every attempt.
Check the visible explanation and staff responsibility
In an approved contained demonstration, compare the stated offer with the actual account result and transaction description. Use written cases if safe interactive registration is unavailable; a test label alone does not prevent real effects.
Check phone readability and whether the customer can find the applicable terms and help route. Demonstrate any proposed message or report preview separately without sending it.
Current catalogue-edit access also includes customer-account and wallet changes. A welcome-offer duty does not establish a narrow bonus role. Use the permissions checklist before assigning corrections.
Keep later outcomes separate from the credit event
If the business reviews subsequent orders, define the period, included records and limitations. Count the actual event rather than treating a credit, account and order as the same conversion.
The repeat-order guide helps review current products, packages and required checks. A welcome credit does not bypass those decisions.
Do not infer a scheduled second-order campaign, automatic suppression or revenue uplift from the registration feature. Any further contact needs its actual purpose, channel and permission review.
Give a reviewed welcome rule a clear shop context
Choose DROPS when account-linked credit information should sit alongside identifiable products and customer-linked orders. Pair that foundation with an explained rule and accountable exception handling.
Explore DROPS.ST and the shop demos. Bring one ordinary and one skipped fictional outcome, then compare the actual supported behavior with the words a customer would see before approving any offer.