> 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/paying-affiliates.md).

# Paying Affiliates

Paying on time is the quiet thing that keeps affiliates loyal. The short answer: review and approve sales on a fixed rhythm tied to your refund window, pay on a predictable schedule with a small minimum threshold, and record every payout the moment you send it so your balances stay honest. This article explains how to build that discipline, then links the Bloop tools that support it.

Partners promote stores that pay reliably and drop the ones that make them chase commissions. In Bloop the mechanics are deliberately simple: you only ever pay against **approved** sales, so a payout is just turning a balance you already owe into a recorded payment. Bloop never moves money itself — the reliability comes from your process.

### Approve before you pay

Every affiliate-driven order starts as a claim, not a payment. The gap between the two is your chance to catch cancelled orders, returns, and fraud before money leaves your account.

* Review sales on a rhythm aligned with your refund window — approving weekly, after the typical return period, means you rarely pay on an order that later comes back.
* Skim for anything unusual, like a sudden spike from one affiliate or oddly large baskets, before bulk-approving the rest.
* Reject cancelled or returned orders promptly so balances stay accurate.

Do this in the [Sales review](/affiliate-program/sales.md) tab.

### Set a schedule and a threshold, then keep them

Reliability beats generosity here. A fixed cadence tells affiliates exactly when to expect payment and keeps your accounting tidy.

| Choice            | Recommendation                                                                      | Why                                                  |
| ----------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------- |
| Cadence           | A fixed interval — for example monthly, once sales have cleared their review period | Predictability is what keeps affiliates loyal        |
| Minimum threshold | A small minimum balance before you pay out                                          | Avoids the overhead of tiny transfers                |
| Timing vs refunds | Pay after the refund window has passed                                              | Stops you clawing back commission on returned orders |

Publish your schedule and threshold to affiliates up front so there are no surprises.

### Record every payout immediately

Bloop's payouts area has two views: **Approved**, each affiliate's outstanding balance (what you currently owe), and **Paid**, a record of everything you have completed. The Approved view is only trustworthy if you record payouts the moment you send them — otherwise it overstates what you owe and you risk paying twice. Make recording the payout the last step of every payment, not a later cleanup task.

### Keep clean records for accounting

Export your payout history regularly so your bookkeeping matches what affiliates received. Clean records also make it easy to answer a partner's "have I been paid?" question without digging, which reinforces the reliability that keeps them promoting.

### Set it up in Bloop

* Approve sales in [Affiliate sales review](/affiliate-program/sales.md).
* Pay and record in [Affiliate payouts](/affiliate-program/payouts.md).
* Set the commission those payouts draw on in [Best practices: a commission structure that scales](/best-practices/commission-structure.md).

### Related

* [Best practices: a commission structure that scales](/best-practices/commission-structure.md)
* [Best practices: recruiting and approving affiliates](/best-practices/recruiting-affiliates.md)
* [Affiliate payouts](/affiliate-program/payouts.md)


---

# 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/paying-affiliates.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.