Forum
    • Categories
    • Register
    • Login
    1. Home
    2. soundsync
    3. Posts
    • Profile
    • Following 1
    • Followers 1
    • Topics 114
    • Posts 703
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Payment providers compared

      Hey Gang,

      Quick update: SoundSync’s previous 10% pricing has been replaced.

      3% SoundSync fee on discounted sales, excluding tax, plus actual payment-processing fees.

      $20 monthly minimum on sales fees only—not $20 plus 3%.

      Marketing emails: 1,000 free/month, then $0.50 per started 1,000.

      Free/external redemptions: 10,000 free/month, then $0.005 each. License validations and activations don’t count.

      Developer payouts through Stripe or PayPal, with applicable payout/FX fees deducted and displayed. Estimates reconcile to actual charges.

      Using your own checkout? Licensing + Hosting remains $20/month, or Licensing only $10/month, plus applicable usage, with no percentage on external sales.

      The old figures in my earlier posts/PDF are outdated.

      posted in General Questions
      soundsyncS
      soundsync
    • Email Marketing, Audiences, and Growth Flows

      Hey Gang,

      I’ve talked a little about Growth Flows already, but wanted to show some actual screens and give a quick look at the rest of the email marketing tools in SoundSync.

      It’s a fairly big section, so I’ll touch on the main parts here and leave the more detailed walkthroughs for anything people want to see.

      Email campaigns

      You can put together product updates, launch emails, offers, or newsletters using the visual email builder. Start blank or from a template, then add text, artwork, buttons, product sections, and other blocks.

      A preview of my recent Halowire / Ivoryveil campaign, with a dark background and large artwork.

      A preview of my recent Halowire / Ivoryveil campaign, with a dark background and large artwork.

      You can preview the email, check the mobile view, send a test, and choose when it goes out. There’s also a cart-link tool for putting a product selection behind an email button; the customer reviews the cart before checkout.

      Contacts and segments

      Contacts can be imported from a CSV, and you can filter or save segments using things like product ownership, purchase dates, and recorded email activity. The audience estimate helps you check who is eligible before sending. Unsubscribes, complaints, bounces, and suppressions are respected.

      Filter by a catalog product and recorded email activity, then reuse the rules as a segment.

      Filter by a catalog product and recorded email activity, then reuse the rules as a segment.

      Growth Flows

      These handle follow-ups around a customer event or a selected audience. The templates cover onboarding, cart recovery, review requests, cross-sell / upsell, promotion follow-ups, winback, product updates, new releases, and special promotions.

      A few of the available starting templates, including onboarding, recovery, reviews, and cross-sell.

      A few of the available starting templates, including onboarding, recovery, reviews, and cross-sell.

      You choose the emails and the delays between them. For example, a flow could introduce related products seven days after someone receives access, then follow up a week later. Cross-sell can respond to supported purchases, free claims, serial redemptions, and access grants, and recommends products the customer doesn’t already own.

      An example sequence: Email 1 waits seven days after the trigger; Email 2 waits seven more days after Email 1.

      An example sequence: Email 1 waits seven days after the trigger; Email 2 waits seven more days after Email 1.

      Optional rewards

      Supported flows can include a promo code or a reward tied to a qualifying action. A review flow, for example, can send a separate coupon email after an eligible review is approved. A review incentive should welcome honest feedback regardless of the rating.

      Review reward controls show the approval condition and coupon selection.

      Review reward controls show the approval condition and coupon selection.

      Reports and sending setup

      Reports separate sent and delivered messages, opens, clicks, unsubscribes, bounces, and complaints, with attributed orders and revenue where available. Growth Flows also show queue status and recipient history so you can check what happened with a particular follow-up.

      Moonwave’s reporting view, with delivery and engagement metrics (figures blurred).

      Moonwave’s reporting view, with delivery and engagement metrics (figures blurred).

      The sending settings bring together your sender identity, reply-to, business details, and required footer. Home gives you a quick look at the audience, send usage, campaigns, and automation activity.

      Sending settings show Moonwave’s sender identity and reply-to address.

      Sending settings show Moonwave’s sender identity and reply-to address.

      All of this is managed through the dashboard. If there’s a particular part you’d like to see in more detail, I can put together a separate walkthrough.

      Email marketing guides

      Growth Flow details

      What are you currently using for your emails and follow-ups, and what would you find useful to have connected to your products?

      posted in General Questions email marketing growth flows automation sell plugins
      soundsyncS
      soundsync
    • Setting Up Promotions Around Your Catalog

      Hey Gang,

      I wanted to show a bit more of the promotions side of SoundSync and a few ways you can put an offer together around your products.

      There are regular promo codes, single and tiered cart discounts, buy-one-get-one offers, group buys, and purchase rewards. There’s also a separate subscription-promotion option for the initial subscription payment; renewals use the regular list price.

      Some of the offer choices in the promotion editor.

      Some of the offer choices in the promotion editor.

      Promo codes and the rules around them

      For a code, you can choose a percentage or fixed USD discount, the eligible products, dates, minimum spend, and usage limit. Codes can also be restricted to specific customers.

      An example 10% code, with Paused selected during setup.

      An example 10% code, with Paused selected during setup.

      You can choose whether a code works on sale items and whether it combines with an automatic offer. Those are separate settings, so it’s worth checking both when putting a promotion together.

      Sale-item eligibility, automatic-discount stacking, product scope, and customer eligibility are separate choices.

      Sale-item eligibility, automatic-discount stacking, product scope, and customer eligibility are separate choices.

      Cart discounts

      A single cart discount can apply after the cart reaches a minimum number of eligible items. Tiered discounts let you change the percentage based on how many different eligible products someone chooses.

      For example, I could include Moonwave’s Conduit, Voidline, and Eidolon and set:

      Conduit, Voidline, and Eidolon selected as the eligible products.

      Conduit, Voidline, and Eidolon selected as the eligible products.

      • Two different eligible products: 10% off.
      • All three: 15% off.

      That can apply automatically at checkout or require a code. Buying extra copies of the same product doesn’t unlock a higher tier; the threshold counts different eligible products.

      Entered example tiers: two different products for 10%, and three for 15%.

      Entered example tiers: two different products for 10%, and three for 15%.

      The customer preview shows the calculation before you activate anything. With three eligible products and an illustrative $100 subtotal, this example takes $15 off, leaving $85 before tax.

      The three-product example reaches the 15% tier: $15 off an illustrative $100 subtotal.

      The three-product example reaches the 15% tier: $15 off an illustrative $100 subtotal.

      Purchase rewards

      You can also issue a customer-specific coupon after a qualifying purchase. For example, someone buys an instrument and receives a $10-off coupon for a future order, with one use and 30 days to redeem it.

      A Moonwave example reward with a $10 coupon value.

      A Moonwave example reward with a $10 coupon value.

      In this example I’ve set a $20 minimum eligible spend for redemption. You can configure the qualifying purchases, reward expiry, and whether to issue one coupon per order or per distinct qualifying product.

      The preview shows the $10 coupon, one use, 30-day expiry, and $20 minimum spend.

      The preview shows the $10 coupon, one use, 30-day expiry, and $20 minimum spend.

      Before making an offer active, check its preview, eligible products, and final checkout price. Paid products need to remain at least $9.99 after discounts, before tax.

      You can keep offers paused while preparing them and review their usage once they’re running. Coupon imports also have a preview so you can check the matches and any problems before applying them.

      Promotion details and setup

      What kinds of offers are you currently running, and which parts are the most awkward to manage?

      posted in General Questions promotions sell plugins discounts rewards
      soundsyncS
      soundsync
    • Bringing an Existing Catalog Into SoundSync

      Hey Gang,

      One thing I wanted to go through is how you can bring an existing product catalog into SoundSync without entering every product again.

      You can start with a public store URL, a product export such as a CSV, or use both together. The importer finds what it can, then gives you a review screen before anything is saved as a draft.

      I’m using Moonwave for the examples below, with Conduit, Voidline, and Eidolon in the CSV walkthrough. The delivery ZIPs are small test files for showing the process; they aren’t the actual product installers. Everything shown stays unpublished.

      1. Open the importer

      Go to Products → Import / Upload. There is a Store URL field and an optional Product export field. You can leave the URL blank and use an export on its own.

      01-import-start-focused.jpg

      The starting screen supports a URL, an export, or both.

      2. Import from a CSV

      Choose your CSV and click Find my products. CSV, TSV, Excel (.xlsx), and JSON exports are supported, up to 8 MB.

      Open Review export column mapping and check where your columns are going. For example, Product Name should map to the product name, Price to the product price, and any download-link columns to private delivery links. Use product prices here, rather than an order total or sales report.

      There is also a Download Demo Import CSVs button with editable examples, including WooCommerce- and Shopify-style exports. Unzip the examples and replace the demo values and URLs with your own.

      02-csv-selected-focused.jpg
      Moonwave CSV selected, with the Store URL left blank.

      03-csv-column-mapping-focused.jpg
      Check the name, price, artwork, and video column mappings.

      3. Import from a website URL

      For the URL route, enter your public store address and click Find my products. The export field can stay empty. An individual public product page can also be used to bring in one product.

      SoundSync looks for readable product information and supported artwork, public audio, and video references. Check the final product list against your original catalog; the number found is not a guarantee that every product was discovered.

      If the site needs a login, blocks access, or only exposes its product content after JavaScript runs, use an export or fill in the missing information manually. You can also provide a URL and an export together.

      For the Moonwave product results in this walkthrough, I used the CSV route. If homepage scan does not recognize the products or you get an empty or incomplete result, add an export and check it against your catalog.

      12-web-url-selected-focused.jpg
      The URL entry step, using Moonwave’s public store address. Product-result screenshots below come from the CSV import.

      4. Check the product details

      For either route, expand the products and check the actual information. In particular:

      • Are all the expected products present, and are any duplicates or variants being mistaken for separate products?
      • Are the names, descriptions, product types, and listed contents correct?
      • Are the prices correct in USD? No currency conversion is performed. Review any missing-price or minimum-price warnings.
      • Are the selected images the right artwork? Are audio files public demos rather than the files customers are meant to receive?
      • Are video links correct, and is anything important missing?
      • For repeat imports, is an item a new product, a matched draft, or a published product that will be skipped?

      Selected artwork and public audio are copied into SoundSync storage before the drafts save. If a copy fails, retry it or deselect that file and upload a replacement later. Supported video embeds stay with their video provider.

      04-review-product-details-focused.jpg
      Review Conduit’s name, type, price, and description.

      16-moonwave-media-review-focused.jpg
      Review the Moonwave artwork and video included from the CSV. Public media is separate from private delivery files.

      5. Save the selected products as drafts

      Select the products you want, confirm the review checkbox, and click Save selected as drafts. Nothing is published automatically.

      Matched drafts are unselected by default. If you opt into filling their empty fields, existing saved content and prices are preserved. Published products are skipped by this importer.

      05-drafts-saved.jpg
      The three Moonwave walkthrough drafts are ready for delivery files and final setup.

      6. Add files from your computer

      Under Add delivery files together, select your installers or product archives and check the product assigned to every file. Filename matches are suggestions, so correct them before clicking Upload matched files.

      You can attach several files to one product. Here the Windows and macOS test ZIPs both go to Conduit, while the third test ZIP goes to Voidline.

      These are private customer downloads, separate from the public artwork and audio demos. Package installers as ZIPs; supported manuals, audio, text, and MIDI files can also be attached.

      The interface supports up to 10 GB per file. Keep the tab open for local transfers. Upload progress is retained for 24 hours from the start; after a reload, choose the same original files to resume saved chunks.

      06-match-local-delivery-files.jpg
      Two test files matched to Conduit, with a separate file matched to Voidline.

      11-files-in-product-editor-focused.jpg
      The Conduit draft retains both operating-system test archives when reopened.

      7. Add files from download links

      If your files already have direct download URLs, use Import delivery files from links. Upload a CSV with a product-name column and one or more download-link columns, then click Review download links.

      Confirm the name and link columns, check each product match, select the files you want, and confirm the private-delivery checkbox before starting the import. Unmatched or duplicate names need a manual product selection.

      These need to be direct file links, including valid signed links where appropriate. A checkout page, sign-in page, or ordinary share page is not a direct download. Expired links need replacing.

      SoundSync copies the files into private delivery storage and attaches them to the selected product. Link imports continue on the server if you leave the page. Check for an attached result and review or retry failures.

      For the Eidolon example here, I used SoundSync’s public demo-CSV ZIP as a harmless test transfer. It isn’t an Eidolon installer. For an actual product, use your own delivery URLs.

      08-download-link-review-focused.jpg
      Review the Eidolon draft, selected test download, and confirmation before importing. The test download is attached privately to the Eidolon walkthrough draft.

      8. Finish the product setup before publishing

      Open each draft and check the remaining setup:

      • Product copy, artwork, public demos, version, product type, and price.
      • Actual downloadable files: filenames, Windows/macOS versions, manuals, and archive contents. Test the downloads.
      • Compatibility/specifications, installation instructions, license documents, and support information.
      • Access and licensing settings. For a plugin, generate the appropriate integration package and test activation and validation in your exported build.
      • Any bundle membership or subscription configuration, which needs its own setup.
      • The product-page preview, storefront placement, and intended publication settings.

      The catalog import handles product information and supported files. Existing customer accounts, past orders, recurring billing, and marketing permissions need their separate migration workflows.

      I wanted to show the whole process because finding the products is only part of moving a catalog. The review and delivery steps are where you make sure customers receive the right thing.

      If you have an export from another platform, I’d be interested to hear which fields or file formats have been the most awkward to move.

      10-finish-product-setup-focused.jpg
      The imported product remains a draft while the remaining product sections are reviewed.

      Import overview: https://www.soundsync.dev/features/product-import

      posted in General Questions sell plugins import
      soundsyncS
      soundsync
    • Automated Growth Flows | Onboarding, Reviews, Cross-Selling, Cart Recovery, Winback and more.

      Hey Gang,

      I’ve been doing some more work on the Growth Flows in SoundSync and wanted to explain what they can do.

      These let you set up emails around things like a purchase, an abandoned checkout, or a customer getting access to a product. You choose the products and audience, write the emails, and set the delays between them.

      The current flows include:

      • Product onboarding — send installation/activation help, then follow up with tutorials or tips.
      • Cart recovery — follow up with eligible customers who started checkout but didn’t finish.
      • Review requests — ask for feedback after giving someone some time with the product.
      • Cross-sell / upsell — recommend other products from your catalog, leaving out products the customer already has.
      • Product updates and new releases — prepare emails for existing owners or another selected audience.
      • Promotion follow-ups — remind an eligible audience about an offer they haven’t used.
      • Winback — follow up with eligible customers after a period of inactivity.
        For example, you could send someone a getting-started email after purchasing an instrument, then a walkthrough a few days later. You could also set up a separate review request once they’ve had some time to use it.

      Some flows also support rewards for certain actions. For example, you can offer a promo code after a qualifying review, with your own eligibility and expiry settings. Review rewards are for honest feedback, regardless of the rating.

      One thing I’ve just updated is the cross-sell flow. That can now start when someone receives product access through a purchase, free claim, serial redemption, or a manual grant.

      So if you have a free instrument, you can configure a follow-up that introduces eligible customers to other products they don’t already own. You choose the timing and what you want to recommend.

      You can preview and test the emails, edit the individual steps, pause a flow, and see what’s queued, sent, or failed. There’s also recipient history so you can check what happened with a particular customer. Unsubscribes and other marketing restrictions are respected.

      This is all handled through the SoundSync dashboard and email. There’s no extra scripting to add to your instrument for these flows.

      I wanted to share this because a lot of the work continues after someone gets the product, especially when you’re handling everything yourself.

      Growth Flow details and setup

      Would be interested to hear what follow-ups you’re currently doing manually, or what you’d find useful here.

      posted in General Questions growth selling plugins automation
      soundsyncS
      soundsync
    • RE: Overview, intro videos and AI....

      @David-Healey It's not perfect but I'm still figuring it out. Chat may not be the best option but I think it did pretty well. I have high hopes once its dialed in.

      posted in General Questions
      soundsyncS
      soundsync
    • RE: Overview, intro videos and AI....

      @Lindon I released 2 plugins about a week ago and both used ChatGPT to help create the Intro and Walkthrough videos.

      Ivoryveil
      https://moonwavefx.com/products/ivoryveil-piano-engine

      Halowire
      https://moonwavefx.com/products/halowire-guitar-engine

      I worked with Chat through the entire process creating the script, timeline, styling, etc etc etc.

      The end product is Chat putting it all together. I only had 1 or 2 revisions and I was happy.

      To be honest, the time saved was ridiculous and it tuned out better than I would do anyway.

      posted in General Questions
      soundsyncS
      soundsync
    • RE: AI takeover the plugin industry

      @lijas90 Time. This the the one & you've hit it on the nose.

      posted in AI discussion
      soundsyncS
      soundsync
    • RE: AI takeover the plugin industry

      @SampleScience @David-Healey

      Davids right, it's more than a plugin, its the entire user experience. People still like interacting with people, they just don't care how the plugin came together, especially if it works great and solves the problem.

      I started off nearly 15 years ago creating music, sample packs, midi packs, construction kits, etc.

      I certainly wouldn't consider myself a professional coder, hense why I came to HISE years ago. It was a way, with limited coding experience, to expand my brand.

      AI has done that x10.

      My opinion is adapt and move forward, not retreat. I don't think AI is going anywhere. Praying for its downfall wouldn't be a hill I'd be willing to die on.

      posted in AI discussion
      soundsyncS
      soundsync
    • RE: Payment providers compared

      Quick follow-up on the documentation gaps raised earlier: we’ve expanded SoundSync’s public pages so the features, fees, and commercial policies are easier to find.

      Product migration is now supported. You can bring a catalog from another platform using public store/product pages or a supported spreadsheet/JSON export. Imports become drafts for review before publishing. Customer accounts and existing recurring payments are separate from catalog migration. Migration details

      Security and integrations have expanded too. We support authenticator-based two-factor authentication, recovery codes, and team accounts with role and product-specific access. HISE developers have both HISEScript and native C++ integration paths, alongside the JUCE package. The API documentation now covers substantially more of the platform, including licensing, refunds, subscriptions, and partner integrations.
      Account security · Developer documentation

      We’ve also expanded the Website Builder and branding tools, including root-domain support and SoundSync-provided SSL, plus native affiliate and collaborator programs alongside reseller integrations.

      The commercial details are now explicit: Stripe and PayPal checkout, USD-only pricing, and one 10% SoundSync fee covering ordinary payment processing on SoundSync-managed checkout. Developer, affiliate, and collaborator payouts follow the same schedule: the 1st and 15th, after the minimum 14-day hold.

      The updated pages also explain Merchant of Record responsibilities, tax handling, refunds, disputes, and payout eligibility.
      Pricing · Trust Center · Payout policy

      Thanks again for pointing out what was missing. That feedback helped us make the information much clearer.

      posted in General Questions
      soundsyncS
      soundsync
    • RE: Payment providers compared

      @dannytaurus Thanks for putting this comparison together. I'm Aaron, the developer behind SoundSync. Your post highlighted some genuine gaps in our public documentation, so I've updated the site to make these details much easier to find and compare.

      I've also attached a detailed 10-page reference covering the SoundSync entries in your comparison, newer features, and links to the relevant public pages:

      Download the SoundSync information reference PDF

      Pricing and what's included

      SoundSync charges one 10% fee on SoundSync-managed sales, with ordinary payment processing included. There is no additional marketplace fee and no fixed per-sale SoundSync charge. For example, a $49 sale has a $4.90 SoundSync fee, leaving $44.10 for the developer before any agreed affiliate/collaborator shares. Tax is handled separately from product earnings.

      The $10 monthly minimum is a minimum, not another subscription charge on top: SoundSync fees already incurred that month, including sales fees and usage charges, count toward it. If those total $7, the shortfall is $3; if they total $10 or more, there is no minimum top-up. Paid products, bundles, and subscriptions must be $9.99 or higher after discounts, before tax.

      Transactional emails are included. Marketing email includes 1,000 sends per month, then $1 per started block of 1,000 additional sends. Qualifying free claims and external serial redemptions include 10,000 per month, then $0.005 per additional redemption. These allowances reset monthly without rollover. Normal licensing validation calls are not billed as external redemptions, and a free BOGO gift included in a paid checkout does not incur an external-redemption charge.

      Pricing: https://www.soundsync.dev/pricing

      Email counting and billing: https://www.soundsync.dev/docs/email-marketing/usage

      Fees and redemptions: https://www.soundsync.dev/docs/fees

      Payments, Merchant of Record, and the business behind it

      PayPal is supported for one-time checkout, alongside Stripe payment options. Recurring subscriptions currently use Stripe. Products and checkout currently use USD only; this is not a claim of local-currency pricing. Any provider currency conversion is separate, and developers bear applicable conversion costs when receiving funds in another currency.

      SoundSync Solutions is the Merchant of Record for SoundSync-managed checkout, including developer storefront and marketplace sales processed through that checkout. SoundSync handles the applicable sales-tax/VAT responsibilities for those sales. The tax page lists current country coverage and explains the scope; developer income taxes remain the developer's responsibility. An external reseller collecting its own payment is different: SoundSync does not absorb that reseller's processing fees or become its Merchant of Record merely by fulfilling a serial or entitlement.

      SoundSync Solutions is based in Michigan, USA. The business address is 2632 Crossing Circle #1010, Traverse City, Michigan 49684, and support is support@soundsyncsolutions.biz. The site now has substantive Terms and Privacy information, rather than just headings, plus retention and account-closure details.

      Payments: https://www.soundsync.dev/payments

      Merchant of Record: https://www.soundsync.dev/trust/merchant-of-record

      Tax scope and countries: https://www.soundsync.dev/trust/tax-compliance

      Business information: https://www.soundsync.dev/about

      Terms: https://www.soundsync.dev/legal/terms

      Privacy: https://www.soundsync.dev/legal/privacy

      Where funds are held, and when payouts happen

      Funds collected through Stripe and PayPal are transferred manually to a dedicated business account used only for developer, affiliate, and collaborator payouts, not business expenses. Developer payouts are made through Stripe Connect. This is a dedicated payout account, not a claim of escrow or deposit insurance.

      Payouts are scheduled twice monthly, on the 1st and 15th, after at least a 14-day hold. Eligible funds go into the next scheduled payout after that hold completes. There is no SoundSync payout minimum or routine reserve. The scheduled date means payment initiation, not a guaranteed bank-arrival date; unresolved disputes, account restrictions, or payout-destination issues can affect an individual balance.

      Payout policy: https://www.soundsync.dev/trust/payouts

      Refunds and disputes

      Customers request refunds from the product developer within 14 days of the initial purchase. Authorized developers can refund the full order or selected whole products; arbitrary cash amounts and fractional refunds of one product are not supported. For subscriptions, the standard refund policy covers the initial payment, not renewals, with mandatory consumer rights still applying.

      The customer receives the refunded product's paid amount and associated tax. SoundSync retains its original share, and the developer is responsible for actual additional refund charges and confirmed chargeback/dispute losses. This is separate from ordinary checkout processing already included in the 10% fee. Affiliate/collaborator shares reverse according to the original allocation. Access associated with the refunded purchase is withdrawn; unrelated purchases are not removed.

      Refund and dispute policy: https://www.soundsync.dev/trust/refunds-disputes

      HISE, JUCE, licensing, and delivery

      There are now two HISE integration paths: HISEScript, for easier integration without modifying HISE source, and native HISE C++, which requires patching/rebuilding HISE and offers stronger native enforcement. The JUCE package is also available, with activation, processor-owned licensing, and Store/My Products integration. Package-specific requirements matter: HISEScript documents configurable offline grace following a valid state, while the current JUCE release requires online renewal at startup and does not provide offline audio access.

      The public API reference includes serial claims and claim status, activation, customer-login activation, validation, and deactivation, with authentication and request/response details. File delivery uses authorized customer downloads, and the customer library brings together owned products, downloads, serials, device access, and support.

      HISE docs: https://www.soundsync.dev/docs/hise

      Native HISE setup: https://www.soundsync.dev/docs/hise/native-setup

      JUCE docs: https://www.soundsync.dev/docs/juce-package

      Licensing API: https://www.soundsync.dev/docs/api/licensing

      File delivery: https://www.soundsync.dev/features/secure-delivery

      Customer library: https://www.soundsync.dev/features/customer-library

      Storefronts and branding

      SoundSync supports hosted storefronts and a full embedded commerce experience, including catalog, product pages, cart, checkout, and customer access. Custom domains can use the main domain, not just a shop/store subdomain. Developers need domain control and DNS access; SoundSync provides guided setup and manages the hosted connection and SSL certificates once verified. Brand Manager covers logos, light/dark branding, colors, imagery, support details, and the supported brand settings reused across the storefront and other surfaces.

      Storefronts: https://www.soundsync.dev/features/storefronts

      Branding and domains: https://www.soundsync.dev/features/brand-manager-domains

      Affiliates, collaborators, teams, and resellers

      There are dedicated native affiliate and collaborator programs, not just reseller attribution under another name. Affiliates use agreed product/rate terms and referral links; collaborators use product revenue-sharing agreements. Their earnings and payouts are tracked separately. Team Accounts are a separate permissions system, so a revenue-sharing agreement does not automatically grant dashboard access. Approved resellers also have serial, external-order, fulfillment, and API integration paths, including WooCommerce.

      Affiliates: https://www.soundsync.dev/features/affiliates

      Collaborators: https://www.soundsync.dev/features/collaborators

      Team Accounts: https://www.soundsync.dev/features/team-accounts

      Resellers: https://www.soundsync.dev/features/partners

      Partner API: https://www.soundsync.dev/docs/api/reseller-partner

      Email, growth, subscriptions, and marketplace discovery

      Marketing includes campaigns, audience management, scheduling, reports, and growth flows such as cart recovery, onboarding, review requests, follow-ups, and winback. Promotions include scheduled deals and supported codes/offers. Subscription documentation distinguishes recurring access from models where paid invoices earn product ownership.

      Marketplace discovery is included in the same commercial model. Launch into an ecosystem backed by nearly 50,000 established audio-software customers.

      Email marketing: https://www.soundsync.dev/features/email-marketing

      Growth flows: https://www.soundsync.dev/docs/email-marketing/growth-flows

      Subscriptions: https://www.soundsync.dev/features/subscription-bundles

      Marketplace: https://www.soundsync.dev/features/marketplace

      Two clear "no" answers for the comparison

      We do not currently offer assisted Gumroad migration or pay-what-you-want pricing. Imports and external fulfillment should not be described as a Gumroad account-migration service.

      Migration policy: https://www.soundsync.dev/docs/migrations

      Product setup: https://www.soundsync.dev/docs/products

      SoundSync is still a newer platform, and I understand that documentation is only part of evaluating one. My aim here is to make the commercial details and integration requirements public and easy to check, rather than leave you guessing. Thanks again for calling out what was missing.

      Trust Center: https://www.soundsync.dev/trust

      Documentation: https://www.soundsync.dev/docs

      posted in General Questions
      soundsyncS
      soundsync
    • RE: Payment providers compared

      @David-Healey I've tried getting SES for over a year now with no luck, they deny every time.

      How did you manage to get it?

      If I could get them, I could reduce Soundsync marketing email pricing by nearly 50%.

      posted in General Questions
      soundsyncS
      soundsync
    • RE: The gap between finishing a plugin and running a plugin business

      @dannytaurus A bit of a rigamarole but I'm biased lol.

      @cartemtune I'd open it up. As David said, Japan & Australia have a good market, about 15% of my sales are these 2 places.

      posted in General Questions
      soundsyncS
      soundsync
    • RE: The gap between finishing a plugin and running a plugin business

      @dannytaurus What do you mean by reseller terms?

      posted in General Questions
      soundsyncS
      soundsync
    • RE: The gap between finishing a plugin and running a plugin business

      @dannytaurus ahhh I see now, I misunderstood the statement.

      posted in General Questions
      soundsyncS
      soundsync
    • RE: The gap between finishing a plugin and running a plugin business

      @cartemtune Does it prevent you from using the platform once the cap is reached?

      posted in General Questions
      soundsyncS
      soundsync
    • Why you should plan for support before launch.

      Hey Gang,

      Planning how your plugin business handles licensing, logging, customer accounts, purchases, activations, updates, and product management can prevent many support requests before they happen.

      It also gives you the information and tools you need when a customer does need help.

      A few things worth planning early:

      • A reliable licensing system that handles activation, restoration, device limits, and offline use.
      • A logging system that records useful technical information without collecting the customer’s creative data.
      • A customer-management system that connects purchases, products, licenses, downloads, and support history.
      • A solid checkout and order system for failed payments, duplicate purchases, refunds, receipts, chargebacks, and missing orders.
      • A clear Merchant of Record or payment-processing setup so tax, billing, refunds, and customer responsibilities are properly defined.
      • Self-service tools for resetting activations, managing devices, finding receipts, and downloading products again.
      • A clear way to identify the installed plugin version and whether an update is available.
      • Useful error messages that explain what happened instead of only saying something failed.
      • A simple way for customers to send relevant diagnostic information with a support request.
      • A plan for server outages, expired subscriptions, refunded purchases, and other unusual situations.

      Purchase issues can create just as much support work as technical problems. A customer may have been charged but not received access, used a different email at checkout, purchased the wrong product, or lost their receipt. If orders, customer accounts, product access, and licensing are disconnected, resolving a simple issue can require searching through several systems.

      When everything is connected, support becomes much easier.

      If someone changes computers, they can reset an old activation themselves. If a customer reports a problem, you can quickly see what they purchased, which version they are using, and whether their license is active. If a payment or fulfillment problem occurs, you can trace the order and restore access without manually piecing everything together.

      Good customer service is not only about responding quickly. It is also about building systems that prevent confusion and give both the customer and developer useful options when something goes wrong.

      This is one of the areas we are working on with SoundSync: connecting commerce, customer accounts, licensing, activations, downloads, product versions, communication, and support information in one system.

      The goal is to reduce preventable support requests while making the requests that do happen much easier to understand and quicker to resolve.

      posted in General Questions support launch licensing copy protection
      soundsyncS
      soundsync
    • RE: Using customer data to grow a plugin business

      @dannytaurus SoundSync can currently receive information related to the product’s operation and the customer journey, including:

      • When the plugin is opened or connects to SoundSync
      • Activation, validation, restoration, and deactivation activity
      • The installed plugin version
      • The product and license associated with the activation
      • A hashed installation/device identifier for managing activations
      • Interactions with SoundSync-provided areas such as activation, account, store, support, and update interfaces
      • Timestamps showing recent validation or connection activity

      This can be combined with information already created elsewhere in SoundSync, such as purchases, products owned, downloads, customer accounts, support activity, email engagement, and marketing consent.

      That makes practical things possible. For example, a developer could notify customers using an outdated version, help somebody who purchased but never activated, exclude existing owners from a promotion, or create a re-engagement flow based on meaningful customer activity, cart recovery, etc, etc.

      SoundSync does not inspect or collect the customer’s audio, MIDI, presets, parameter changes, DAW projects, filenames, or what they are creating. We are interested in product lifecycle events that help with licensing, updates, support, and relevant communication, not the customer’s creative activity.

      We also try to keep the principle fairly simple, collect the minimum information needed for the feature, be clear about how it is used, and give developers the controls they need to handle consent and privacy properly.

      Some of this varies by integration. For example, the HISE package can report plugin-open and SoundSync interface events, while licensing integrations naturally generate activation and validation events whenever they communicate with SoundSync.

      posted in General Questions
      soundsyncS
      soundsync
    • Using customer data to grow a plugin business

      Hey Gang,

      Just wanted to drop in with a post I thought some might find useful.

      When someone buys and uses a plugin, useful information is created across the store, licensing system, email platform, and the plugin itself.

      Connecting that information makes marketing & servicing much more useful. Instead of sending the same emails to everyone, developers can create:

      • Marketing emails: Send product announcements, educational content, updates, and offers to the appropriate customers.
      • Growth flows: Automate cart recovery, post-purchase follow-ups, review requests, customer rewards, upgrade campaigns, and re-engagement emails.
      • Segmentation: Group customers by products owned, purchase history, license status, activation activity, installed version, or engagement.
      • Personalization: Adjust email content and offers based on what each customer owns and how they interact with the product.
      • Cross-selling: Recommend compatible expansions, sound packs, or related plugins while excluding customers who already own them.
      • Customer retention: Identify inactive customers and send relevant education, updates, or incentives to bring them back.
      • Product updates: Notify only the customers affected by a release, compatibility change, or important fix.
      • Analytics: Connect campaigns to purchases, activations, product use, reviews, and repeat sales instead of measuring email clicks alone.

      This is especially useful for smaller plugin companies because these tasks can run automatically instead of requiring someone to manually manage lists and customer records.

      It is not about collecting every possible piece of information. It is about making the information you already have useful. Purchase, license, activation, and product data can help make emails & servicing more relevant and show what is actually helping the business grow.

      This is one of the larger ideas behind SoundSync. We are connecting the store, customer accounts, licensing, plugin activity, marketing emails, growth flows, and analytics so developers can manage the customer journey from one connected system.

      posted in General Questions sell plugins customers growth licensing
      soundsyncS
      soundsync