> 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/retail-lending/release-notes/2026.md).

# 2026 Changelog

See what's new in Retail LOS.

{% updates format="full" %}
{% update date="2026-11-05" tags="new-feature" %}

## Initial release—November

Retail LOS ships the applicant experience, six lending products, decisioning and pricing, bank statement analysis, queues, and vendor integrations.

### Applicant experience

* Apply for several products in one application, sign in with a magic link, and invite co-applicants.
* Prefill with Plaid and Finicity, and upload documents that are read automatically.

### Products

* Configure Credit Card, Line of Credit, Unsecured Personal Loan, Business Term Loan, Scorecard Loan, and Auto Loan products.

### Configuration and decisioning

* Build application forms in Flow Designer and route outcomes in the visual workflow builder.
* Decide with the credit decision matrix and its simulator, and use scorecards.
* Manage document types in the document registry, with checklists.

<a href="/retail-lending/release-notes/2026/november.md" class="button primary" data-icon="readme">Read full update</a>

<details>

<summary>Also included</summary>

* **Pricing** — Rate card by tier, Prime-based variable rates, locked offers, and underwriter rate and term overrides.
* **Underwriting** — Bank statement analysis, debt-to-income, and bank-based income verification.
* **Operations** — Role-based application workspace, work queues, withdrawal and incompleteness handling, and identity reuse across applications.
* **Integrations** — Sumsub, Plaid, Finicity, Middesk, Cobalt, CRS, J.D. Power, PandaDoc, Resend, Azure email, Document AI, and TValue.

</details>
{% endupdate %}
{% endupdates %}

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% 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/retail-lending/release-notes/2026.md?ask=<question>&goal=<user_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.