Loyalty cards

Loyalty cards let returning customers collect stamps or points. They are separate from referral and affiliate programs. Loyalty activity does not count toward rewarded-order usage.

Create a card

The sidebar lists the loyalty pages under Loyalty: Cards, Customers, Messages, Reports and Counter setup. On a phone, tap Loyalty in the bar at the bottom, then pick one from the row of tabs. Cards shows each card's pass design, name, status, customer count and visits in the last seven days. The name appears under each pass, so cards that share a logo stay easy to tell apart. With no cards, it shows the three setup steps a shop needs before its first stamp: create the card, print the counter poster, and set up the scanner. The last step has an Open Counter setup button. New card sits in the header. After you save a card, a New card tile also appears in the gallery.

Choose New card to open the full-page editor. New cards have three steps, Reward, Design and Publish. The stepper marks the current step and shows a check for earlier steps. Choose an earlier step to return to it. Choosing a later step checks the current step and moves forward once. The defaults are 10 stamps per reward, one stamp per visit, a 30-minute wait between stamps and a wide barcode. You cannot change a saved card's type.

Under Card type, choose Stamp card or Points card. Enter Card name and Reward text. Language tabs appear only if your company uses more than one language. Use them to write each company language. A missing-copy label marks unfinished languages.

For a stamp card, set Stamps per reward. Type a number from 1 to 50, or use the minus button, Fewer stamps, and the plus button, More stamps. Open Advanced to change Stamps per visit, Most stamps staff can give at once and Wait before the same card can get another stamp. This group starts closed and shows the current values in its summary. A saved card shows its type at the top of the Reward tab. The wait is in minutes and applies to the same card on every scanner. Set it to 0 for no wait. The preview skips it.

For a points card, set Points per visit. Zero is allowed. Turn on Earn points on spending to complete the sentence "Customers earn 1 point for every $1.00 spent". Type the points and the amount in your company currency. Grizzlee rounds earned points down to a whole point. For example, 3 points for every $1.00 earns 4 points on a $1.50 purchase.

Choose Add reward to expand the points catalog. Enter Reward text in every language you use and set each Cost in points. Costs must be positive whole numbers.

Design the card

Under Reward, enter the card name and reward text in every company language. Points reward text lives beside each catalog cost.

Under Design, drop a PNG or JPEG onto Logo upload, or choose a file. On Apple Wallet the logo replaces the card name in the pass header, the way a printed card shows only your brand. Google Wallet always shows the card name beside a round logo. A wide PNG with a transparent background looks best. Grizzlee trims empty transparent edges from PNG logos so the mark fills the space. If at least three corners of a PNG are the same solid colour, such as a white or black box around the mark, Grizzlee trims that border too. Trimming does not make that colour transparent, so it still shows behind the mark. JPEG logos are not trimmed. Trimming happens on upload, so upload an older logo again to trim it. The upload shows your logo on the card colour. If the logo sits on a solid box, such as a white background, a warning asks you to upload a wide version with a transparent background.

Set the card's colours under Colours. After you upload a logo, Colours from your logo comes first and offers card colours taken from that image. Under Theme, Espresso, Sage, Oat, Blush, Ink, Tomato, Butter and Graphite each set the card, text and small headings colours together. The selected theme stays marked while all three colours match. Open Custom colours to pick your own Card colour, Text colour and Small headings colour. Changing the card colour leaves the other two alone. Stamp cards also show Stamp icon tiles.

Open More design options to set Banner photo, Banner crop position, Custom stamp icon and Code shown on the card. Only stamp cards have Custom stamp icon. This group starts closed. Its summary shows whether a banner or custom icon is set and which code the card shows. Logos and stamp icons accept PNG or JPEG files up to 1 MB. Banner photos accept up to 5 MB. Banner crop position appears after you upload a banner and moves the photo vertically. The live preview shows the crop and stamps over the photo. Without a banner, the strip uses the background colour. The artwork contains no text. Choose Wide barcode (recommended), Line barcode or Square QR code. The scanner reads all three, and the card code stays the same.

The preview stays beside the form on wide screens. On smaller screens, choose Preview at the bottom of the screen to open it. On a saved card, it appears on the Reward and Design tabs. The pass sits in a rounded panel. Switch between Apple and Google, then choose Show back to read the reward rules and merchant name. Show front returns to the pass. Preview actions never change a customer's balance.

A saved card opens on five tabs. Reward holds the name, reward and earning rules. Design holds the logo, colours, stamp icon and banner. Share holds the sign-up link, the counter QR codes and the poster. Game holds the counter game and shows On while the saved game is on. Automatic messages shows how many automations are on. The address keeps the open tab, so reloading the page returns to it.

The header shows the card's status, Draft or Active. On a draft card, choose Publish card and confirm to save it as active right away. On an active card, Pause card saves it as a draft after you confirm. Active cards accept sign-ups and balance operations. A draft card closes its sign-up page, and staff can't add stamps or points or redeem rewards for existing customers. The game and automatic messages stop too. Customers keep their cards and balances. If you have other unsaved changes, publishing or pausing saves them as well.

When you change anything on a saved card, a bar appears at the bottom of the screen with Unsaved changes, Discard and Save. Save saves every tab at once and keeps you on the current tab. A short message at the bottom of the screen confirms the save. Discard puts every tab back to the saved card. Unsaved changes stay when you switch tabs. New cards have Continue at the bottom of the first two steps and Back on the last two. Continue checks only the current step. From the Design step, Save draft in the header checks every step and saves a new card as a draft. In Publish, Publish card checks every step and saves it as active. These checks take you to the first field that needs fixing, switching tabs and opening its group if needed. Leaving with unsaved changes asks for confirmation. That covers links in the sidebar and the More menu, browser Back or Forward, switching companies, and closing or reloading the tab.

Share the sign-up page

For a new card, Publish shows a summary. It lists Card type, Reward text in your company's first language and Stamps per reward. Points cards show the number of catalog rewards instead of reward text and stamps. Both types show Sign-up link. The sign-up address is your business name in lowercase with hyphens. If another card already has that address, Grizzlee adds a short suffix. After publishing, you can copy the link, download a QR code and print a poster for your counter.

To change the address of a saved card, open the Share tab, then Advanced, and edit Sign-up page address. Use lowercase letters, numbers and hyphens, at least 3 characters and at most 80, starting with a letter or number. Each address belongs to one card across all companies. The URL updates as you type, and an unavailable address shows an error. The Share tab shows the saved Sign-up link and its QR code. Choose Copy to copy the saved link. Unsaved address changes do not change the link or QR code until you save. When the new address differs from the saved one, a warning reminds you that posters and QR codes you already printed, including the game QR, stop working after you save, and so does the old link. Grizzlee does not redirect the old address. Draft and archived cards show a closed message at that link. Deleting the card or company frees its address.

Everything to print is under Put this at your counter on the Share tab. To make a poster, choose Poster language, then Print poster. The poster shows your business name, a translated invitation to scan, the reward in one line, your card design and the sign-up QR code. The QR code opens the sign-up page in the poster's language. The printed address under it leaves out https://. Under Paper size, choose Letter or A5, then Print. Use the same paper size in the browser's print dialog. Choose Download QR code for a PNG of the sign-up QR code, or open More formats and choose Download QR as SVG. Both open the saved sign-up link.

When the saved game is on, the same section shows the Game QR code, with Download QR and Open game page. They appear once the card is active. Until then, a note asks you to publish the card. This QR opens the game rather than the sign-up page.

The sign-up and web card pages use your card's background and text colours, with your logo at the top. The sign-up page uses your business name as its heading, then the reward in one line, such as "Collect 10 stamps to get Free coffee." Points cards list their earning rules and catalog instead. A smaller card preview without balances keeps the form near the top on a phone. Customers enter their name and one phone number or email address, the same field as the game claim form. A 10-digit phone number uses country code +1. Other phone numbers need + and the country code. Birthday is optional. Customers pick a month and enter a day, with no year. When the card's Birthday automatic message is on, the form adds "We'll send you a treat on your birthday." A missing or invalid entry shows its message under that field, and the cursor moves to the first one. The marketing consent checkbox starts unticked. Grizzlee records consent with its time and the card's sign-up page as its source. The page picks one of your languages from the customer's browser, with your first language as the fallback. Adding ?lang=fr-CA or another of your languages to a sign-up, card or game link opens it in that language. When your company uses more than one language, these pages show a link for each one at the top. The game hides them once a play starts, so a prize isn't lost to a reload.

New customers see their web card immediately after submitting, without email verification. Customers who provide email also receive its private link by email. If the email or phone already belongs to a customer with a saved email address, Grizzlee sends a one-time recovery link to that saved address. The page then says the customer already has a card with your business. The rest of the message depends only on whether they entered an email or a phone number, so it does not reveal whether a phone match has email on file. If the customer has no saved email address, staff can give them their card at the counter using the scanner. The ordinary sign-up form does not create another pass for a matched customer.

Recovery links expire after 24 hours and work once. Opening one replaces every earlier private link to that card and opens a new link for the customer to save. For a customer joining another card from the same business, opening the recovery link creates the new pass. Repeat sign-ups leave the saved profile and marketing consent unchanged. Grizzlee allows one recovery email per saved address every 10 minutes across all your cards. If email is unavailable or delivery fails, existing card links keep working.

Use or delete a web card

Completed stamp cards stay full until the customer redeems the reward. If the customer has started the next card, a short line below the web-card artwork shows those stamps. The remaining-stamp count then describes the next card. For example, 12 stamps toward a 10-stamp reward shows one available reward, 2 stamps on the next card and 8 to go. Apple Wallet and Google Wallet show the same carryover line with the available rewards.

The web card shows your business name, the customer's first name, the reward in one line, their balance, available rewards and a barcode containing their card code. A line under the barcode says "Show this code at the counter." The bottom of the page asks the customer to bookmark it and not share the link. When Apple Wallet is connected, customers can choose Add to Apple Wallet to save their card. The pass shows your branding, balance, reward details and member barcode. Balance changes update the pass, and Wallet can show a lock-screen message when a reward becomes available. When Google Wallet is connected, choose Add to Google Wallet to save the same balance, stamp artwork, reward details and member barcode. Google updates the saved card after balance or design changes. It can send a notification when a new reward becomes available, up to three notifying attempts per card in 24 hours. Later reward messages appear without a notification. Google Wallet retries a reward message without another notification if delivery was uncertain. Cards show a wide barcode unless you pick a line barcode or a square QR code. The staff scanner reads all three.

Android phones can't open an Apple Wallet pass. If Apple Wallet is connected but Google Wallet isn't, Android customers don't see Add to Apple Wallet. The card asks them to bookmark the page or add it to their home screen instead. The browser tab names your business. A wrong or deleted card link, or a sign-up or game address that no longer exists, opens a short page in the customer's language asking them to get a new card from staff.

The back of the Wallet pass shows the reward rules and your business name. It contains no private web-card link. Recovering a web card replaces its private link without changing the saved Wallet pass.

Customers can choose Delete my card and confirm to erase their personal details and invalidate all their card links with this business. Anonymous balances and activity remain. Anyone holding the private link can use this action, so customers should keep it private.

A Wallet pass can appear on more than one device. Removing it records that device's removal and stops its updates. Deleting the web card stops downloads and updates on every device, but cannot erase a pass already saved on a customer's phone.

Live email delivery needs the configured Resend connection. In the local sandbox, sign-ups and web cards work, but Grizzlee sends no email. A repeat sandbox sign-up still hides the existing card link, leaves it working and creates no pass for a matched customer.

Test the card

The Apple Wallet preview and Google Wallet preview show the shared pass artwork without installing a card. These previews make no Wallet API calls. They appear only in the dashboard. In the local sandbox, for companies without a Wallet connection and for companies left off the server's Wallet company list, the customer's web card shows no button for that Wallet and no preview notice.

The preview uses the same calculations as real balances. It starts with a few sample stamps or points so you can see filled and empty slots. Preview language appears only if your company uses more than one language. Choose it to check your copy. Open Test the card below the pass to try earning. This group starts closed. Set Number of stamps and choose Add stamps, or set Number of visits and choose Add visits. When the card earns points on spending, type a purchase in Amount spent and choose Spend. Available rewards show a redemption button. Reset preview clears the trial balance. These actions never change a customer's balance.

Edit or archive

Open a pass from Cards to edit it. Changes to earning rules create a saved rule version. Design and text changes do not.

A stamp cycle keeps the target it started with, even if you change the card's rules. Every completed cycle unlocks a reward. Redeeming consumes that cycle's stamps and keeps extra stamps. New cycles use the current rules. Points catalog cost changes apply immediately. Saved earnings and redemptions keep their original rule versions.

Reversing an earning removes only the stamps that entry added to its cycles. If any of those cycles has been redeemed, reverse that redemption first, then reverse the earning.

Open the card actions menu, the button with three dots in the header, and choose Archive card. Choose Archive card again in the dialog to stop enrollment, earning and redemption. Archiving keeps the card and its history and cannot be undone.

Choose Delete card in the same menu, then Delete card in the dialog, to close the sign-up page and invalidate customer card links. Anonymous history stays in reports. Editors, admins and owners can manage cards. Viewers can read them and try the preview.

Locations and staff scanning

Open Loyalty, then Counter setup. Owners and admins manage locations, counter devices and staff here. With no active locations and no counter devices, a setup panel shows the order. Add a location, pair the counter tablet or phone, then optionally add staff. Add location is the first action. Set up a scanner stays disabled with "Add a location first" until an active location exists. The location and device tables appear after you add a location or create a device.

Choose Add location, enter Location name and choose Save. Address is optional. To put the shop on the map, open Map position on a phone or tablet while you are at the shop and choose Use this device's location. The browser asks for permission first. Enter coordinates by hand shows Latitude and Longitude if you'd rather type them. Remove map position clears both. The group starts closed, and its summary says whether a position is set. Apple Wallet and Google Wallet passes include up to 10 active locations with coordinates and use them to suggest the card when a customer is nearby. Wallet decides when to show that suggestion. The card's Near the shop automatic message sets the Apple Wallet text and can turn the suggestion off. Use Edit location to change these fields. Archive location asks you to confirm, then stops scanning at that location, including on its paired devices, and keeps its history. You can't restore an archived location.

Owners, admins and editors can choose Open scanner and use their normal Grizzlee account. Select Location before scanning. The browser remembers the last location for that company. These accounts can scan at any active location. Viewers and partners cannot scan. If the company has no active location, the scanner shows owners and admins an Add location button that opens Counter setup. Editors and paired devices see a message asking an owner or admin to add one.

Set up the counter device

Counter devices shows the scanner's full address with a copy button, and a QR code that opens it. On the counter phone or tablet, scan that QR code with the camera or type the address in the browser. After adding a location, an owner or admin chooses Set up a scanner. Enter Device name, select Location and choose Create pairing code. On the counter device, choose Pair device if the scanner is already showing. Enter the Pairing code, or read the displayed QR with the device camera. The code expires after 10 minutes and can be used once.

The paired device stays signed in for up to one year. It can scan only for its company and location. It has no dashboard access or server API key. Use the browser's Add to Home Screen action to install the scanner. It opens without the usual browser controls. Full screen also uses the browser's full-screen mode when available. Camera access needs HTTPS or a trusted local development address, and scanning needs a network connection.

The dashboard lists devices under Counter devices, with Last used. Choose Unpair and confirm to revoke a lost device or stop using it. The next scanner request is refused. Pairing it again needs a new code. Use another account or pair again clears the pairing cookie on that browser; Unpair is the remote revocation control.

Staff PINs

In the Staff section, choose Add staff member, enter Staff name and a 4-digit PIN, then choose Save. Active staff members need different PINs. Turn on Require a staff PIN on counter devices in the same section to ask for a PIN before a paired device can read or change customer cards. Staff need no email or Grizzlee account. Normal account scans continue to record the signed-in user.

On the counter device, enter the PIN and choose Start staff session. The session stays on that device until someone chooses Switch staff, the owner changes the PIN requirement, or the staff member is removed. Five incorrect PIN attempts lock PIN entry on that device for 15 minutes. Switching staff does not clear the lock.

Remove staff member asks you to confirm, then stops that person's PIN, ends their counter sessions and preserves their name on past activity. Deleting the company erases staff names, PIN hashes and staff names saved on past activity before the rest of the company is erased. To replace a PIN, remove the staff member and add them again. Leave the PIN requirement off when individual staff attribution is not needed.

Scan, earn and redeem

Choose Scan with camera, or enter the Card code and choose Find card. The scanner shows the card name and the customer's first name, then the balance with its unit, such as "4 of 10 stamps" or "120 points". The earn controls and available rewards come next. Give card sits below the rewards.

To give this customer another card or replace a lost private link, choose Give card. Under Card, choose one of your active cards, then choose Give card again. Ask the customer to scan the large QR code with their phone camera and save the link. The dialog also shows the link as text. Choose Close to return to the scanner.

If the customer already has that card, this replaces its private link. Earlier links stop working. Their balance, prizes, card code and saved Wallet pass stay the same. If they do not have that card, Grizzlee creates a pass for the same customer. Their profile and marketing consent stay unchanged. Staff need the customer's card code or an existing card to look them up first. You can find card codes in Customers. No email or SMS is needed.

On stamp cards, Number of stamps starts at Stamps per visit. Adjust it up to Most stamps staff can give at once, then choose Add stamps. The card then waits for Wait before the same card can get another stamp before it can get more, on every scanner. Undoing an earning does not clear that wait. A refused earn shows the time remaining. There is no override.

On points cards, enter the purchase amount in your company's currency, then choose Add points. Both 12.50 and 12,50 mean twelve currency units and fifty cents. Grizzlee adds one visit's points and calculates spend points with the card's rules. A card without spend earning adds only visit points.

Choose an available reward, check the confirmation and choose Confirm redemption. Choose Undo last action within 10 minutes to append a reversal of the latest action from this scanner. Grizzlee refuses an undo if the balance or stamp history no longer allows it and shows the reason. Then choose Scan next card.

The scanner saves each balance action in browser storage before sending it. Card handoff links stay only in the open dialog. If the result is uncertain, it shows that an earlier action needs confirmation and blocks new actions, even after a reload. Sign in again or enter your staff PIN if asked, then choose Retry action in the same browser. The retry uses the original action and location, so it cannot earn or redeem twice. The scanner clears the saved action only after success or a definite rejection of that action. Browser storage must be available before scanning.

Customers

Open Loyalty, then Customers. Type in Search by name, email, phone or card code and the list updates as you type. Card limits the list to one card. Each row is one customer's pass, with its balance, last visit, joined date and wallet status. Previous and Next move between pages. The wallet status column shows web-card availability and Apple Wallet when at least one device has an active registration. Downloading a pass alone does not mark it installed. Removing it from the last registered device removes its Apple Wallet status. Google Wallet appears after Google confirms a save and disappears after a removal callback. Requesting the Google save link alone does not mark it installed.

Open a row to see contact details, birthday and marketing consent, including its time and source. Each pass shows its balance, card code, wallet status and available rewards. Activity lists each balance change with its date, what happened, the change, and who recorded it and where. Notes appear under the entry. Removed staff keep their name on past entries. Older console entries may have no location. Activity has its own Previous and Next controls.

Editors, admins and owners can choose Adjust balance on an active card. Enter a positive or negative whole number under Balance change, add a required Note, then choose Adjust balance. Negative changes cannot exceed the balance. On stamp cards, additions complete existing cycles before starting new ones. Deductions remove stamps from the newest cycles first and keep the remaining cycles' original targets. Adjustments do not count as visits or stamps and points given in reports. Correct an adjustment with another adjustment.

The dialog saves each adjustment separately before sending it, so adjustments in different tabs keep their own operation IDs. If the response is uncertain, reopen Adjust balance on the same pass in the same browser and choose Retry action. Grizzlee reuses the saved amount, note and operation ID. A retry cannot apply that adjustment twice. If several adjustments remain pending, reopen the dialog to retry each one. Browser storage must be available.

Choose Delete customer and confirm to erase the customer's contact details, birthday, consent and activity notes. This invalidates every private card link for that customer with your business and stops Apple Wallet downloads and updates on all registered devices, as well as Google Wallet saves and updates. Anonymous balances and activity remain. Viewers can read customers and activity but cannot adjust balances or delete customers.

Owners and admins can choose Export CSV to download the full list matching the applied search and card filter, across all pages. The file has one row per pass and includes contact details, birthday, consent, consent time and consent source. Spreadsheet formula prefixes are escaped. Editors and viewers cannot export personal data.

Reports

Open Loyalty, then Reports. Choose Date range from Last 7 days, Last 30 days, Last 90 days or All time. Card and Location filter everything on the page. Days start at midnight in your browser's time zone, which the page names, and include today so far. The 7-day and 30-day ranges show days. The 90-day and all-time ranges show weeks starting Monday.

Four numbers come first: Visits, New customers, Rewards redeemed and Returning customers. Below them, Visits per day or Visits per week draws one bar per period. Open More detail for active customers, active cards, stamps or points given, wallet installs and removals, and the By card, By location and daily or weekly tables. Stamp numbers show only when you have a stamp card, and points numbers only when you have a points card.

New customers count distinct customers enrolled during the period. A customer who joins several cards counts once in the overall total and once under each card. Sign-ups have no saved location and appear under No location. Selecting a specific location excludes them.

Active customers have any activity in the period, including adjustments and reversals. Active cards are distinct customer passes with an unreversed earning, redemption or adjustment in the period. One customer with activity on two passes counts as two active cards. The count appears in totals, card and location tables, and each daily or weekly period. A later reversal excludes its original activity from this count. A visit is an earning operation that has not been reversed. Returning customers have at least two such visits in the period. Adjustments do not count as earnings or visits. Stamps given, points given and rewards redeemed exclude reversed entries, even if the reversal happened after the selected period. Totals keep anonymous activity after a customer is deleted and history for deleted cards. Daily and weekly customer and card counts describe each period separately, so adding them can count a customer or pass more than once.

Apple Wallet installs count the first registration of each pass on each device during the selected period. Reinstalling the same pass on the same device does not add another install. Apple Wallet removals count each unregistration in the period, including removals after a reinstall, invalid device registrations reported by Apple and registrations ended by customer or card deletion. A later reinstall does not remove earlier removals from stats. These events do not count as visits or active cards.

Wallet events have no recorded location and appear under No location. Selecting a specific location excludes them. The totals, card and location tables, and daily or weekly activity all include wallet counts. The sandbox uses the same definitions for saved registration history, but its preview creates no installs. Google Wallet installs count the first confirmed save per pass. Reinstalls do not add installs. Google Wallet removals count received removal transitions, and a later save restores the installed status. Google sends these confirmations on a best-effort basis, so its totals may miss events. Google counts passes rather than devices. Opening its save link and previewing a card do not count as installs.

Add a counter game

Save a card, then open its Game tab. Turn on Enable game to show the game settings. While the game is off, the tab shows only the switch and a short description. Choose Game type. The card must be active for customers to play. Each game uses the card colours and logo. Customers spin reels, pick a mystery card, choose a side for a coin toss, roll dice, scratch a card, answer a timed question or stop the clock. The wheel always has at least eight slices. The Rules sheet lists the actual prize odds. Slice sizes do not represent those odds.

Under Prizes, write each Prize name in every company language. With more than one language, each field names its language. Set Win chance as a percentage with up to two decimal places. Prizes per day limits how many of that prize can be won each local day. Leave it empty for no limit. Add prize adds another row and Remove prize removes one. The remaining chance appears as No prize. Total prize chances cannot exceed 100%. When a prize runs out for the local day, its chance becomes a loss. Unclaimed wins also use stock.

Open When prizes can be used. Its summary shows the current start and validity. Under Prize starts, choose Today or From the next visit. The second choice starts validity at midnight tomorrow. Set Valid for, days between 1 and 365. Saving uses your browser's time zone to define local days. Editing the game never changes a prize someone has already won.

For the stopwatch, set How close to 10 seconds counts as a win, in seconds. A value of 0.1 accepts a stop from 9.90 through 10.10 seconds. The clock shows its first three seconds, then hides until the customer stops it. The stopped time stays on screen. The customer's measured stop decides the win. The server also checks that the timing is plausible.

For the quiz, set Answer time, seconds and choose Add question. Write the question and every choice in each company language. Choose Correct answer. Each play gets one random question. A correct answer in time wins one of the prizes, picked by their chances with No prize left out. The stopwatch picks a prize the same way after a successful stop. If the picked prize has run out for the day, the customer gets nothing. The Rules sheet tells customers this.

Open Links after the game to enter any Instagram, TikTok or Google review links you want to offer. Its summary counts the links you set. Use HTTPS links. Customers see them after they keep a prize or after a loss. Following or leaving a review never unlocks a prize. Grizzlee counts link taps only.

Use Try preview to see the game in your card colours. The game QR code sits on the Share tab under Put this at your counter, with the sign-up poster. The QR image, Download QR and Open game page appear only after you save the game turned on and publish the card, because the game page does not open before that. Use Download QR for a PNG sign. Open game page opens the saved public game. This QR opens the game rather than the normal signup page.

The game page shows the first prize that can still be won under its title, such as "Win A coffee on us". Customers can play once per device per card each local day. A device that already played today sees Come back tomorrow as soon as the page opens. A loss shows "So close!" and a link to get the card, or to View my card when the device remembers the customer's card. The Rules sheet says when plays reset, such as "Plays reset at midnight (Toronto time)." A winner chooses Keep your prize. A remembered card needs one tap. Other customers enter their name, phone or email, and optional marketing consent. A 10-digit phone number uses country code +1. Other phone numbers need + and the country code. The form does not ask for a birthday. Grizzlee attaches the prize to the card that signup resolves to. Existing customers keep their card and receive the normal recovery email when email delivery is available. No private card link appears just because someone enters a saved email or phone number. Each card can claim one prize each local day.

The result and web card show each prize as a ticket with its dates. A Ready today badge marks usable prizes. The optional links panel stays hidden when no links are set. Keyboard users can reveal a scratch card with Reveal. Reduced motion replaces the game animations with a short fade and shows the Reveal button. Apple Wallet lists them on the back and shows a Prize field when one is usable today. Google Wallet lists them in a text section. Staff see prizes beside the normal rewards in the scanner. Future prizes show their start date and cannot be redeemed yet. Redeeming a prize leaves stamps and points unchanged. The existing confirmation, retry and undo actions also work for prizes. Undo restores the prize, with its original expiry date. Wallet updates include prize redemptions and undo, even when the balance stays the same.

Game stats appears at the bottom of the tab, below the setup, once the game has plays. It shows Plays and Prizes redeemed. Open More stats for wins by prize, taps on each link and customers who made a recorded visit within 30 days after their first play. Anonymous plays cannot count toward this return figure until Grizzlee can associate them with a card. Deleting a customer removes the card links, claim credentials and device identifiers from their game records. Anonymous game totals, consumed daily stock and balance history remain. Detached prizes disappear from customer cards and the scanner and cannot be claimed or redeemed. Detached plays no longer count toward the returning-customer figure.

For a returning customer who enters a phone number, the game can attach the prize to their existing card before staff give them its link. Staff look up the customer, choose Give card and select the card used by the game. The customer sees the saved prize when they open the card. The handoff keeps the prize's original dates.

Messages

Open Loyalty, then Messages. The page lists the Automatic messages of every card, then Sent messages. Editors, admins and owners can choose Send a message to write one. Viewers can read both lists.

Write a plain-text Message in every company language, up to 200 characters each. Choose one active Card or All cards. Choose Send now, or choose Schedule and enter Local date and time. The form shows your browser's time zone. Grizzlee stores the time in UTC.

Choose Preview recipients to see the recipient count and how many customers lack marketing consent. Check the message, card and time, then confirm with Send now or Schedule. Grizzlee checks recipients and consent when it sends, so scheduled counts can change. Only customers with marketing consent and a live pass on an active card receive the message. Deleted cards and deleted customers receive nothing. A customer with several target passes receives the message on each pass. Choose Cancel beside a scheduled message to stop it before sending starts.

Sends are unlimited. Notifications are limited. Google Wallet allows at most three notifying updates per customer card in a rolling 24 hours. Reward-ready alerts and merchant messages share that allowance. Later messages still appear on the card without a notification. Apple Wallet shows only the latest message in a Latest news field on the back of the pass. Its lock-screen notices are best-effort, and several changes can produce only the newest notice. Web-only cards show the latest message and its date without a notification.

The history includes the newest 200 messages and every scheduled or sending message, newest first. Older scheduled messages keep their Cancel control. Each row lists the date, message, card, Sent to and status. Under the status, a warning line counts deliveries that failed, and a muted line counts customers left out without marketing consent. Sent to counts passes. An update counts as delivered when the Wallet update succeeded or a web-only card shows the message. That does not confirm that a person saw a notification. A pass saved in both wallets counts once and completes after both updates succeed. A failed update makes that pass's delivery fail. Delivery retries do not create another recipient row. Deleting a card or a customer preserves completed delivery counts. Erasure removes their message history from delivery records and queued work. Anonymous totals remain, and deliveries stopped before completion count as failed.

In the sandbox, messages appear on web cards and count as delivered. No Wallet API calls or notifications occur. Scheduled previews run when the sandbox next handles a request at or after the selected time.

Automatic messages

Messages lists every card's automatic messages with an on or off badge. Choose a row to open that card's Automatic messages tab. In the card editor, save a card, then open the Automatic messages tab. Near the shop starts on and the four messages that send start off. Each one is a row with its name, when it applies and an on/off switch. The four that send also show how many they sent in the last 30 days. Turn on the ones you want. Choose a row to open it, edit Message in every company language, then choose Save. Each message allows 200 plain-text characters per language. Saving uses your browser's time zone for local dates. Text changes apply only to future sends.

• Welcome sends once on the next worker run after sign-up. Only passes created after you enabled it qualify. Turning it on does not message existing customers. It starts off because the web card already confirms sign-up.
• Birthday sends on the customer's saved birthday month and day in the saved time zone. Customers without a birthday are skipped. February 29 birthdays use February 28 in years without February 29. Birthday bonus, stamps or Birthday bonus, points adds a whole number from 0 to 1000 with the message. Zero adds nothing. Activity labels this entry Birthday bonus. It can complete stamp cycles and unlock rewards, but does not count as a visit or an adjustment.
• We miss you sends when the last unreversed visit is at least Days since last visit local days old. The default is 30 days, with a range of 7 to 365. It sends once for that visit. A new visit starts a new waiting period. Customers without a visit are skipped.
• Reward reminder sends once for each reward that has stayed available and unredeemed for Days with an unredeemed reward local days. The default is 7 days, with a range of 1 to 365. Redeeming a reward stops its pending reminder, even if Wallet delivery is waiting to retry. Redeeming a stamp reward removes that cycle from consideration. Points rewards use each threshold crossing and start a new period after redemption if another reward is still available. Undo restores the original reward's reminder history. This reminder does not expire points or rewards.

Near the shop works differently. It sends nothing. It sets the text Apple Wallet shows on the lock screen when the pass is relevant near one of your locations with a map position. Wallet decides when that is, and the row shows no send count. Google Wallet shows its own nearby notification and does not use your text. The text allows 80 plain-text characters per language, and Apple Wallet may cut longer text short. It appears on every saved pass, whatever the customer's marketing consent. Saving updates passes already in Apple Wallet and Google Wallet. Turning it off removes your locations from passes, so neither wallet suggests the card nearby. If no active location has a map position, the row says so and shows a Go to Counter setup link.

Only customers with marketing consent and a live pass on an active card qualify for the other four. Birthday bonuses require that same consent and arrive only with the birthday message. Reward-ready alerts remain transactional and separate from these automations.

The worker checks due passes in batches and processes scheduled messages and queued deliveries between batches. It checks each pass once per local day and again after card edits or ledger activity. New sign-ups qualify on the next worker run. Retries and worker restarts reuse the same send keys. If one customer's automation fails, its changes roll back and other customers still receive their messages. In the sandbox, the next request runs due automations and updates web cards without calling Wallet providers. A failed automation does not block the requested action.

Automatic messages use the same Wallet notification limits as messages. Google Wallet allows three notifications per pass in a rolling 24 hours, shared with manual messages and reward-ready alerts. When the allowance is spent, the message still updates the pass silently. Apple Wallet notices are best-effort. Web-only cards show the latest message without a notification.

The four rows that send show how many messages they sent in the last 30 days. Open Birthday or We miss you to see Customers who visited within 14 days. This counts distinct customers who made an unreversed visit on that card after one of those sends. Recent sends have not had the full 14 days yet. Sends count selected passes, even if a provider later fails. Erasure keeps anonymous send totals and removes the customer from return counts. It removes their automation history links and stops queued messages and birthday bonus Wallet updates. Completed delivery counts and bonus ledger entries remain. Automatic sends appear here and stay out of the manual Messages history.