> 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/the-add-to-cart-button-is-missing.md). # The Add to cart button is missing What to check when the Add to cart button is missing from a Volume product page, and how the sticky buy bar works. Most of the time the button is not broken — either a theme setting has switched selling off, or Shopify is refusing to sell the product. Work down this list. ### Shopping is switched off theme-wide Start here, because it is the fastest to check and the easiest to hit by accident. **Theme settings → Cart → Disable shopping functionality** turns the whole store into a catalogue: every buy button disappears and the cart icon vanishes from the header. If your header has no cart icon either, this is your answer. ### The Buy buttons block was removed The button itself lives in the **Buy buttons** block inside the **Product overview** section. If someone rebuilt the template, or the product uses a template where the block was never added, it is simply not there. Open the Theme Editor, check the block list and re-add it. {% hint style="warning" %} A block can also be present in the editor and absent on the live store if the product is being viewed in a market that has its own template file. See [I added a block but it does not show on the product page](/docs/volume-themes/faq/products-and-variants/i-added-a-block-but-it-does-not-show-on-the-product-page.md). {% endhint %} ### The product is unavailable Shopify hides the buy button when the selected variant is out of stock with **Continue selling when out of stock** switched off, when the product has no active sales channel, or when it is not published to the Online Store. Check the product's **Publishing** panel and its inventory settings. ### There is no valid variant selected If a product has options but the chosen combination does not exist — a size that is not made in that colour, for instance — there is nothing to add. Pick a combination that exists and see whether the button returns. ### An app is in the way Subscription, pre-order, bundle and "request a quote" apps commonly replace or hide the native button. Disable the app's embed temporarily and reload. ### The sticky buy bar The **Product overview** section has its own **Sticky 'Add to Cart'** group of settings, separate from the **Buy buttons** block: **Enable**, **Show** (**Both**, **Desktop** or **Mobile**), **Desktop position**, **Show image**, **Show outline** and a colour scheme. So if the bar follows the scroll but the in-page button is missing, the block is gone; if the in-page button works but nothing follows the scroll, **Enable** is off or **Show** is set to the other device. {% hint style="warning" %} The **Buy buttons** block also carries the dynamic checkout buttons — Shop Pay, PayPal and the rest — behind **Show dynamic checkout buttons**. Those only render once the corresponding accelerated checkouts are enabled under **Settings → Payments**, so an empty gap under Add to cart usually means none are active. {% endhint %} {% hint style="success" icon="lightbulb" %} See [Product page](/docs/volume-themes/products/product-page.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/the-add-to-cart-button-is-missing.md?ask=&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.