Affiliate Commission Calculator for Tiered Payouts
Find the payout owed on a single affiliate sale: a 250 sale with 12,500 in qualifying volume reaches the 7.5% tier and earns 18.75. Enter the sale, the volume your program counts and each tier with its rate. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Sale amount
- 250
- Volume
- 12,500
- Applied min volume
- 10,000
- Commission percentage
- 7.5
- Commission owed
- 18.75
This affiliate commission calculator determines the payout owed on one sale when an affiliate program uses percentage tiers based on qualifying sales volume. Enter the sale amount, the volume used by the program for tier eligibility, and each threshold with its commission percentage. The calculator selects the highest threshold reached, applies that rate to the sale, and returns a currency-ready amount rounded to two decimal places. It is useful for checking statements, previewing payouts, and making commission logic explicit before it enters an automated workflow.
Describe the sale and the qualifying volume separately
Start with the amount of the individual sale for which commission is owed. Then enter the qualifying volume that your affiliate program uses to determine the rate. Keeping those two values separate matters because the payout is calculated on the sale amount, while the volume only selects the percentage tier.
A program may define qualifying volume as monthly revenue before this sale, monthly revenue including this sale, lifetime referred revenue, or another documented total. Use the exact convention in the affiliate agreement so the selected tier matches the statement you are checking. The calculator does not add the sale amount to volume automatically, because doing so would silently impose one program's policy on every other program.
Both amounts must be finite and nonnegative. A zero sale is valid and produces a zero payout, which can be useful for testing a tier schedule. A negative sale is rejected instead of being treated as a refund or clawback, since those cases usually follow separate contractual rules and should not be disguised as an ordinary commission calculation.
Build a clear threshold and percentage schedule
Add one row for every commission tier. Each row contains a minimum qualifying volume and the commission percentage that begins at that threshold. For example, a base row can begin at zero, a higher rate can begin when volume reaches a program milestone, and another rate can begin at the next milestone.
Rows may be entered in any order: the algorithm examines the complete schedule and selects the eligible row with the greatest minimum volume. Duplicate thresholds are rejected because two rates at the same boundary would make the contract ambiguous. Percentages must be between zero and one hundred, and thresholds cannot be negative.
Include a threshold at or below the volume being evaluated. In most schedules that means including a base tier at zero. The calculator applies the selected percentage to the entire sale amount; it does not split one sale progressively across bands.
That distinction is important. A progressive schedule, where portions of volume earn different rates, is a different commission model and should not be represented as a simple tier schedule.
Read and reconcile the calculated payout
The result repeats the sale amount and qualifying volume, identifies the minimum volume of the tier that was applied, reports its commission percentage, and gives the commission owed. The raw multiplication is rounded to two decimal places, matching the precision commonly used for currency payouts. Because currency codes and conversion rates are not part of the input, the result remains in the same currency as the sale amount: a sale entered in dollars yields a dollar-denominated payout, while a sale entered in euros yields a euro-denominated payout.
Keep all tiers and the sale in one consistent monetary basis. When reconciling an affiliate statement, compare the returned threshold and percentage before comparing the final amount. A difference in the selected tier usually points to a volume-definition or reporting-period disagreement, while a matching tier but different payout may indicate rounding, exclusions, or adjustments in the program's contract.
The same deterministic logic is used in both channels, with no network calls or changing external data.
What you can do with it
Check an affiliate statement
Recalculate the commission on a reported sale and confirm that the statement used the tier reached by the agreed qualifying volume.
Preview a partner payout
Estimate what a partner will earn on a pending sale after entering the current volume and the program's published thresholds.
Test commission rules before automation
Run representative sales at tier boundaries to verify that a proposed schedule selects the intended rate before connecting it to a payout workflow.
FAQ
How is the applicable commission tier selected?
Tier rows do not need to be sorted.
Does volume include the current sale?
Use the definition in your affiliate agreement. Enter volume including the sale only when the program uses that convention; the calculator does not add it automatically.
Are the tiers progressive?
No. The selected tier's percentage applies to the entire individual sale amount. This calculator does not allocate portions of a sale or volume across multiple bands.
How is the commission amount rounded?
The calculated payout is rounded to two decimal places. The result uses the same currency basis as the sale amount because no currency conversion is performed.
What happens if the sale amount is negative?
Refunds and clawbacks may have different contractual treatment and are intentionally outside this calculator's scope.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/ecom/affiliate-commission-calc \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"sale_amount":250,"volume":12500,"tiers":[{"min_volume":0,"commission_percentage":5},{"min_volume":10000,"commission_percentage":7.5},{"min_volume":25000,"commission_percentage":10}]}'const res = await fetch("https://api.kit.forhosting.com/ecom/affiliate-commission-calc", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"sale_amount": 250,
"volume": 12500,
"tiers": [
{
"min_volume": 0,
"commission_percentage": 5
},
{
"min_volume": 10000,
"commission_percentage": 7.5
},
{
"min_volume": 25000,
"commission_percentage": 10
}
]
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/ecom/affiliate-commission-calc",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"sale_amount": 250,
"volume": 12500,
"tiers": [
{
"min_volume": 0,
"commission_percentage": 5
},
{
"min_volume": 10000,
"commission_percentage": 7.5
},
{
"min_volume": 25000,
"commission_percentage": 10
}
]
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/ecom/affiliate-commission-calc", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"sale_amount":250,"volume":12500,"tiers":[{"min_volume":0,"commission_percentage":5},{"min_volume":10000,"commission_percentage":7.5},{"min_volume":25000,"commission_percentage":10}]}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"sale_amount":250,"volume":12500,"tiers":[{"min_volume":0,"commission_percentage":5},{"min_volume":10000,"commission_percentage":7.5},{"min_volume":25000,"commission_percentage":10}]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/ecom/affiliate-commission-calc", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"sale_amount": 250,
"volume": 12500,
"tiers": [
{
"min_volume": 0,
"commission_percentage": 5
},
{
"min_volume": 10000,
"commission_percentage": 7.5
},
{
"min_volume": 25000,
"commission_percentage": 10
}
]
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "ecom.affiliate_commission_calc",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Read and reconcile the calculated payout
The browser calculation is free, while an automated API request costs $0.002.
Technical questions
What does an API calculation cost?
Each API request costs $0.002. You can also run the same deterministic calculation free in your browser.