Developer documentation
Partner and Reseller Operations
Relationship approval, product scope, external orders, serials, commissions, WooCommerce, and partner portals.
Choose the supported partner path
Reseller relationships, product assignments and reporting are separate from custom order fulfillment. Custom Partner API credentials, external-order submission, manual license issue, serial allocation and fulfillment webhooks require activation by SoundSync. These custom fulfillment operations are not currently enabled by default.
An approved WooCommerce connection has its own authorization, mapping and activation checks. Native affiliate and collaborator programs are separate again; the custom fulfillment setting does not switch those programs off. Historical records remain subject to their normal account permissions. Contact SoundSync before planning a custom fulfillment integration.
SoundSync
Partner Hub
Resellers and partner integrations are supported
SoundSync supports resellers through approved developer-partner relationships, assigned products, serial batches, external-order fulfillment, and partner API integrations. Native WooCommerce fulfillment is another supported integration path.
Sales paid through SoundSync checkout use SoundSync's Merchant of Record setup, with actual processing fees billed separately to the developer. Sales collected by an external reseller remain that seller's payments: SoundSync does not absorb their processing fees or become Merchant of Record for those sales. Product access, credentials, and API permissions follow the approved relationship.
Approve the commercial model first
A developer-partner relationship defines assigned products and permitted operations. Referral attribution, hosted checkout, external order reporting, serial batches, and API fulfillment are different models; agreeing one does not authorize them all.
Partner access is by approval. Product ownership and permissions remain enforced for the developer workspace. SoundSync-managed checkout and externally reported sales have different legal-seller and tax responsibilities.
SoundSync
What the relationship contains
| Area | Use |
|---|---|
| Products and assignments | Choose the products a partner may sell or fulfill |
| External orders and customers | Reconcile partner references with scoped fulfillment and ownership |
| Serial allocations | Allocate batches/pools, inspect availability, and export only authorized records |
| API credentials and health | Manage scoped keys, revocation, rotation, and integration health |
| Conversations and activity | Keep requests, decisions, and operational history with the relationship |
| Commission and statements | Review the agreed relationship financial records and reversals |
| Partner portal | Give approved partners their own connection and reporting workspace |
| WooCommerce | Authorize a store, approve product/variation mappings, and fulfill relevant lines |
Credentials do not belong in plugins
The partner API uses its own Bearer credentials and scopes; product licensing credentials are a different authentication system. Keep partner tokens on trusted servers. Record external order references and use the documented idempotency contract for retries.
Ending or restricting a relationship can affect keys, webhooks, and future fulfillment. Reconcile outstanding orders and statements before removing an integration. Ordinary API validation is not a new external redemption every time it runs.
SoundSync
Integration guides
SoundSync
Affiliates, collaborators, and team members
Affiliate programs
Agreements, referrals, attribution, and earnings.
Collaborator sharing
Product-specific contribution agreements.
Recipient payout policy
Funded shares, consent, eligible balances, and adjustments.
Team Accounts
Dashboard access is a separate permission.
Working with partners and contributors
Choose the model before integrating: externally collected reseller sales, managed-checkout referrals, or product revenue sharing. Each has its own credentials, authorization, and financial record.
SoundSync
Agreement and payout details
Program payouts
Eligible earnings, original-share refunds, and recipient readiness.
SoundSync
Developer relationship management
Partner Hub Management API
Separate account-session management, external fulfillment and historical reads.
SoundSync
Partner workspace and integration
Inventory, reported sales and statements have different meanings
The partner workspace separates Overview, Licenses, Sales, Statements, Conversations and Settings. Available serial pools are inventory. Redemptions can estimate activity; they are not the same as a partner-reported sale or an actual statement.
Record a reseller statement with its period, currency, reported sales, amount due, reference and cumulative payment received. A payment record describes money received outside SoundSync; saving it does not initiate a SoundSync payout. Keep currencies separate. Private PDF, CSV or XLSX statement attachments can be up to 5 MB and remain relationship-scoped.
Custom external-order API availability and an approved WooCommerce connection are separate capabilities. A disabled custom fulfillment API does not mean an approved store connection is enabled or disabled. Test validation is not a real license issue. Disconnecting a store removes saved connection credentials and stops new fulfillment while keeping history; remove unused provider keys and webhooks separately.
SoundSync
Reconcile reseller statements
External reseller statements are reporting records, separate from SoundSync checkout and platform payout history. This compatibility-screen example contains no real partner transaction.
Select the right product and serial delivery
Partner product choices distinguish relationship authorization from serial-pool eligibility. One-time download products can use customer-library redemption codes without enabling native plugin serial activation. Native activation serials remain a separate path with their own product requirements.
Subscription-only products and access-only bundles need their supported fulfillment model; archived products cannot be treated as available inventory. A product appearing in a selection list is not proof that every delivery mode is enabled. Custom Partner API fulfillment still requires SoundSync activation; approved reseller and WooCommerce paths remain separate.
External checkout has no SoundSync sale percentage
The 3% SoundSync fee applies to SoundSync-managed checkout, not a payment collected outside SoundSync by you or a reseller. A branded storefront using SoundSync checkout is still managed checkout. Your selected monthly service charge or Full Store minimum and qualifying external-redemption charges still apply. The collecting seller remains responsible for external payment-provider costs and its transaction obligations.
Reseller reports estimate the developer amount after the agreed reseller split and any recorded collaborator allocations. They do not invent an external processing rate or a SoundSync checkout fee. Existing recorded allocations retain their original estimated amounts; they are not automatically repriced or turned into funded SoundSync payouts.
Maintain an external integration without confusing it with checkout
Partner Hub relationship aliases share their existing permissions and saved commercial terms. Where custom fulfillment is enabled, authorized developers can create or rotate relationship API keys; revoking an existing key remains available as a safety action. The older developer-created order and payable-statement writes remain disabled; use the approved external integration and current statement-record tools instead.
SoundSync
Relationship and credential details
Partner Hub Management API
Alias map, key lifecycle and the distinction between external reports and SoundSync payouts.
Connect your own external checkout
FastSpring, Gumroad and developer-owned WooCommerce connections fulfill supported one-time perpetual purchases through their provider-specific authentication. They are distinct from reseller relationships, affiliate attribution and collaborator revenue shares. Map only the supported products and keep original-provider monetary refunds separate from SoundSync license reconciliation.
SoundSync
External checkout setup
Provider connections
Separate Test/Live setup, confirmed grants and original-event retries.
