Requirements

Write the requirements before you shortlist any vendors.

A requirements list built from your own billing reality — renewals, refunds, currencies, stores and who approves a payout — turns vendor demos from a feature tour into a comparison you can actually decide on.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Billing-shapedApproval-awareStore-aware

Built for operating reality

Clear contracts at every boundary.

01

Start from your billing events

List the events that should and should not create a commission: first payment, renewal, upgrade, downgrade, partial refund, chargeback, trial conversion and reactivation. That list is your requirement set.

02

Decide who may approve money

Separate who configures a programme, who approves a payout and who can see financial history. If one role does all three, the platform cannot enforce a control you may later be audited against.

03

Name every surface that sells

Web checkout, the App Store, Google Play and in-app purchases each attribute differently. A requirement that names only the web will be met by a platform that only tracks the web.

Non-functional

Write the failure requirements down too.

Duplicate delivery must not create a second commission. A refund must reverse with context. A rule change must not rewrite settled history. These read as obvious and are the requirements most often left unwritten, which is why they are the ones most often unmet.

Exit

Include the requirement to leave.

Specify what you must be able to export: affiliate identities, referral codes, live attributions with their claim history, and commissions with the rule version and monetary basis behind each one. A platform that cannot meet that requirement is a platform with a very long contract.

Questions, answered

Know where the boundaries are before you integrate.

What are the minimum requirements for SaaS affiliate software?

Server-side conversion recording, idempotent intake, recurring commission on renewals, reversal on refunds and chargebacks, a separate sandbox environment, and export of the evidence behind every commission.

Do mobile apps need different requirements?

Yes. Store purchases are confirmed by the store rather than your checkout, so attribution has to survive a purchase your own server did not process, and renewals arrive as provider events months later.

How many affiliate tiers should we require?

Start with one. Multi-tier and sub-affiliate structures multiply the reversal cases, and a clawback that has to cascade through several levels is the hardest thing to get right in the whole system.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access