Sell plugins, downloadable software, and license keys from your own site.

Why plugin sales need both files and entitlement

A plugin buyer usually needs two things after checkout: the installer or downloadable file, and proof that they are allowed to use it. That proof might be a license key, serial number, activation code, or product-specific entitlement your software checks later.

If those pieces live in separate tools, support gets painful quickly. The order is in one place, the key list is in another, the file is somewhere else, and the buyer email is in a payment processor. Zwely keeps the commercial context together so you can answer the normal support questions: who bought it, which product, which key, and whether the order is still active.

That makes Zwely useful for solo developers, small software shops, audio plugin makers, template sellers, and creators who want a real software selling workflow without building an internal commerce system first.

License key assignment after checkout

For products that require a license, Zwely can assign a key from the product's license pool when checkout completes. That key can be included in the customer delivery email along with the download button, so the buyer receives the pieces they need in one place.

Keeping keys product-scoped is important. A license intended for one plugin shouldn't accidentally unlock another product. Product-level key pools make the assignment clearer, and they make validation safer when your app checks a key later.

This also helps with support. When a buyer asks for their key, you can look at the order and see the assigned license without searching through raw files or spreadsheets.

Refunds, support, and customer expectations

Software refunds create edge cases. A buyer might request a refund after receiving a key, lose an email, reinstall a plugin, or enter a license key into the wrong product. The selling system needs to keep enough context for you to respond clearly.

Zwely links orders, customers, products, license keys, payment status, delivery settings, and refunds. It doesn't expose raw card details or secrets, but it does give you the operational context you need to handle support.

That context is what separates a real software checkout workflow from a plain download link. Buyers get a clean email, and you get a record you can trust.

Compatibility, versions, and install notes

Software buyers need to know whether the product will work for them. State supported operating systems, host apps, plugin formats, framework versions, dependencies, update policy, and any known limitations before checkout.

Zwely handles payment, file delivery, and license assignment, while your product copy gives buyers technical confidence. Clear compatibility notes reduce refunds and make support feel more professional.

Designing a calmer activation experience

Activation should not feel like punishment for paying. Ask for the license key, optionally ask for the customer email, show a useful error when validation fails, and explain what to do if the buyer cannot find their key.

Because Zwely's validation statuses are more specific than a generic failure, your app can provide better messages. A refunded order, an email mismatch, and a missing key should not all produce the same confusing error.

Developer documentation as part of the product

If your plugin uses license validation, your own docs matter too. Buyers need to know where to paste the key, what happens during activation, and how to contact you if they reinstall or change machines.

Zwely provides API docs for the commerce and validation side. Your product docs should translate that into buyer-facing instructions, activation screenshots, troubleshooting notes, and plain-language licensing terms.