> 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/affiliate-program/settings.md).

# Program Settings

Set when commission is earned, when it is revoked, and how partners get paid.

Affiliate settings decide the mechanics of your program: when a commission is earned, when it's taken back, how partners get paid, and how the program identifies itself. Getting these right before you recruit matters — an affiliate who earns a commission but can't be paid, or whose commission vanishes without explanation, stops promoting.

Open **Affiliate → Settings**. It has five tabs: **General**, **Automation**, **Order Settings**, **Payment**, and **Integration**.

> **Best practice:** Decide your commission triggers before you recruit, not after. Changing "when commission is earned" once affiliates are live changes what they were promised mid-flight — and they will notice.

### General

Two identity settings:

* **Contact email** — the address affiliates use to reach you. It appears in the portal and in emails.
* **Affiliate login page** — the portal URL, with a customizable subpath. Bloop checks availability as you type and tells you if the subpath is already taken. See [portal link](/account-and-settings/portal-link.md).

### Automation

How much of the program runs without you:

| Setting                | Options                | What it means                                                                                                           |
| ---------------------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Affiliate approval     | Manually · Immediately | Whether a new registration waits for your review or is approved on signup                                               |
| Order approval         | Manually · Immediately | Whether sales land as pending in the [Sales](/affiliate-program/management/sales.md) tab or are approved as they arrive |
| Assign tags on Shopify | Customer · Order       | Tag the customers and orders affiliates bring, so you can segment them in Shopify                                       |

**Immediate order approval is the setting to think hardest about.** It removes your review step entirely — including the chance to catch a return before you've committed the commission. Use it only if your Order Settings revoke rules cover you, and read [when to approve and when to reject](/affiliate-program/management/sales.md#when-to-approve-and-when-to-reject) first.

### Order Settings

This tab controls **when an affiliate earns commission** and **what happens to it when the order goes away**.

#### When commission is granted

| Option             | Commission is created when | Suits                                                                                            |
| ------------------ | -------------------------- | ------------------------------------------------------------------------------------------------ |
| **Paid** (default) | The order is paid          | Most stores — the affiliate's work is done at checkout                                           |
| **Fulfilled**      | The order is fulfilled     | Pre-orders, made-to-order, long lead times, or anywhere a paid order still commonly doesn't ship |

Only one trigger fires per order, so a sale is never created twice.

#### When commission is revoked

| Option                             | Revokes on        |
| ---------------------------------- | ----------------- |
| **Canceled or refunded** (default) | Either            |
| **Canceled**                       | Cancellation only |
| **Refunded**                       | Refund only       |

A revoked commission is set to **rejected**, and the affiliate sees the reason on their Commissions page in the portal — "Commission revoked because the order was cancelled" or "...refunded". That transparency is the point: a commission that silently disappears generates a support ticket, an explained one doesn't.

Three rules decide whether a revoke actually happens:

* **Partial refunds are ignored.** Only a fully refunded order revokes the commission — refunding one line of a five-line order doesn't.
* **An already-paid commission is never revoked.** Once a sale is in a payout, a later cancellation won't claw it back. This is the real reason to approve and pay *after* your return window rather than before.
* **An already-rejected sale stays rejected.** The reason isn't overwritten.

If you later move a revoked sale back to approved or pending yourself, the revoke reason is cleared — the affiliate stops seeing an explanation for something that's no longer true.

### Payment

Payment methods define how you pay affiliates and what details you collect from them.

Bloop ships with four methods:

| Method        | Fields collected                                                                        |
| ------------- | --------------------------------------------------------------------------------------- |
| Bank transfer | Bank name, account name, account number (required); agency code and BIC code (optional) |
| Paypal        | Email (required)                                                                        |
| Debit cash    | Name, debit card number (required)                                                      |
| Google pay    | Email (required)                                                                        |

For each method you can **enable or disable** it — only enabled methods are offered to affiliates — and **edit the fields** it collects: each field's label, type (Text or Email), and whether it's required. **Add more payments** creates a method of your own: give it a payment name and define its fields.

Details an affiliate enters are stored on their profile and shown when you [pay them out](/affiliate-program/management/payouts.md). An affiliate with no payment method on file **cannot be paid** — the payout button is disabled until they fill one in.

#### Choosing which methods to offer

More payout options means more decisions for the affiliate and more reconciliation for you. Enable the one or two that cover your partners and disable the rest.

| Method        | Best for                                                 | When to offer it                                                       | Friction to watch                                                    |
| ------------- | -------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Paypal        | Individual creators, influencers, international partners | Most creator-led programs — fast, familiar, and crosses borders easily | Requires a PayPal account; fees may apply on their end               |
| Bank transfer | Businesses, agencies, higher-volume or local partners    | Larger or recurring payouts and partners who prefer direct deposit     | Most fields to collect and verify; details vary by country           |
| Google pay    | Partners in the Google Pay ecosystem                     | A lightweight email-based option alongside PayPal                      | Narrower availability and reach than PayPal                          |
| Debit cash    | Programs that pay directly to a card                     | Niche cases where a card payout is how you settle                      | Card-number fields are sensitive; only enable if you actually use it |

A creator-led program can often run on Paypal alone; a B2B or agency program leans on bank transfer. Offering all four forces every affiliate to choose and leaves you reconciling four payout flows for no benefit.

#### Editing a method's fields

Two principles keep payouts smooth:

* **Require only what you can't pay without.** For bank transfer you genuinely need account name and number; agency code or BIC may be optional depending on the country. Marking a "nice to have" as required delays the partner from finishing their profile — and an unfinished profile is an affiliate you can't pay.
* **Label fields the way the partner's bank or wallet does.** Matching labels mean a partner copying details from their bank app won't second-guess which number goes where.

#### A worked example: a creator program's payout setup

For a program of mostly individual creators with a handful of agencies: enable **Paypal** (its one required field covers most creators), enable **Bank transfer** for agencies (require bank name, account name, account number; leave agency code and BIC optional), and disable Debit cash and Google pay so no affiliate sees a method you can't pay through. A creator fills in one field, an agency fills in three, and you reconcile exactly two payout flows — see [Affiliate payouts](/affiliate-program/management/payouts.md).

### Integration

Shortcuts to the same Klaviyo and Mailchimp connections the referral program uses, with their current status. Setting either one up is covered in [Klaviyo](/referral-program/integrations/klaviyo.md) and [Mailchimp](/referral-program/integrations/mailchimp.md).

### Setup guide

A checklist on the Settings page tracks what's left before your program is ready: finish the campaign, set up the signup form, customize the portal, set up email notifications, configure payout methods, and test the flow. Each step links straight to the screen that completes it, and the header shows how many of the tasks are done. Dismiss it once you're live.

### Email notifications

Bloop sends affiliates transactional emails at key moments — registration (pending), approval or decline, sale approval or decline, coupon assignment, and payout. Default templates are created during setup.

Some templates ship **disabled** — the "declined" and "denied" templates, and both owner-facing notifications — so they won't fire until you turn them on. If you want alerts on new registrations, enable that owner notification and set a recipient. The full list of types, triggers, and default on/off states is in [Affiliate email notifications](/affiliate-program/emails.md).

#### Send a test email

Before launching, send yourself a test of any affiliate email to check wording and formatting:

1. Open the email you want to test.
2. Enter one or more recipient addresses.
3. Send the test.

Bloop renders the template with your store's details and delivers it to the addresses you entered. Test sends are rate-limited, so send in small batches.

Test every enabled email — especially the approval and payout messages, since those are what partners read most carefully. A test send is the only way to catch an unfilled variable or broken button before a real partner sees it.

### Common mistakes to avoid

* **Approving orders immediately while paying out weekly.** Immediate approval plus a fast payout means a cancelled order's commission is already paid and can't be revoked.
* **Offering every payment method.** Enable the one or two that fit your partners; disable the rest.
* **Over-requiring payout fields.** Require only what you need to complete a payment. Optional details stall a partner mid-setup — and an unfinished profile blocks the payout.
* **Skipping test sends.** A partner receiving an email with a placeholder still showing is avoidable. Test every active template first.

### When to revisit these settings

* **You start selling pre-orders or made-to-order items** → switch the grant trigger to **Fulfilled**.
* **Refund-driven clawbacks start biting** → check whether you're paying out before your return window closes; revocation can't touch a paid commission.
* **Your partner mix shifts** (more creators or more agencies) → revisit which payment methods are enabled.
* **You expand to new countries** → bank-transfer fields may need adjusting (agency code, BIC) for partners' regions.
* **You change your brand voice or program name** → re-edit the email templates so messages still sound like you.

### Related

* [Affiliate sales tracking](/affiliate-program/management/sales.md) — where the grant and revoke rules show up.
* [Affiliate payouts](/affiliate-program/management/payouts.md) — where payment methods are used.
* [Affiliate email notifications](/affiliate-program/emails.md) — every email type, variables, and editing.
* [Managing affiliates](/affiliate-program/management/affiliates.md) — registration and statuses that trigger emails.
* [Recruiting affiliates](/best-practices/recruiting-affiliates.md) — getting the right partners into a program that's ready to pay them.


---

# 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/affiliate-program/settings.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.