> 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/products-and-variants/i-added-a-block-but-it-does-not-show-on-the-product-page.md).

# I added a block but it does not show on the product page

Five reasons a block you added in the Volume theme editor does not appear on the live product page.

Work through these in order — the first two cover most cases.

### 1. You edited a template the product does not use

Volume ships several product templates — **Default product**, **simple-product**, **stretched-product**, **two-columns-product**, **preorder** and **quick-view** — and each keeps its own blocks, block order and settings. A product uses whichever one is set under **Product → Theme template** in the Shopify admin. If you added the block to **Default product** while the product is on **stretched-product**, nothing changes on that page. Check the assignment on the product itself, then edit the template it actually names.

### 2. The quick view is a different section entirely

Volume's quick view runs on the **quick-view** template, which uses its own section rather than **Product overview**. Nothing carries over from the product page. If a block is missing from the quick-view pop-up but present on the full page, add it again there: **Customize → template selector → Products → quick-view**.

### 3. It moved instead of disappearing — check Second container

Every block placed **below** the **Second container** block is pulled out into a separate container, and where that container lands is decided by **Layout** under the **Content** header of the **Product overview** section. Depending on the option chosen, your block may now be in the right-hand column, stretched below the gallery, or under the media rather than where you expected it. Scroll the whole page before assuming it is gone.

### 4. A market has its own copy of the template

If you use Shopify Markets, a market can have a context template such as `product.context.gb.json`. That copy has its own block order and its own settings, and it is what visitors from that market see — while the theme editor shows you the default. A block that exists in the editor but is missing on the live store for some countries is almost always this. Look for `*.context.*.json` files under **Edit code → Templates**.

### 5. The block is there, but the product gives it nothing to show

Several blocks render nothing when the data is missing, which looks identical to a block that was never added:

* **Variant picker** outputs nothing on a product with no variants, and **Theme settings → Variant picker → Hide option if only one variant exists** hides any option with a single value.
* **Linked products** needs the `custom.linked_products` metafield filled in on the product being viewed.
* The size guide is not a block at all — it is the **Size guide** group inside the **Variant picker** block, and it stays hidden until **Content from rich text** or **Content from page** is filled in.
* The gift-card recipient form is not a block either — it is **Show recipient information form for gift card products** inside the **Buy buttons** block, and it only appears on gift card products.

{% hint style="warning" %}
Before digging into code, open the page in an incognito window. App embeds and browser extensions can hide elements on your own logged-in session only.
{% endhint %}

{% hint style="success" icon="lightbulb" %}
See [Quick View & Pre-order templates](/docs/volume-themes/products/quick-view-and-pre-order-templates.md) and [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/products-and-variants/i-added-a-block-but-it-does-not-show-on-the-product-page.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.