
Affiliate platforms: questions to ask before you migrate (SaaS)
A practical checklist for migrating affiliate platforms in SaaS: what to export, how to compare ledgers, how to handle refunds and clawbacks, and the safest cutover plan.
Read articleTiers are an ops tool, not a hype tactic: keep payouts predictable and easy to audit

Affiliate tiers (e.g., 20% until you send $1,000, then 25%) sound like an easy way to ‘motivate’ partners. Sometimes they are. But in SaaS, tiers often become an accounting argument: what counts, when it counts, what happens on refunds, and whether the partner is paid at the higher rate retroactively.
This guide is a practical decision framework. The goal is not to build a complicated commission system — it’s to create a tier structure you can explain in one paragraph and pay out without manual heroics.
A tier is just a rule that changes commission terms based on performance or partner type. It can change your rate (20% → 25%), your approval speed (30-day hold → 14-day hold), or your payout cadence (monthly → biweekly).
The mistake is treating tiers like a marketing gimmick. In reality, tiers are a contract + a calculation method — and your payout ledger has to support them.
If you’re early, a better default is: one simple base rate + occasional manual bonuses for exceptional partners. Bonuses are flexible; tiers are policies.
| Model | How it works | When it fits | Main risk |
|---|---|---|---|
| Volume tiers (monthly net revenue) | Rate increases when a partner drives $X net revenue in a month/quarter. | You sell self-serve and can compute net revenue reliably. | Refunds/partials create disputes if you define tiers on gross revenue. |
| Milestone tiers (new customers) | Rate increases after N new paying customers in a period. | You want to reward consistent pipeline creation. | Customer definition gets messy (trials, invoices, annual prepay). |
| Partner-type tiers (segments) | Different default rates by partner group (creator, agency, integration). | Your partner motions are fundamentally different. | Feels ‘unfair’ if segments aren’t communicated clearly. |
If you use tiers, write the rules like you expect an argument. Most disputes come from ambiguous definitions, not bad intent.
Keep one mental model: commissions become approved only when the revenue is ‘safe’ (refund window closed), and tiers are calculated on the same basis you pay on.
If you’re setting up tracking and want payout-ready exports, TinyAffiliate is built for simple affiliate ops. You can start a free trial here: https://www.tinyaffiliate.com/signup
Retroactive tiers (the whole month paid at the higher rate once the threshold is hit) can feel more ‘rewarding’, but they’re harder to explain and reconcile. Forward-only tiers are simpler and reduce disputes. Pick one and document it.
They can, but the accounting gets heavier. If you pay recurring commissions, define whether tiers are based on new revenue only or on ongoing MRR, and keep refunds/chargebacks rules consistent.
I share practical notes on affiliate programs for SaaS.No spam. No hype.
Unsubscribe anytime. No spam.
Ready to launch?
If Rewardful feels like overkill, start simple: signup page + links + Stripe-attributed revenue.

A practical checklist for migrating affiliate platforms in SaaS: what to export, how to compare ledgers, how to handle refunds and clawbacks, and the safest cutover plan.
Read articleA founder-friendly guide to affiliate tracking for SaaS subscriptions: which event earns commission, how to handle trials and plan changes, how recurring commissions work, and the tests that catch broken attribution.
Read article