> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/faq/cart-and-checkout/how-do-i-run-the-store-as-a-catalogue-without-checkout.md).

# How do I run the store as a catalogue, without checkout?

What Disable shopping functionality switches off in Volume, what it leaves visible, and the two buttons you have to turn off yourself.

Volume has one switch for this: **Theme settings → Cart → Disable shopping functionality**. It is off by default. Turning it on puts the whole store into browse-only mode in a single move — no need to unpublish products, strip templates or install an app.

Typical reasons to use it: a wholesale catalogue where pricing is agreed off-site, a brand site that sends people to stockists, a store whose checkout is not set up yet, or a product range that cannot legally be sold online in some markets.

### What it switches off

<details>

<summary>The full list</summary>

* the **Buy buttons** block on the product page, including the dynamic checkout buttons;
* the buy button inside **Quick view**;
* the cart icon in the header and in the **Mobile dock**;
* the cart drawer and the cart notification popup;
* the whole **Quick order list** section — it stops rendering and its settings are hidden in the editor;
* the buy buttons inside **Shoppable media slider** and the video reels slideshow.

</details>

It is a theme-level switch, so it applies to every product at once. There is no per-product or per-collection version of it.

### What it leaves alone

**Prices stay visible.** That is deliberate — most stores using this want a price list without a checkout. The `/cart` page also still exists, it is simply no longer linked from anywhere.

If you want the prices gone too, turn off **Show price** in the **Price** block on the product page, and hide the price on cards from **Theme settings → Product card**.

{% hint style="warning" %}
**Two buy buttons are not covered by this setting and have to be turned off by hand.**

* **Quick buy on product cards.** Collection pages keep showing the quick-buy button on every card, and on a product with several variants it opens a Quick view that then has no buy button in it. Set **Theme settings → Product card → Quick buy** to **Disable**.
* **The sticky Add to cart bar.** In the **Product overview** section, under **Sticky 'Add to Cart'**, turn **Enable** off.
  {% endhint %}

{% hint style="success" icon="lightbulb" %}
If you only want to stop selling a handful of products rather than all of them, leave this setting alone — unpublish those products from the Online Store sales channel, or give them a product template that has no **Buy buttons** block.

If the button vanished and you did **not** set this, work through [The Add to cart button is missing](/docs/volume-themes/faq/cart-and-checkout/the-add-to-cart-button-is-missing.md).
{% endhint %}


---

# 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://staylime.com/docs/volume-themes/faq/cart-and-checkout/how-do-i-run-the-store-as-a-catalogue-without-checkout.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.