> 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/commission-structure.md).

# Commission Structure

Your commission structure decides how hard partners work to promote you and how much margin you keep on every sale they drive. The short answer: anchor the rate to your **profit margin**, not a round number; pick the commission **model** that matches your average order and product range; and start low so you can reward proven performers rather than cut everyone later. This article works through those choices, then links the Bloop campaign settings that implement them.

In Bloop every affiliate belongs to exactly one **campaign**, and the campaign holds the structure. Get it right once and the program scales cleanly; get it wrong and you either repel good affiliates or quietly lose money on every order.

### Anchor the rate to margin

Before choosing a number, decide what share of the profit on an affiliate-driven order you are willing to give away, then back into the rate from there. A 20% commission on a 60%-margin candle is healthy; the same 20% on a 12%-margin electronics order erases your profit. When unsure, start lower — it is far easier to raise a rate for a top performer than to cut one across the board.

### Pick the model that fits your store

The right model follows your margins, your average order value, and your product range.

| Store profile               | Margin                | Order pattern                | Suggested model                              | Why                                                              |
| --------------------------- | --------------------- | ---------------------------- | -------------------------------------------- | ---------------------------------------------------------------- |
| Fashion & apparel           | Healthy (50–60%)      | Mid-value, varied baskets    | Percentage                                   | Scales fairly with order size without per-item math              |
| Beauty & cosmetics          | High, repeat          | Small, frequent              | Percentage with a cap                        | Keeps rates attractive while protecting margin on bulk orders    |
| Electronics & high-ticket   | Thin (10–20%)         | Infrequent, large            | Flat per order                               | A fixed amount keeps payout predictable on thin margins          |
| Single hero product / DTC   | Known per-unit profit | One product, varied quantity | Flat per item                                | Pays exactly per unit, so cost per sale is predictable           |
| Subscription                | Recurring value       | First order, then renewals   | Flat per order on the first sale             | A fixed bounty avoids over-paying on a low first-cycle price     |
| Mixed catalog               | Ranges widely         | Anything                     | Percentage base + product-specific overrides | Safe base rate everywhere, richer rates only where margin allows |
| High-value creator partners | Any                   | High volume                  | Tiered (advance)                             | Bigger orders earn a higher rate, motivating larger baskets      |

The pattern: **percentage** suits healthy, variable margins; **flat per order** protects thin or high-ticket margins; **flat per item** fits predictable per-unit profit; and **tiered** or **product-specific** rates let you reward selectively once a base program works.

### Build in guardrails before you scale

A structure that scales needs limits, not just rates.

* **Commission cap.** A maximum per order protects margin on unusually large baskets and keeps payouts predictable. It pairs especially well with a percentage model, which would otherwise scale without limit.
* **Exclude what is not profit.** Commission on the order's product revenue, and consider excluding shipping and tax — you rarely want to pay on money that never lands as margin.
* **Attribution window.** A longer cookie suits considered, slower purchases; a shorter one suits impulse buys. Match it to how long your customers take to decide.

### Use campaigns to segment, not to complicate

You can run multiple campaigns and assign each affiliate to one. The cleanest way to scale is a standard campaign for everyone and a higher-rate campaign for proven top performers, rather than negotiating one-off deals. A short-term, richer campaign for a product launch is another common, contained pattern.

### Set it up in Bloop

* Configure the model, cap, exclusions, and cookie in [Affiliate campaigns and commissions](/affiliate-program/campaigns.md).
* Pay against approved balances in [Affiliate payouts](/affiliate-program/payouts.md).
* For the full reasoning on setting a number, see [how to set affiliate commission rates](https://bloop.plus/blog/referral-commission/).

### Related

* [Best practices: recruiting and approving affiliates](/best-practices/recruiting-affiliates.md)
* [Affiliate campaigns and commissions](/affiliate-program/campaigns.md)
* [How to set affiliate commission rates](https://bloop.plus/blog/referral-commission/)


---

# 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/commission-structure.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.
