> 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/button-on-collection-pages.md).

# Quote button on collection pages

Show the quote button on every product card in your collection pages so customers can request several items quickly.

A quote button on each product card lets customers add several products without opening every product page. It suits stores where buyers order a list of items at a time.

Like the product page button, this is a single dropdown with a handful of positions.

## Set the position

{% stepper %}
{% step %}

### Open the button settings

In the app, go to **Quote settings** and click **Customize**, then open the **Button & widget** tab.
{% endstep %}

{% step %}

### Find Button position

Scroll to **Button position** and open the **Collection page button position** dropdown.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2FTAUEBPq48RswclJelZfd%2Fimage.png?alt=media&amp;token=36487119-0a8f-4064-8554-920382cb10f1" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Choose where the button goes

Pick the option that fits your product cards — see the table below.
{% endstep %}

{% step %}

### Check the preview, then save

Use the desktop and mobile toggle in the **Preview** panel, because product cards are tight on a phone. Save your changes, then open a collection on your storefront.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-f2f58daa2c64e7efe96d64f515242fad8ee644d8%2FScreenshot%202026-09-29%20at%2014-41-43.png?alt=media" alt="A storefront collection page with an Add to Quote button under each product card"><figcaption><p>The button on a live collection page, under every product card.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## What each position does

<table><thead><tr><th width="290">Option</th><th>What customers see</th></tr></thead><tbody><tr><td><strong>Below product card button</strong></td><td>The quote button sits under whatever button your theme already puts on the card.</td></tr><tr><td><strong>Below product price</strong></td><td>The quote button sits directly under the price, higher up the card.</td></tr><tr><td><strong>Replace product card button</strong></td><td>The quote button takes the place of the card's own button, so quoting is the only action.</td></tr><tr><td><strong>Don't show on collection pages</strong></td><td>No quote button on collection pages. Customers open a product page to quote.</td></tr></tbody></table>

{% hint style="info" %}
Products on a collection page often have several variants. If customers need to choose a size or finish before adding, turn on **Show variant selector** — see [Show a variant selector](/sa-request-a-quote/collecting-quote-requests/variant-selector.md).
{% endhint %}

## Your theme may only show the button on hover

Where the button lands on a product card is partly up to your theme. A theme can attach it to its own quick-add control, and when it does, the button sits invisible until the shopper hovers over the product card — and it appears as a small icon rather than as your **Button text**.

So if you set a position, save, open a collection page and see nothing at all, hover a product card before you decide something is broken.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-ab76953a7e48f6ea8a0b39b5f408ba4c2198ac35%2FScreenshot%202026-09-30%20at%2017-03-16.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
There is no hover on a phone. Check a collection page on your own mobile as well as on a desktop, and if the button is hard to find there, collect quotes from product pages instead — see [Quote button on product pages](/sa-request-a-quote/collecting-quote-requests/button-on-product-pages.md).
{% endhint %}

## This is a separate setting

**Product page button position** and **Collection page button position** are independent. Setting one does nothing to the other.

If the button shows on product pages but not in your collection grid, this dropdown is usually the one you haven't set. If it is already set, check whether your theme is only showing the button on hover, as above.

## Next steps

* [Show a variant selector](/sa-request-a-quote/collecting-quote-requests/variant-selector.md) — let customers pick a variant from the card
* [Set the after-click behavior](/sa-request-a-quote/collecting-quote-requests/after-click-behavior.md) — what customers see after clicking
* [Floating quote widget](/sa-request-a-quote/collecting-quote-requests/quote-widget.md) — let customers see everything they have collected


---

# 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/button-on-collection-pages.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.