Appearance
Products
Last updated: 2026–08-19
A product is a financing offer configured for your tenant: an application form, decision workflow, pricing, and branding bundled together as something a borrower can apply for. Product Studio is where products are built, versioned, and published. The Products list is where you see what’s currently configured and manage it day to day.
What’s on the Products list
Each row in the Products list shows:
- Name — the product’s display name.
- Referral code — a unique code identifying the product. This code appears in the application URL a borrower uses to apply (for example, a URL containing
/application/product/personal-loan_205). - Version — the version number currently set as the product’s default.
- Status — shows Published when the current draft matches what was last published. If someone has made changes since the last publish, the product shows as not yet in sync.
- Launch — only available once the product has at least one published version. A brand-new draft that has never been published cannot be launched.
- Active — whether the product is turned on. You can switch a product between active and inactive.
- Created by / Modified by / Last updated — audit information for the product.
- Application URL / Preview URL — links for testing the applicant-facing wizard for this product.
The list can be searched, sorted, and paged, so you can find a specific product by name.
Products are often configured at the tenant or platform level. Whether you can create, rename, or clone products from your account may depend on your role or tenant setup. Use the list to see what’s available and how products are referred to in Applications and Pricing Engine.
A note on referral codes
A product’s referral code is what identifies it in application URLs and in reporting. For a product that has a tenant-specific copy, the referral code can carry a numeric suffix that identifies which tenant the copy belongs to. Renaming a product only changes its display name — the referral code itself does not change, so links and integrations that point at that code keep working.
Product versions
A product can have more than one version. Open a product’s version list to see, for each version: the version number, a description, who last modified it, when, and whether it’s the version currently marked as default — the one applicants get when they start a new application.
From the version list you can:
- Update the version — set a different version as the product’s default. New applications start using it right away.
- Copy a version to a new draft — create an editable copy of a version so you can make changes without touching the version that’s currently live.
- Clone a version — duplicate a version’s configuration under a new description.
Worked example
Riverside FCU has a Personal Loan product live in Product Studio. Its referral code is personal-loan_205, it’s on version 3, and it’s marked Active with Status: Published. An underwriting manager wants to raise the minimum FICO band before rolling the change out to applicants.
- She opens Product Studio, finds Personal Loan, and opens its version list.
- She selects version 3 and copies it to a new draft. LendAPI creates a new version — version 4 — as an editable copy of version 3’s configuration, and confirms with “Product version copied.”
- She edits version 4 to raise the minimum FICO requirement.
- She uses the product’s Preview URL to walk through the application as a test applicant and confirms the new criteria show up correctly.
- Once she’s satisfied, she updates the product so version 4 becomes the default. LendAPI confirms with “Product version updated.” New applications now use version 4’s criteria.
- Version 3 stays in the version list, so she can refer back to it or revert if needed.
Use case
A multi-brand lender wants to offer the same loan product under two partner brands, each with its own logo and color scheme, without building the product twice.
- The lender configures the base product once in Product Studio — the application form, workflow, and pricing.
- The lender clones the product to create a second copy for the second brand. LendAPI confirms with “Product cloned.”
- Each of the two products is assigned its own white-label theme (logo, colors, background image) in Product Studio’s theme settings. A theme tracks how many products it’s applied to, so the lender can check that before making shared branding changes.
- Both products are marked Active, each with its own referral code and application URL, so each brand’s applicants land on the right look and feel.
Managing products
- Open Product Studio from the sidebar.
- To create a new product, use the create action. LendAPI confirms with “Product created.”
- To duplicate an existing product as a starting point, use the clone action and give it a new name. LendAPI confirms with “Product cloned.”
- To change how a product is labeled, use the rename action. LendAPI confirms with “Product renamed.” If the rename fails, the error message returned by the system is shown.
- To turn a product on or off, use the active/inactive toggle. LendAPI confirms with “Product status updated.”
Best practices
- Publish a version before expecting a product to be launchable — Launch stays unavailable until at least one version has been published.
- Copy a version to a new draft before you start editing, rather than working directly on the version marked default, so you can preview changes before they affect new applications.
- Check a theme’s assigned product count before changing shared branding — a theme can be applied to more than one product, and changes apply everywhere it’s used.
- Remember that renaming a product changes its display name only. Its referral code, and any application URL built from that code, stays the same.
Related pages
- Applications — see how products appear in the application list and filters.
- Pricing Engine — see how products are referenced in offer tables.