> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/quote-form/overview.md).

# Quote form overview

Where the quote form lives, what it can collect, and how the form builder is organised before you start changing things.

The quote form is what a customer fills in to send you a request. Everything about it — which template you start from, which questions you ask, and how it looks — is set in one place.

## Where to find it

Open **Quote settings**. The page heading is **Request a Quote**, and the first card is **Customize**:

> Design how your request a quote experience will look to customers. Set button behavior, quote form, quote cart, widget, colors and messages.

Click **Customize** to open the full-screen editor. It has four tabs — **Button & widget**, **Quote form**, **Quote cart page** and **Success message**. Everything on this page is on the **Quote form** tab.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fk2DUk3Nun3MioRLAtwd9%2Fimage.png?alt=media&amp;token=d3566356-6795-4f6a-9a48-8c4256b3d464" alt=""><figcaption><p>Every form in the app is built on this one screen.</p></figcaption></figure>

## How the Quote form tab is organised

<table><thead><tr><th width="250">Section</th><th>What it controls</th></tr></thead><tbody><tr><td><strong>Form template</strong></td><td>The template your form starts from, for example <strong>B2B customer form</strong>. <strong>Change</strong> opens the template picker.</td></tr><tr><td><strong>Product page form display</strong></td><td>"Show the quote form directly on product pages." Controlled by the <strong>Enable product page form display</strong> checkbox.</td></tr><tr><td><strong>Form builder</strong></td><td>The questions themselves, grouped into sections. <strong>Add element</strong> adds a field to a section; <strong>Add section</strong> adds a whole new one.</td></tr><tr><td><strong>Style</strong></td><td>The style preset, and the <strong>Match theme styling if possible</strong> checkbox.</td></tr><tr><td><strong>Customize text</strong></td><td><strong>Font style</strong> for the form.</td></tr><tr><td><strong>Customize form color</strong></td><td>Title bar color, Title bar background, Color, Background color, Border color and Quote popup primary color.</td></tr></tbody></table>

## Start from the right template

**Form template** sits at the top of the tab, and it decides what the rest of the tab looks like. There is more than one template to choose from, and **Change** opens the picker.

<table><thead><tr><th width="230">Template</th><th>How the app describes it</th></tr></thead><tbody><tr><td><strong>Detailed quote form</strong></td><td>"For custom orders, delivery, installation, or project-based quotes. Includes login autofill guidance."</td></tr><tr><td><strong>B2B customer form</strong></td><td>"For wholesale or business buyers who need company, shipping, billing, and payment term information"</td></tr></tbody></table>

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2F42XwcikENKHmHE0M3N56%2Fimage.png?alt=media&amp;token=0bf472f5-ba61-405b-a547-9af8e8e69fae" alt=""><figcaption><p><strong>Change</strong> opens the picker and the template decides the rest of the tab.</p></figcaption></figure>

{% hint style="warning" %}
Changing the template **replaces the current field list**. The sections and fields you are looking at are swapped for the new template's own, so anything you added, renamed or deleted goes with them. Choose your template first, then customize it.
{% endhint %}

## The sections in the Form builder

The sections in the builder are the ones your template brought with it, so this list is not the same on every store.

<table><thead><tr><th width="230">Template</th><th>Sections it arrives with</th></tr></thead><tbody><tr><td><strong>Detailed quote form</strong></td><td>Contact information · Shipping address · Extra info</td></tr><tr><td><strong>B2B customer form</strong></td><td>Contact information · Company information · Shipping address · Billing address · Payment terms · Extra info</td></tr></tbody></table>

Each section expands so you can see and edit the fields inside it.

<table><thead><tr><th width="230">Section</th><th>What it collects</th></tr></thead><tbody><tr><td><strong>Contact information</strong></td><td>First name, Last name, Email address, Phone number, Address</td></tr><tr><td><strong>Company information</strong></td><td>Company name</td></tr><tr><td><strong>Shipping address</strong></td><td>Country/region, First name, Last name, Company/attention, Address, Apartment suite etc, City, Postal code, Phone number</td></tr><tr><td><strong>Billing address</strong></td><td>A <strong>Billing address same as shipping address</strong> checkbox, then the same fields again</td></tr><tr><td><strong>Payment terms</strong></td><td>Payment terms, a <strong>Required deposit</strong> checkbox, and Deposit</td></tr><tr><td><strong>Extra info</strong></td><td><strong>Message</strong> on the <strong>B2B customer form</strong>; <strong>Project detail</strong> and <strong>Delivery service</strong> on the <strong>Detailed quote form</strong> — plus anything else you add yourself</td></tr></tbody></table>

{% hint style="info" %}
It isn't only the list of sections that changes with the template — the fields inside them change too. **Extra info** is the clearest example: the **Detailed quote form** puts **Project detail** and **Delivery service** there, because a project quote needs to know what the job is and how it gets delivered. The **B2B customer form** has neither.
{% endhint %}

{% hint style="info" %}
If the **Form builder** controls are greyed out with a padlock line reading "🔐 This feature is available on …", that is your plan, not a fault. Open **Pricing plans** in the app to see what your plan includes.
{% endhint %}

## What lives on the other tabs

Two things merchants often look for on the **Quote form** tab are actually on **Quote cart page**:

* **Enable Quote Sections** — "Lets customers group the products in their quote cart into named sections."
* **Quote form appearance** — "Controls how the quote form looks on the quote cart page." Choose **Multiple step** or **Single page**.

The wording and placement of the quote button itself is on **Button & widget**.

## Where to start

* [Build a standard form](/sa-request-a-quote/quote-form/build-standard-form.md) — build your form end to end
* [Build a B2B form](/sa-request-a-quote/quote-form/build-b2b-form.md) — the B2B customer form, with company, billing and payment terms
* [Customer information fields](/sa-request-a-quote/quote-form/customer-info-fields.md) — contact and address details
* [Quoted product group](/sa-request-a-quote/quote-form/product-group.md) — let customers split a quote into named sections
* [Allow file uploads](/sa-request-a-quote/quote-form/file-uploads.md) — which file types the app accepts, and the storage uploads use
* [Match your theme style](/sa-request-a-quote/quote-form/match-theme-style.md) — make the form look like the rest of your store
* [Add reCAPTCHA](/sa-request-a-quote/quote-form/recaptcha.md) — stop spam submissions

## Ask for less than you think

Every field you add is a reason to abandon the form. Ask for what you genuinely need to produce a price — usually contact details, quantities and one free-text box. You can always follow up by email.

## Next steps

* [Build a standard form](/sa-request-a-quote/quote-form/build-standard-form.md) — start building
* [Collecting quote requests overview](/sa-request-a-quote/collecting-quote-requests/overview.md) — where customers reach this form from


---

# 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.samita.io/sa-request-a-quote/quote-form/overview.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.