Rewards

A reward is what a member gets for taking part. Most rewards come from completing a quest; members can also buy some with their points. For example:

• 50 XP for answering a quiz.
• An "OG" badge for joining in the first week.
• A Discord role that opens a members-only channel.
• A tote bag collected at your booth, or bought for 500 points.

A quest's rewards go to the member who completes it. A referral program can reward both the inviter and the friend they invited.

Reward kinds

Offers sell tier rewards. Referral programs and leaderboard prizes pay points and tier rewards. Badges, group memberships and Discord roles come only from quests (and reviewers, for badges): to give one for a referral or a leaderboard place, reward it from a quest instead. See referrals before choosing which one owns an award.

Match tiered rewards in your app

Reads name a tiered reward by its stored ID, not the key you gave defineTieredReward. An entitlement's reward.id is reward_… even when the source says key: "tote".

1. Read the project's tiered rewards with relay.tieredRewards.list(), or useTieredRewards() in React, whose data holds the list. Each entry has id and key.
2. Find your reward by key, then compare IDs: rewards.find((r) => r.key === "tote")?.id.
3. Show the reward's title from the read itself, never its ID.

Quest views already carry the key: a tier reward has reward: { id, key, title } and the tier it grants.

Retire a tiered reward

When a tiered reward is done, such as merch from a finished campaign, archive it so nothing new hands it out. In test, open Settings → Resources, choose Archive tiered reward on it and give a reason, then promote to live.

• Nothing new can grant it. A deploy that would make a quest, offer or leaderboard prize grant it fails until you unarchive it or remove it from that code.
• What already grants it keeps working. A quest, offer or prize that granted it before you archived it keeps granting it, a new version of it included. To stop those grants too, archive them.
• Members keep what they earned. Rewards they earned can still be handed over, and their apps still show them.
• Console stops listing it. Rewards leaves it out of its rewards, but still shows the ones members earned.
• Its key stays taken. A new tiered reward with the same key must have the same definition. Give a replacement its own key.

Unarchive tiered reward brings it back. Badge and group membership rewards aren't listed here: archive the badge or group instead.

Completion and delivery

Completing a quest and receiving its reward are two separate moments. Points arrive with the completion. A Discord role or a tote bag can take longer.

• Discord roles arrive on their own. Domino records the role request with the completion, then keeps trying to grant it. It always goes to the Discord account and server the member had when they earned it. If you revoke the completion, Domino removes the role, unless something else still earns it. Domino only removes roles it granted itself; roles members already had, or that you chose to keep, stay.
• Physical rewards wait for pickup. Earning a tote bag and handing it over are separate steps. A collection pass lets staff look the member up and start the pickup; confirming they took it is a separate action.
• Digital rewards can be collected at once. With automatic fulfillment, Domino marks the reward collected the moment it's granted, with no staff step.
• Buying with points is all or nothing. Domino holds one unit of stock and the member's points before granting the reward. A failed purchase spends nothing and takes no stock.
• Promised rewards stay fixed. Publishing new quest rules does not replace the reward an existing attempt was promised. Keep reward identity stable when updating source.

See Discord role rewards for authoring and the participant API for progress and delivery reads.

Offers

An offer lets members spend points on a reward, like a shop shelf. You set the price, how many there are, and how many one member can buy. Members see whether an offer is available, paused, sold out, or already at their limit.

• Each purchase grants one reward. Rewards that need staff wait for pickup; automatic ones are collected straight away.
• Pause without editing. You can pause an offer at any time without changing it.
• Retire an offer by archiving it. In test, choose Archive offer on its card in Rewards or in Settings → Resources, then promote. Members stop seeing it and can't buy it. Its past purchases stay as they are and can still be canceled. Console labels it Archived, and Unarchive offer brings it back. Deleting an offer from your code doesn't archive it.
• Sell only to some members. An offer can require what quests can: a completed quest, a minimum balance, or membership of a group. Members who don't qualify still see the offer, along with what they're missing, and can't buy it until they meet every requirement. Console shows an offer's requirements on its card. The loyalty starter works this way: its members-only offer unlocks once a quest's group membership reward adds the member to its members' group.
• Cancel with a refund. Canceling a fulfilled purchase refunds the points the member paid, returns one unit to stock, and voids the reward. Canceled purchases stay visible in Console.

Keep an uncertain redemption pending

An offer redemption spends points and consumes stock once for its action ID. If the answer is lost, a new ID represents another purchase. Keep the original ID and payload until the result is known. relay.action() and useRedeemOffer() retain them and offer a replay-safe retry; the helper is kept in memory, so recovery across reloads needs a persisted key. See Retry after an uncertain answer.

Correct a tiered reward

A tier reward moves from available to handing-over when staff start a handover, and to collected when they confirm it. Your team can undo each step, void the reward, or restore a voided one, with a reason. Each correction acts on the version the operator saw, so a reward that changed in the meantime is refused until they reload it.

Needs recovery. If you revoke a completion after the member already collected its reward, Console shows Needs recovery in Rewards and explains why in the reward and member details. The item still counts as collected until you resolve it. Get the item back, or fix a mistaken collection, then choose Correct collection with a reason. The correction either voids the reward or makes the tier the member still earned available, and records it in history.

A voided reward stays in the member's rewards with status void and the time it was voided. If a quest grants the member the same reward again, it becomes available as a fresh grant at that quest's tier. A voided referral reward stays void until you restore it.

Restore reward undoes a void your team made. It can't undo a void that something else made, so the reward can't drift from the cause:

• A revoked completion voided it. Restore the completion instead.
• A completion revoked after the void earned it. Restoring gives back the tier another accepted completion still earns. If none does, restore the completion instead.
• Canceling an offer redemption voided it. The redemption's price went back to the member, so the reward stays void.
• A referral reward voided before restore existed. Its referral review wasn't kept, so it stays void.

In Console, open the member and find the reward under Earned rewards. A project with in-person pickup also lists every earned reward in the Earned rewards tab on Rewards. Audit history lists each correction under Rewards with its reason and who made it. These are corrections to member state, so they work in live too.

Inventory corrections and retirement

Your team can rename a stock item, correct how many are left, archive it and unarchive it. Use Console Rewards → Pickup & stock → Inventory items, including stock owned by offers, and choose Rename item, Correct stock, Archive item or Unarchive item. A project with no rewards handed over in person has no tabs, and lists Inventory items on Rewards itself.

• Stock already promised stays. A correction cannot remove units already reserved or redeemed. Pickup labels already assigned stay the same when you rename the item.
• Archive only unused items. You can't archive an item while an offer or pickup uses it, including a paused or archived offer, so an item behind an offer stays as it is; archive the offer instead. For pickups, move the pickup to another item first. Existing handovers and their history stay available.
• Live takes stock corrections only. Creating, renaming, archiving and restoring an item, and pickup setup, are definition changes, so they reach live by promotion from test.

Participant reward reads

Your app can show members what they earned, whether it's waiting for pickup, collected, or voided, and whether a Discord role has arrived.

Badges

A badge marks an achievement, like "Early supporter" or "Attended the meetup". It has a name, a description and an image. A member holds each badge once, even when several quests award it. Badges have no built-in levels: if you want bronze, silver and gold, your app builds them from badge keys, points or ledgers.

Manage the catalog in Console Rewards. Archive badge and Unarchive badge sit beside each badge and ask for a reason. In a Console quest's editor, choose Add badge. Reviewers award and revoke badges in the member drawer. Live badges come from a promotion from test; awards and revokes work in live. A member you erased keeps their badges, and neither works for them.

Group membership

A group membership reward adds the member to a group when they complete the quest. It's the way to run an approved program: members apply through a quest your team reviews, approval puts them in the "Approved creators" group, and the program's quests are open only to that group. Approving the application is the one step that lets someone in.

import { defineGroup, groupMembership } from "@domino-sdk/relay/authoring";

export const creators = defineGroup({ key: "approved-creators", title: "Approved creators" });

// In the application quest's definition:
const rewards = [groupMembership(creators)];