Set up a software product
Software products cover SaaS, apps, browser tools, and licensed software access. Buyers expect a login page, download link, or automated account creation after payment.
Use this guide when you sell access to software rather than courses, communities, or professional services.
When a software product fits
| Use a software product when | Use another product type when |
|---|---|
| Buyers receive app or SaaS access | The offer is professional services. See service product setup. |
| Delivery is login, download, or license URL | Buyers receive a PDF ebook. See ebook delivery. |
| You may integrate access via callback or webhooks | Lessons live in a members area. See course product setup. |
Full setup workflow
- Confirm you are in the correct business workspace.
[Screenshot: App header showing the active business name and workspace switcher.]
- Open Products and start a New product.
[Screenshot: Products list page with New product button visible.]
- On What will you sell?, select Software.
[Screenshot: Product type selector — Software tile selected; subtitle reads "SaaS, apps, etc."]
- Complete product details: name, description, category, and sales page URL.
[Screenshot: Software product details form — name, description, category, and sales page URL.]
- Configure delivery: usually Link delivery or external access instructions.
[Screenshot: Software delivery settings — link delivery selected with access URL fields.]
- Add labeled links for login, signup, download, API docs, or mobile app store.
[Screenshot: Delivery links for software — labels such as "Web app login", "Create account", and "Download desktop app".]
- If access is automated through an external system, configure callback URL or webhooks as required.
[Screenshot: External callback or webhook configuration tied to software access provisioning.]
- Save the product and complete product approval details.
[Screenshot: Product approval section describing the software offer and access method.]
- Create the plan and offer. Software is often subscription-based.
[Screenshot: Subscription plan for software — monthly or annual billing connected to the product.]
- Create a checkout link.
[Screenshot: Checkout link for the software product with copy button.]
- In the checkout builder, explain login steps, account creation, and supported platforms.
[Screenshot: Checkout preview with software access instructions and published status.]
- Run a test purchase and confirm approved status in Sales.
[Screenshot: Approved software test sale in Sales.]
- Confirm the buyer can log in, create an account, or download as promised.
[Screenshot: Software login or account creation screen after test purchase access.]
- If subscriptions control access, test renewals, cancelation, and overdue behavior.
[Screenshot: Subscriptions detail — renewal, cancelation, or overdue state tested for software access.]
Delivery options for software
| Option | Use it when |
|---|---|
| Link delivery | Buyers use URLs for login, signup, download, or docs |
| External members callback URLs | Your app provisions accounts from sale events |
| Webhooks | Your backend creates licenses when payment is approved |
| No members area | Access is fully manual during early beta |
What to verify before launch
| Check | Why it matters |
|---|---|
| Login/signup URLs work on mobile and desktop | Software buyers often test immediately after paying |
| Checkout explains whether buyer must create an account | Reduces "I paid but cannot log in" tickets |
| Subscription access rules are defined | Cancel or overdue should match product policy |
| Test sale used the same email flow buyers will use | Account matching issues are common |
Best practices
- Label primary login separately from docs and download links.
- Document whether access is instant on approval or requires manual provisioning.
- Use webhooks for reliable account creation instead of manual checks alone.
- Align subscription billing with license duration in your app.
Common mistakes
- Sending buyers to a login page without explaining they must register first.
- Using staging app URLs in production delivery links.
- Promising API or multi-seat access without configuring the right plan.
- Testing checkout but not the actual software account path.
FAQ
Should software use link delivery or webhooks?
Use link delivery when buyers self-serve into login or signup. Use webhooks or callback URLs when your app must create accounts automatically after an approved sale.
Can software be sold as a one-time license?
Yes. See one-time vs subscription pricing and define whether updates are included.
What if the buyer paid but cannot log in?
Start with troubleshoot buyer access after purchase, verify sale approval, buyer email, and whether account creation depends on a webhook.