Collaborator Revenue Sharing

Agree how a product's revenue is shared

Collaborator agreements record who participates in a product and the share proposed for each eligible product. Use them for product contributions without sharing the developer owner account or giving every contributor access to customer records.

Keep terms and capacity explicit

Review product assignments, rates, effective dates and the accepted version. Multiple collaborators share the post-affiliate remainder. Paused collaborator agreements retain their allocation capacity so resuming cannot exceed a complete product allocation. Ending an agreement preserves its history rather than deleting accepted terms.

Payout responsibility

SoundSync, not the developer, is responsible for the planned recipient payouts on SoundSync-collected sales. Applicable SoundSync fees are deducted first, then accepted affiliate and collaborator shares and the developer remainder are kept separate. The planned schedule is the same 1st and 15th schedule and minimum 14-day hold used for developer payouts, with refund and dispute adjustments. An external reseller receipt does not fund a payout: those proceeds remain unfunded until SoundSync actually receives the money.

Changing an agreement does not retrospectively rewrite a sale allocation or erase an earlier obligation. The live allocation, provider funding and refund handling must be connected before any preview becomes payable.