> 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/collecting-quote-requests/overview.md).

# Collecting quote requests overview

The ways customers can start a quote in your store, and where every one of those settings now lives.

Before a customer can ask you for a price, they need somewhere to ask from. Nearly everything that decides where and how they can ask sits in one place: **Quote settings**.

## Where these settings live

In the app, open **Quote settings**. The page is headed **Request a Quote** — "Customize the quote experience and choose which products will show the RFQ button." It has three parts:

<table><thead><tr><th width="230">Section</th><th>What it is for</th></tr></thead><tbody><tr><td><strong>Customize</strong></td><td>"Design how your request a quote experience will look to customers. Set button behavior, quote form, quote cart, widget, colors and messages." The <strong>Customize</strong> button opens a full-screen editor.</td></tr><tr><td><strong>Preview</strong></td><td>A quick look at the result, with <strong>Online store</strong>, <strong>Cart</strong> and <strong>Quote list</strong> tabs.</td></tr><tr><td><strong>Select quote products</strong></td><td>"Select products or collections that should show the Request a Quote button."</td></tr></tbody></table>

The **Customize** section also shows the state you are currently in at a glance: **Active now**, **Visibility**, **Product page**, **Collection page** and **Cart page**.

{% hint style="info" %}
The **Preview** section carries its own note: "Preview is only for quick checking. Full settings and detailed preview are inside Customize." Treat it as a sanity check, not as the place to make changes.
{% endhint %}

## The four tabs inside Customize

Click **Customize** and you get an editor with four tabs:

* **Button & widget** — the quote button's text, what clicking it does, where it appears, who can see it, and how it looks.
* **Quote form** — the fields customers fill in.
* **Quote cart page** — the customer's quote cart, the storefront pages, and the floating quote widget.
* **Success message** — what customers see once a request has been sent.

Most of the pages in this section are about the **Button & widget** tab.

## Choose your entry points

<table><thead><tr><th width="230">Entry point</th><th width="280">Best when</th><th>Set it up</th></tr></thead><tbody><tr><td>Button on product pages</td><td>Customers decide product by product. The most common choice.</td><td><a href="/sa-request-a-quote/collecting-quote-requests/button-on-product-pages.md">button-on-product-pages.md</a></td></tr><tr><td>Button on collection pages</td><td>Customers order several items at once and shouldn't have to open each product.</td><td><a href="/sa-request-a-quote/collecting-quote-requests/button-on-collection-pages.md">button-on-collection-pages.md</a></td></tr><tr><td>Button on the cart page</td><td>Customers fill a cart first, then decide they would rather ask for a price.</td><td><a href="/sa-request-a-quote/collecting-quote-requests/add-cart-items.md">add-cart-items.md</a></td></tr><tr><td>Form on the product page</td><td>You sell one custom item at a time and want the fewest possible clicks.</td><td><a href="/sa-request-a-quote/collecting-quote-requests/form-on-product-pages.md">form-on-product-pages.md</a></td></tr><tr><td>Floating quote cart widget</td><td>Customers build a list while browsing and need to reach it from any page.</td><td><a href="/sa-request-a-quote/collecting-quote-requests/quote-widget.md">quote-widget.md</a></td></tr></tbody></table>

Each of the three button positions is its own dropdown, so you can show the button in one place, all three, or none.

## Then decide the details

* [Choose quotable products](/sa-request-a-quote/collecting-quote-requests/choose-products.md) — which products show the button at all
* [Set the after-click behavior](/sa-request-a-quote/collecting-quote-requests/after-click-behavior.md) — what happens the moment a customer clicks
* [Change button text and colors](/sa-request-a-quote/collecting-quote-requests/change-button-style.md) — the wording and the look of the button
* [Require login to quote](/sa-request-a-quote/collecting-quote-requests/require-login.md) — who is allowed to see and use it
* [Show a variant selector](/sa-request-a-quote/collecting-quote-requests/variant-selector.md) — letting customers pick a variant before adding
* [Let customers propose a price](/sa-request-a-quote/collecting-quote-requests/customer-price.md) — letting customers name the price they want

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2FYxMCCpZSlpiwEozcKoDm%2Fimage.png?alt=media&amp;token=ca6b5892-8595-41ef-95c1-703df3619391" alt=""><figcaption><p>The <strong>Setup guide</strong> on the dashboard links straight to <strong>Quote settings</strong> with <strong>Open settings</strong>.</p></figcaption></figure>

{% hint style="warning" %}
None of this appears on your storefront until the app embed is enabled in your theme. The dashboard tells you which state you are in — **App embed is enabled** or **App embed is disabled**. If a setting looks right but nothing shows, start with [enable-app-in-theme.md](/sa-request-a-quote/getting-started/enable-app-in-theme.md).
{% endhint %}

## Next steps

* [Quote button on product pages](/sa-request-a-quote/collecting-quote-requests/button-on-product-pages.md) — the usual place to start
* [Choose quotable products](/sa-request-a-quote/collecting-quote-requests/choose-products.md) — decide which products can be quoted
* [Quote form overview](/sa-request-a-quote/quote-form/overview.md) — design what customers fill in


---

# 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/collecting-quote-requests/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.