Pricing

Transparent pricing without hidden-fee language.

SoundSync pricing is built around a $10 monthly minimum, 5% direct platform fee, 15% marketplace platform fee, 1,000 included marketing emails monthly, marketing email usage at $1 per additional 1,000, and clear external redemption usage after the included monthly allowance.

$10 monthly minimum

Active developer platform infrastructure.

5% direct platform fee

Direct storefront or hosted checkout sales.

15% marketplace platform fee

Marketplace listing/discovery sales.

External redemptions

10,000/month included, then $0.005 each after.

Marketing emails

Marketing emails: first 1,000 included monthly, then $1 per additional 1,000 emails. Opt-in campaign usage stays separate from transactional/system email.

Simple campaign usage1,000 marketing emails = $0. 10,000 marketing emails = $9. 50,000 marketing emails = $49.

Examples

Example calculations.

Direct $40 plugin sale

$40.00 gross sale. SoundSync platform fee: $2.00. Checkout processing is included in SoundSync platform billing; before refunds or disputes, developer revenue estimate: $38.00.

Checkout processing is included. Refunds/disputes can still reduce developer proceeds during the 14-day payout hold and through checkout review.

Marketplace $40 plugin sale

$40.00 gross sale. SoundSync platform fee: $6.00. Checkout processing is included in SoundSync platform billing; before refunds or disputes, developer revenue estimate: $34.00.

Marketplace discovery is optional and does not guarantee traffic or sales.

12,500 external redemptions

2,500 billable redemptions x $0.005 = $12.50 overage.

50,000 marketing emails

First 1,000 included, then 49,000 billable at $1 per 1,000 emails = $49.00.

Suppressed, unsubscribed, non-consented, and skipped recipients should not be sent marketing campaigns.

Billing boundaries

Usage and money-moving actions stay explicit.

Marketing email pricing applies to accepted campaign sends, while product prices, scheduled deals, refunds, subscription changes, account actions, and payout timing remain controlled workflows.

Drafts are not sends

Campaign copy is only a draft until a developer reviews the audience, suppression checks, estimates, and send action.

Price changes are deliberate

Scheduled deals and product prices require developer-controlled product workflows.

Account actions stay controlled

Refunds, cancellations, license suspension, and customer access changes stay inside explicit platform actions.

FAQ

Pricing FAQ.

Do I pay before I sell?

The pricing model includes a $10 monthly minimum for active developer platform infrastructure.

What counts as a direct sale?

A paid sale through your owned storefront or SoundSync-hosted direct checkout path.

What counts as a marketplace sale?

A paid sale attributed to the SoundSync marketplace listing/discovery channel.

What are external redemptions?

Manual, reseller, promo, offline, giveaway, or imported serial redemptions not sold through SoundSync checkout.

What counts as a marketing email?

Opt-in campaign sends such as launch emails, product updates, sale announcements, coupon campaigns, upgrade/cross-sell, and customer re-engagement.

Are transactional emails billed the same way?

No. Transactional/system email such as receipts, login/security, purchase notices, license/activation, and account notifications stays separate from marketing campaigns.

Can I email all customers?

Only eligible subscribed contacts should receive marketing campaigns. Unsubscribed, suppressed, bounced, complained, non-consented, deleted, or out-of-scope contacts must be excluded.

Do customers need to opt in?

Yes. Marketing email is consent/opt-in based and should not be used for purchased, scraped, or unrelated lists.

How are unsubscribes handled?

Marketing campaigns include unsubscribe handling and should respect suppression state where available. Developers remain responsible for following the marketing rules that apply to their business and customers.

Can I import contacts?

Imports should require consent/source responsibility and must stay scoped to the developer account. Purchased or scraped lists are not allowed.

Can I segment by product ownership?

Product ownership segments can be used where supported, but only for eligible subscribed contacts owned by that developer.

How does sender branding work?

Customer-facing sender and domain behavior depends on verified domain configuration. SoundSync should present the developer brand wherever the sender setup supports it.

What happens to bounced/unsubscribed contacts?

They should be suppressed from future marketing campaigns where tracked. Required transactional emails are handled separately.

Do I keep my customers?

Your customer relationships remain central to your storefront and product operations.

Can I export customers?

Developer customer export surfaces exist for scoped developer data. Exports should never include other developers customers.

How are refunds handled?

SoundSync uses a 14-day standard refund window before developer payout availability. After that window, refund requests may be handled according to the developer policy, SoundSync platform rules, and checkout dispute processes.

When do developers get paid?

Payout availability is modeled with settlement timing and a 14-day hold before availability so refunds and dispute timing can be handled more cleanly.

Are checkout processing fees separate?

No. Checkout processing is included in SoundSync platform billing for SoundSync checkout.

Who manages the checkout relationship?

SoundSync manages the checkout flow for SoundSync checkout. Developers should review the current platform agreement before going live.

Can I use my own storefront/domain?

Yes. SoundSync is designed around developer-owned storefront and custom domain workflows.

Can I cancel?

Developers can review cancellation and account closure rules in the platform terms before launch.

Launch Center ready

Start with clear pricing.

Know the platform minimum, commerce fees, included checkout processing, redemption usage, standard refund window, dispute handling, and payout availability expectations before launch.