> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/common-scenarios/glossary/product-configuration-glossary.md).

# Product Configuration Glossary

### Product Bundles

[Product Bundles](/product-configuration/product-bundles.md) are a specific product type that combines multiple products together. This enables them to be activated and utilized with a single license, streamlining the licensing process.

![Product Bundle Detail Page](/files/b11b99f7bddd0f14491859744df33bda5e9e1617)

### Product Code/Name

When configuring a new application within LicenseSpring, you will be prompted to enter a "short code" known as the product code. These codes consist of a sequence of characters (minimum 2) and serve as a unique identifier for the product. Product codes are typically used for license checks and activations to identify the specific product associated with the license.

The product name, unlike the product code, does not need to be unique. It serves as a means for tracking and identifying a particular product within the LicenseSpring system. The product name provides a human-readable label or description for the product.

For more information, see [Product Configuration](/product-configuration/configuration.md).

### Product Custom Fields

[Product Custom Fields](broken://spaces/gLzurdfXUuKr9IziZWLz/pages/04fb863a7854c47fa79d0d183a229afc779f657e) are similar to license custom fields, with the distinction that the information is associated with the product itself. By default, all licenses associated with the product will inherit the product custom field values. However, if needed, these values can be overridden or customized at the license level using license custom fields.

### Product Versioning

Creating a new version of a product allows you to manage distinct releases of your product, enabling effective version control and management.

For more information, see [Product Versioning](/product-configuration/product-versioning.md).

![Creating a New Product Version](/files/1487a80f6d3a11da31823bbc4c25c90dbdd4265d)

#### Version Channel

Application channels act as conduits that enable the efficient and secure transfer of data between applications and the queue manager, allowing for seamless communication and facilitating the retrieval of installation files for software updates.

#### Version Release Date

The version release date represents the specific date on which a software version is officially launched or made accessible to users, enabling them to track the progression and evolution of a software product over time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.licensespring.com/common-scenarios/glossary/product-configuration-glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.