> ## Documentation Index
> Fetch the complete documentation index at: https://www.billingserv.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Software License Management Setup Guide

> Set up software license management in BillingServ to sell software, issue licence keys, manage activations, and control digital access.

This guide is for software businesses that need software license management for downloads, licence keys, activations, and customer access.

You will create a software package, enable digital delivery, configure licence rules, test the activation lifecycle, and prepare a support process for access issues.

## Before you start

Decide the software package and release files, billing cycle, licence key prefix and length, activation limit, reissue policy, customer licence-management rules, and any domain, IP, installation-path, or offline restrictions.

## 1. Create the software package

Open **CMS > Packages** and create a group such as **Software**. Add a package for the product.

Set the product name, description, price, billing cycle, tax class, and any trial or setup fee. Explain the licence terms in the description or attach the relevant documentation to the package.

See [Packages](/docs/cms/packages) for the package setup process.

## 2. Enable digital delivery

Add the software files to the package and enable digital delivery. Configure the download policy, link expiry, and download limit if needed.

Test the download separately from activation. A customer may be able to download a release but still fail activation if the licence settings or application request are wrong.

For the download workflow, see [Digital Downloads Setup Guide](/docs/guides/digital-downloads).

## 3. Configure licensing

In the package licensing settings, enable licensing and review:

* Activation limit
* Licence key prefix and length
* Customer licence management
* Maximum reissues
* Domain, IP, and installation-path enforcement
* Offline cache duration

Use settings that match the way your application works. A licence intended for one installation should not have an activation limit that allows unlimited devices.

## 4. Document the activation flow

Before launch, write down what should happen:

1. The customer completes an order.
2. BillingServ creates the licence record.
3. The customer downloads the software or receives the key.
4. The application sends an activation request.
5. BillingServ checks the licence and activation limits.
6. The application stores the response and applies the correct access state.

Also decide what happens when a customer deactivates a device, reaches the limit, requests a reissue, or works offline.

## 5. Test the licence lifecycle

Use a test package and test customer to check new licence creation, successful activation, activation at the limit, deactivation and reactivation, reissue, expiry, suspension, revocation, restricted installation details, and offline activation expiry.

Use [Licensing and Digital Downloads](/docs/reports/digital-delivery-licensing) to review stored licence status, activation count, latest activation time, and expiry date.

## 6. Prepare support

Software customers may change devices, reinstall the application, or lose access to an old installation. Give staff a simple process for checking the customer, order, package, licence status, active activation count, latest activation time, and expiry date.

For the support workflow, see [Support overview](/docs/support/support) and [Support Tickets](/docs/support/support-tickets).

## Next steps

If you are comparing software licensing platforms with billing, downloads, licence keys, and activation controls, see how [BillingServ supports software licensing](https://www.billingserv.com/use-cases/software-licensing/). If the software is sold as a recurring service, review the billing cycles and invoice settings in [Invoice Settings](/docs/settings/invoice).