GoRules Version 2 is here - redesigned, now with managed cloud.GoRules Version 2 is here!
Watch the launch videoWatch
Partner Revenue Sharing
Automated calculation system that determines commission rates, bonuses, and payouts for content, service, and technology partnership agreements.
Solution
The Partner Commission Calculator automates revenue sharing calculations based on partnership agreements. It determines appropriate commission structures by analyzing key partnership factors including partner type, revenue generated, service category, and exclusivity status. For content partners, the system applies tiered rates with higher commissions for premium streaming services generating over $1M in revenue.
The calculator factors in contract duration and customer segment to apply appropriate multipliers, rewarding longer commitments and enterprise-level partnerships. It calculates base commissions on revenue generated, then adds performance bonuses adjusted by the appropriate multipliers. This ensures fair compensation while maximizing company revenue, with all calculations transparently documented for both partners and internal stakeholders.
How it works
The decision graph processes partnership data through three main components:
Input Processing: Collects critical partnership data including partner type, revenue generated, service category, customer segment, contract duration, and exclusivity status.
Commission Rate Determination: Evaluates partner characteristics against a decision table to assign appropriate base commission rates, performance bonus rates, and partner tier classification.
Final Calculation: Applies business logic to determine duration and segment multipliers, calculates base commission amount, adjusts bonus commission with appropriate multipliers, and computes total commission and company revenue.
The system supports various partner types (content, service, technology) with specialized rate structures for each category and adjusts calculations based on revenue thresholds and partnership terms.
Where teams use it
- Media streaming partnership agreements
- Telecommunications service provider contracts
- Technology integration partnerships
- IoT service provider agreements
- Voice service reseller programs
- Content licensing agreements
Inside the decision model
Partner Revenue Sharing ships as a JDM decision graph with 3 nodes, 1 decision table and 9 rules. Download it, load it into GoRules, and run it as-is on Zen Engine.
Request
inputSix request fields describe the agreement: partnerType, serviceCategory, revenueGenerated, and exclusivity pick the rate card, while contractDuration and customerSegment feed the multipliers applied at the end.
Sample requestJSON
{
"partnerType": "content",
"revenueGenerated": 1500000,
"serviceCategory": "streaming",
"customerSegment": "enterprise",
"contractDuration": 24,
"exclusivity": true
}Partner Commission Rates
tableRate cards are resolved by matching partnerType, serviceCategory, revenueGenerated, and exclusivity under a first hit policy, so each family's most demanding row sits on top. A 'content' partner in 'streaming' with revenue > 1000000 and exclusivity true earns the 'premium' tier at a 0.35 baseCommissionRate and 0.02 bonusRate, stepping down to 0.30 above 500000 and 0.25 for the 'basic' row. 'service' partners split by category, 'voice' at 0.28 or 0.22 versus 'IoT' at 0.32, while 'technology' partners top the card at 0.40 for revenue > 1000000 and any unmatched combination falls back to 0.20 with the 'default' tier.
Paying more for exclusivity and for revenue above a threshold reflects how content and wholesale deals are actually negotiated: an exclusive catalog is a differentiator worth extra margin, and volume tiers give partners a reason to concentrate traffic with one carrier. The specific percentages are commercial choices rather than industry standards, with technology integrations rated highest because they tend to displace the most internal build cost.
| Partner TypepartnerType | Service CategoryserviceCategory | RevenuerevenueGenerated | Exclusivityexclusivity | Base Commission RatebaseCommissionRate | Performance Bonus RatebonusRate | Partner TierpartnerTier |
|---|---|---|---|---|---|---|
| 'content' | 'streaming' | > 1000000 | true | 0.35 | 0.02 | 'premium' |
| 'content' | 'streaming' | > 500000 | - | 0.30 | 0.015 | 'standard' |
| 'content' | 'streaming' | - | - | 0.25 | 0.01 | 'basic' |
| 'service' | 'voice' | > 750000 | - | 0.28 | 0.02 | 'premium' |
| 'service' | 'voice' | - | - | 0.22 | 0.01 | 'standard' |
| 'service' | 'IoT' | - | - | 0.32 | 0.025 | 'technological' |
+3 more rows in the downloadable template
Calculate Commission
expressionSettlement math happens in one pass: durationMultiplier is 1 for contracts of 12 months or less, 1.1 up to 36, and 1.2 beyond, while segmentMultiplier pays 1.15 for 'enterprise' and 1.1 for 'business' customers. baseCommission is revenueGenerated * baseCommissionRate, the bonus applies both multipliers on top of bonusRate, and totalCommission plus telcoRevenue split the generated revenue into the partner payout and what the carrier keeps, giving both sides a fully traceable statement.
contractDuration <= 12 ? 1 : (contractDuration <= 36 ? 1.1 : 1.2)customerSegment == 'enterprise' ? 1.15 : (customerSegment == 'business' ? 1.1 : 1)revenueGenerated * baseCommissionRaterevenueGenerated * bonusRate * $.durationMultiplier * $.segmentMultiplier$.baseCommission + $.bonusCommissionrevenueGenerated - $.totalCommissionOther Telco templates
View all templatesDynamic Tariff Engine
Rule-based pricing system for telecommunication services that automatically applies discounts based on user profiles, time periods, and location types.
TelcoRegional Compliance Manager
Automated system that applies region-specific data privacy rules for telecommunications services across EU, US, UK, Canada, and Australia.
TelcoCustomer Eligibility Engine
Intelligent system that analyzes customer data to determine service upgrades, loyalty rewards, and premium features based on usage patterns and account history.
Make this template
your own.
Load Partner Revenue Sharing into GoRules, adjust the rules to your policy, and ship it behind your own API.