> 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/retail-los-overview.md).
# Overview
Understand Retail LOS, its users, products, and tenant model.
Retail LOS is a digital account opening and lending system for Financial Institutions (FIs), including credit unions. A customer opens deposit accounts, or applies for a loan, credit card or line of credit, online. One application can cover both. The system checks who they are, pulls credit, makes a decision, builds offers, collects the signature and passes the file to funding. FI staff manage all of this in the staff portal.
> **Retail LOS manages the complete journey, from opening accounts to lending.** Applicants apply online while FI teams configure, decide, close, and fund in the staff portal.
{% columns %}
{% column %}
#### Applicant journey
Apply, verify identity, provide documents, receive offers, accept, and sign.
{% endcolumn %}
{% column %}
#### FI operations
Configure products and workflows, review applications, manage users, and monitor activity.
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
The applicant, staff, and partner portals support different users. Product and role configuration controls their experience.
{% endhint %}
### Where each audience works
Retail LOS gives each audience its own area. What each one sees depends on the role and on how your FI configures the products.
| For | Where they work | What they do |
| ------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **For Applicants** | The applicant portal | Apply, upload documents, accept an offer and sign. Your FI changes what it asks and shows through configuration. |
| **For FI Staff** | The staff portal, also called the back office | Review and decide applications. Administrators also configure products, manage users and roles, and see logs and reports. |
| **For Partners (Broker)** | The partner portal | Submit deals for customers. |
| **For Technical Teams** | **Settings** and **Logs** in the staff portal, and the integrations behind Retail LOS | Connect integrations, manage API keys and agents, and trace calls and errors. |
Behind all of these, Retail LOS runs the decisions, workflows, offers, integrations and data. Staff never see that layer directly. Technical teams meet it through integrations, API keys, agents and logs.
| Experience | Primary focus |
|---|
| Applicant portal | Apply, upload documents, accept offers, and sign. |
| Staff portal | Configure products, process applications, and oversee operations. |
| Partner portal | Submit customer deals through broker workflows. |
### Who uses it
| User | What they do |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
| Customer or business owner | Applies, uploads documents, accepts an offer, signs. |
| Co-borrower, co-owner, guarantor | Invited by the main applicant to finish their own part on their own device. |
| Partner | Submits deals for customers through the partner portal. |
| Loan officer, banker, relationship manager | Brings in applications and documents, follows up with the customer. |
| Underwriter, senior underwriter | Reviews files the system refers, approves or declines, overrides rates and tiers within their authority. |
| Closer or funder | Prepares the contract and funding after approval. |
| Compliance officer | Oversees notices, consents and audit trails. |
| FI Administrator (Tenant Administrator) | Configures products, workflows, integrations, users and roles. The only role that can configure a product by default. |
### What a customer can apply for
{% tabs %}
{% tab title="Credit products" %}
* Choose one credit product: personal loan, business term loan, auto loan, credit card, line of credit, or equipment finance.
* One application can include one credit product.
{% endtab %}
{% tab title="Deposit accounts" %}
* Choose checking, savings, money market, or several deposit accounts.
* An application can combine a credit product with any number of deposit accounts.
* See [Account Opening](/retail-lending/account-opening.md) for how an applicant opens an account and where each setting lives.
{% endtab %}
{% endtabs %}
{% hint style="success" %}
Individuals and businesses use the same portal. The questions adapt to the applicant type.
{% endhint %}
### Each FI runs its own copy
Each FI (a "tenant") has its own database, products, workflows and integration settings. Some things are shared by all FIs, such as the standard applicant form, the Document Registry, the permission list and the product types. [Configure a product](broken://pages/h1BRHsVc3cwuzs0gW1IM) shows which is which.
| FI-specific | Shared across FIs |
| --------------------------------------------------- | -------------------------------------------------------------------------- |
| Database, products, workflows, integration settings | Standard applicant form, Document Registry, permission list, product types |
***
{% 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/retail-lending/retail-los-overview.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.
