Sales
Lynx Partner Program - Subscription Bridge
Excludes subscription renewal cycles from the partner activity threshold (renewals stay commissioned but do not count)
lynx_partner_program_sale_subscription
· v19.0.1.1.0
· Standard
Beta
What this solves
Lynx Partner Program - Subscription Bridge
Thin glue between the Lynx Partner Program and Lynx Sale Subscription. It installs automatically when both are present and adds no model of its own.
Under the active-partner compensation basis, the contract distinguishes new sales from renewals: renewals stay commissioned but do not count toward the partner activity threshold (art. 8.3). Only the subscription stack knows which invoice is a renewal cycle, so that knowledge lives here, keeping the core program generic and resalable.
Key Features
Renewals do not count toward activity — an invoice generated by a later billing period of a subscription is flagged as not counting toward the activity threshold; its commission is still paid, but it does not keep the partner "active" (art. 8.3).
Initial sale still counts — the first billing period of a subscription (the new sale) counts toward the threshold normally.
Core stays dependency-free — the base program has no subscription dependency; this bridge overrides a single hook so the two features compose cleanly for tenants that run subscriptions.
Auto-Installation
This bridge installs automatically as soon as both lynx_partner_program and lynx_sale_subscription are installed: whenever subscriptions and the partner program coexist, renewal cycles must be excluded from the activity threshold, so the glue is never optional.
Depends on
Try Lynx Partner Program - Subscription Bridge on your team.
Free trial, no credit card. Talk to sales when you're ready.