> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/commercial-lending/getting-started/concepts/products-and-product-categories.md).
# Products and product categories
Learn how a loan product inherits its configuration from a product category and when it can be used.
A **product category** is the template a loan runs on. It owns the intake fields, checklist, credit policies, memo template, wizard configuration, and covenant categories that apply to loans in the category. The categories are CRE, C\&I, and ICRE.
A **loan product** is created from a category, which sets its starting configuration. Every application created from the product inherits its intake, stages, checklist, credit policies, disclosures, and memo.
A product must be both **Active** and **Published** before new applications can use it. Saving a change to an existing product moves it to Draft; publish the product for the change to reach live applications.
Different product categories drive different UI shapes for the same features.
## Related
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/commercial-lending/getting-started/concepts/products-and-product-categories.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
