> 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/hiding-prices/hide-selected-products.md).

# Hide prices for selected products

Hide prices on a specific list of products that you choose by hand.

Use this when a short list of products shouldn't show a price, and that list doesn't change often.

The setting covers the products themselves, so check a product page and a collection page after you save — themes show prices in more places than the product page.

{% hint style="info" %}
If the five options on the **Hide price** tab are greyed out with a padlock line reading "🔐 This feature is available on …", that is your plan rather than a fault. **Hide price** is listed under the **PREMIUM** plan. See [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md).
{% endhint %}

## Set it up

{% stepper %}
{% step %}

### Open the Hide price tab

In the app menu, open **Advanced settings** and select the **Hide price** tab. The card at the top is headed **Hide price?** and holds five options.
{% endstep %}

{% step %}

### Choose the specific products option

Select **Yes, hide prices for specific products**.
{% endstep %}

{% step %}

### Pick your products

Choosing that option reveals a new field below it, labelled **Choose the products whose prices you want to hide**. There are two ways to add to the list, and they open the same picker:

* Type into the field — it reads **Search products** until you do.
* Click **Browse products** to the right of the field, and select from your catalogue by hand. Use this when you would rather scroll a list than remember product names.

Each product you pick joins the list underneath the field, with its image beside it.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2FC45Ke2gpk8VsCvgNUAth%2Fimage.png?alt=media&amp;token=06978ee9-070e-4290-a623-9a73bf7505ba" alt=""><figcaption><p>Search your catalogue and pick the products this applies to.</p></figcaption></figure>
{% endstep %}

{% step %}

### Check and prune the list

Every product on the list shows a thumbnail and its title. The title is a link — it opens that product in your Shopify admin, so you can confirm you picked the right one. To take a product off the list, click the **X** at the end of its row.

A long list pages, so use the paging controls under the list rather than assuming what you see is everything.
{% endstep %}

{% step %}

### Save

**Save** is at the top of the window, not at the bottom of your product list. As soon as you change anything, Shopify's bar at the top reads **Unsaved changes**, with **Discard** and **Save** beside it. Click **Save**.
{% endstep %}

{% step %}

### Check it on your storefront

Open one of those products on your storefront in a private browser window, then open a collection that contains it. Both should show the product without a price.
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Nothing reaches your storefront until you save. If the top bar still reads **Unsaved changes**, your list has not been applied.
{% endhint %}

## What your customers see

The products you picked keep their page, their photos and their description. Only the price goes — on the product page, on collection pages, and anywhere else your theme lists products. Every product you didn't pick carries on showing its price as usual.

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

{% hint style="info" %}
A hidden price with no way to ask about it is a dead end for the customer. Show your quote button on those products so there is an obvious next step — see [Quote button on product pages](/sa-request-a-quote/collecting-quote-requests/button-on-product-pages.md).
{% endhint %}

## Keeping the list right

A hand-picked list is a list, not a rule. Nothing adds to it or removes from it on your behalf:

* A product you add to your catalogue next month is **not** covered until someone opens this tab and picks it.
* Duplicating a product in Shopify does not copy its place on this list.
* Removing a product from the list here does not change anything about the product itself — only whether its price is hidden.

That is the trade you are making for exact control. If it starts to feel like housekeeping, the conditions option maintains itself instead.

## When a hand-picked list is the right choice

<table><thead><tr><th width="300">Use a hand-picked list when</th><th>Use something else when</th></tr></thead><tbody><tr><td>Only a handful of products are affected.</td><td>Dozens of products are affected, or the set keeps growing — use <strong>Yes, hide prices for products that match conditions</strong> instead.</td></tr><tr><td>The products don't share a tag, a collection or anything else in common.</td><td>The same products are the ones you allow customers to quote — use <strong>Yes, hide prices for quoted products</strong> so the two settings stay in step.</td></tr><tr><td>You want to name the exact products yourself.</td><td>New products should be covered automatically, without anyone opening the app.</td></tr></tbody></table>

{% hint style="info" %}
Changing the set often? A condition maintains itself — you tag the product in Shopify and it is covered. See [Hide prices by tag](/sa-request-a-quote/hiding-prices/hide-by-tag.md).
{% endhint %}

{% hint style="warning" %}
Hiding a price does not stop a sale on its own. A customer can still use **Add to cart** or **Buy it now** and check out at a price they never saw. See [Hide Add to Cart and Buy now](/sa-request-a-quote/hiding-prices/hide-buy-buttons.md).
{% endhint %}

## If a price is still showing

<table><thead><tr><th width="320">What you see</th><th>What to check</th></tr></thead><tbody><tr><td>The price is still there on every product</td><td>The top bar was left reading <strong>Unsaved changes</strong>, or the five options are greyed out because of your plan.</td></tr><tr><td>The price is gone on some products but not others</td><td>Those products are not on the list. This option covers nothing but what you picked by hand.</td></tr><tr><td>The product page hides it but the collection grid doesn't</td><td>Send support your store URL and the collection URL — some themes render prices from markup the app has to be pointed at.</td></tr><tr><td>You can see the price but a customer says they can't, or the other way round</td><td>Check whether <strong>Require login to show price</strong> is ticked in the <strong>Login to show price</strong> section below the options. See <a href="/sa-request-a-quote/hiding-prices/login-to-show-price.md">Require login to show price</a>.</td></tr></tbody></table>

## Next steps

* [Hide Add to Cart and Buy now](/sa-request-a-quote/hiding-prices/hide-buy-buttons.md) — also take away the buy buttons
* [Hide prices by tag](/sa-request-a-quote/hiding-prices/hide-by-tag.md) — a lower-maintenance alternative
* [Hiding prices overview](/sa-request-a-quote/hiding-prices/overview.md) — the other four hide price options


---

# 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/hiding-prices/hide-selected-products.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.