> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/best-practices/choosing-rewards.md).

# Choosing Rewards

The reward you offer is the single biggest factor in whether your referral program spreads, so decide it on purpose rather than copying a competitor. The short answer: match the reward **type** to how often your customers buy, and set the combined value **below your profit on a referred order** so every successful referral stays profitable. This article walks through how to make that decision for your store, then points you to the Bloop settings that put it live.

A Bloop referral has two rewards, and they do different jobs. The **referee reward** lowers the barrier for a new customer to try you, so it has to feel worth acting on. The **referrer reward** thanks an existing customer for the introduction, so it has to feel worth the small social risk of recommending you. Tuning both is the work; this page is about the strategy behind the numbers you eventually type into the [rewards settings](/referral-program/rewards.md).

### Start from your repeat-purchase pattern

The reward type should follow how customers buy from you, not what looks generous on a landing page.

* **Store credit** pulls a customer back for another order, so it suits stores people buy from often. It also keeps the reward inside your store, which protects cash.
* **A percentage or fixed discount** carries more weight when purchases are rare or one-off, because credit toward a "someday" order feels weak.
* **Cash** is the strongest signal for high-ticket or infrequent purchases, where neither credit nor a discount feels worth a recommendation. It is the only type Bloop tracks but does not settle automatically, so plan to process it by hand.

### Recommended rewards by industry

There is no universal right answer. Use the table as a starting point, then refine against your own margins.

| Industry                  | Buying pattern             | Suggested referrer reward            | Suggested referee reward                   |
| ------------------------- | -------------------------- | ------------------------------------ | ------------------------------------------ |
| Fashion & apparel         | Frequent, impulse-driven   | Store credit toward the next order   | Percentage off the first order             |
| Subscription              | Recurring, retention-led   | Store credit or a free billing cycle | Discount on the first cycle                |
| Beauty & cosmetics        | Repeat, habit-forming      | Store credit to encourage restocking | Fixed amount off a trial-sized first order |
| Electronics & high-ticket | Infrequent, considered     | Cash or a meaningful fixed amount    | Fixed amount off the first purchase        |
| Food & beverage           | Low margin, high frequency | Modest store credit                  | Small percentage or a free add-on          |

The thread running through every row: high-frequency stores benefit from store credit because it loops customers back, while infrequent high-ticket stores often need cash or a sizeable fixed amount to feel worth a recommendation.

### Set a value you cannot lose money on

The safe rule is simple: the **referrer reward plus the referee reward** should stay below the profit you make on a referred order. A referral that costs you more than it earns is a slow leak, even when conversion looks healthy.

* Estimate the gross profit on a typical first order from a new customer.
* Subtract the referee discount, which comes off that first order directly.
* Whatever profit remains is your ceiling for the referrer reward.

If that ceiling is uncomfortably tight, lean on store credit for the referrer side — it is redeemed against a future order, so its real cost is your margin on that order, not its face value.

### Decide where the reward applies

A reward only works if it is easy to use. In Bloop, discount and store-credit rewards settle automatically inside Shopify, while cash is tracked for you to pay out manually. If predictable, hands-off operation matters more than maximum motivation, prefer the automatic types and reserve cash for high-ticket programs where it genuinely moves the needle.

### Set it up in Bloop

Once you have chosen a type and value:

* Configure both sides in [Set up referrer and referee rewards](/referral-program/rewards.md) — reward type, value, minimum requirements, expiry, and the review period.
* Decide how referrers share that reward in [Referral methods](/referral-program/referral-methods.md).
* For worked examples of incentive ideas across stores, see [the best referral incentives](https://bloop.plus/blog/best-referral-incentives/).

### Related

* [Best practices: designing your referral offer](/best-practices/designing-your-offer.md)
* [Set up referrer and referee rewards](/referral-program/rewards.md)
* [The best referral incentives](https://bloop.plus/blog/best-referral-incentives/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloop.plus/best-practices/choosing-rewards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
