CannaRewards Cannabis loyalty software for brands
Start a label pilot

Launch scope

Build the first label-pilot brief.

Send batch materials, set the first reward menu, and define the feedback prompt so CannaRewards can return QR-ready labels and a signal-report plan. Commercial terms follow after the first scope is clear.

CannaRewards QR marker added to a launch label
Launch handoff Batch materials in. QR-ready labels out. Reward setup, feedback prompt, and signal-report plan stay tied to the first run.
Build the launch brief See the receipt
Batch file QR-ready output Scan setup: first run Feedback prompt: first run CannaRewards QR marker added to a launch label
  1. Input check Batch materials Label PDFs, METRC details, COA evidence, product names, and package counts.
  2. Setup check QR label package QR-ready batch-label list, scan points, reward costs, and the first feedback prompt.
  3. Signal check Action queue Scan activity, feedback, reward views, saves, claims, and weekly action queue.
  4. Terms check Commercial terms Confirmed after the first label run, reward menu, feedback prompt, and reporting scope are clear.

Buyer receipt

The first label pilot reads like a receipt.

Use this surface to check what the brand sends, what CannaRewards returns, what the pilot shows, and what belongs on a later path.

Brand sends

Launch inputs

  • Label PDFs
  • METRC details and COA evidence
  • Product names and package counts
  • Reward direction and first feedback prompt
CannaRewards returns

QR-ready handoff

  • Batch-label list for print handoff
  • Scan setup and point values
  • Reward costs and customer scan state
  • Feedback prompt plan
Pilot shows

Signal to act on

  • Scan activity and repeat behavior
  • Feedback on the first product moment
  • Reward views, saves, and claims
  • Weekly action queue
Separate scope

What waits

  • Product rewards after a participating retailer checkout path is ready
  • Published result claims after customer evidence is verified
  • Additional label runs after the first QR-ready handoff is clear
  • Commercial terms until the first scope is clear

What changes scope

Choose the first decision for the brief.

Use the scope path to decide what belongs in the first label handoff and what belongs after pilot signal or checkout-path readiness.

First handoff

Start when source label files and package context are ready.

QR-ready output Batch-label list Print handoff
  1. 01Source labels checked
  2. 02QR-ready list returned
  3. 03First scan setup attached
Brand sends
Label PDFs, METRC details, COA evidence, product names, and package counts.
CannaRewards prepares
QR-ready batch-label list for print handoff plus the first scan setup.
Scope note
Without batch materials, the launch brief stays exploratory.
Send batch context
Reward direction

Use brand-controlled rewards to learn what customers save and claim.

Reward menu Merch, digital offers, brand experiences Product rewards need checkout readiness.
  1. 01Reward costs set
  2. 02Views, saves, claims watched
  3. 03Product rewards held for checkout path
Menu starts with
Merch, digital offers, or brand experiences.
Signal watched
Reward views, saves, claims, feedback, and repeat scan behavior.
Scope note
Product rewards need a participating retailer checkout path.
Scope rewards
Scan question

Define the first feedback prompt before the QR label package is returned.

Feedback prompt One first-scan question Signal report plan follows the prompt.
  1. 01Question tied to product or batch
  2. 02Feedback and repeat scans watched
  3. 03Next action kept narrow
Prompt asks
One product or batch question tied to the first scan moment.
Signal watched
Feedback, scan activity, repeat behavior, and reward demand.
Scope note
Keep the first question narrow so the signal report points to a usable next move.
Plan the prompt
Later path

Separate checkout-dependent rewards from the first label pilot.

Ready now QR labels, scan points, feedback Published claims wait for verified customer evidence.
  1. 01Non-product rewards can start
  2. 02Product rewards need checkout path
  3. 03Published metrics need verification
Ready now
QR labels, scan points, feedback capture, and non-product reward demand signal.
Needs
A participating retailer checkout path before product rewards are added.
Scope note
Published customer result claims wait for verified customer evidence.
Scope separately

Fit check

Use the launch brief when labels can carry the first customer action.

The first pilot works best when the team can start with batch materials, a QR-ready label run, brand-controlled rewards, and a signal report. Some requests belong after the needed path is ready.

Good fit now
  • Batch labels, METRC details, COA evidence, product names, and package counts can be shared.
  • The first reward menu can start with merch, digital offers, or brand experiences.
  • The team wants scan activity, feedback, repeat behavior, and reward demand as pilot signal.
Separate scope
  • Product rewards need a participating retailer checkout path.
  • Published customer metrics wait for verified customer evidence.
  • Batch materials and the first feedback prompt are not ready.

Scope FAQ

Answer scope questions before the launch handoff.

These answers stay inside the launch model: labels first, rewards and costs next, then signal reporting and checkout paths as the program grows.

Why start with launch scope?

The useful decision is what the first label pilot includes: batch materials, QR-ready label handoff, scan points, rewards, feedback, and signal reporting.

What is the first scoping step?

Start with batch materials: label PDFs, METRC details, COA evidence, product names, and package counts.

What happens after labels are ready?

Add scan points, reward costs, the first feedback prompt, and a signal report so scans and reward demand can inform the next move.

When do commercial terms come in?

Confirm commercial terms after the first label run, reward menu, feedback prompt, and reporting scope are clear.

Launch handoff

Send the materials that make a label pilot real.

Share the batch context and first reward direction so the launch brief can move into a QR-ready label handoff and scan rewards.

QR-ready output Batch-label list Scope first, then return the print handoff.
Brief Batch context.

Label PDFs, METRC and COA context, product names, and package counts.

Set Reward and feedback scope.

Reward menu, scan points, reward costs, and first feedback prompt.

Return QR-ready label handoff.

QR-ready batch-label list for print handoff plus the first scan-reward setup.

Build the launch brief

What to read next

Use these pages to tighten fit before sending materials.

Scope is clearer when the product model, reward menu, and launch inputs are already understood.

Use case

QR flow and scan mechanics.

See the product mechanics before the launch conversation starts.

Review the QR flow

Geo fit

New York launch fit.

Check how batch-label readiness, rewards, and feedback fit a New York launch.

Check New York fit

Answers

Rollout questions.

Handle objections on scans, rewards, checkout paths, and rollout shape.

Read rollout answers

Company

Company context.

Give the buyer the trust and company context behind the product story.

See company context