> 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/sections/products/featured-product.md).

# Featured Product

Build a custom single-product info layout using title, price, vendor, and app blocks.

Unlike other Products sections, Featured Product has no product picker or layout settings of its own — it's a block canvas for building a custom info layout around a single product, typically used on the Product template.

***

### How to add

1. In Theme Editor, open the **Product** template.
2. Click **Add section** and select **Featured Product**.
3. Add, remove, and reorder blocks to build the info layout around the current product.

### Good to know

* This section has no settings of its own — everything is controlled through blocks, so you build the info layout by adding, removing, and reordering blocks.
* **Title**, **Title with price**, and **Title with vendor** are each limited to one block — pick the one variant that matches what you want to show, not all three.
* **Vendor** can appear up to twice as its own block, letting you show it both near the top and elsewhere in the layout.
* **Title with vendor** can render the vendor as plain text or as a vendor logo image.
* **Title with price** includes badge display and a compare-at-price color option (with background variants), plus an option to hide the shipping note.
* App blocks can be inserted anywhere in this block list, so third-party apps (reviews, size guides, subscriptions) slot in alongside the native blocks.

### Customization ideas

* Use Title with vendor plus a vendor logo image if your catalog spans multiple brands — it reads more like a marketplace listing.
* Place a Vendor block once near the top and once near the bottom of a long info layout to reinforce brand recognition.

***

### Settings reference

<details>

<summary>Block reference</summary>

| Block             | Limit | What it controls                                                                                              |
| ----------------- | ----- | ------------------------------------------------------------------------------------------------------------- |
| Title             | 1     | Plain product title                                                                                           |
| Title with price  | 1     | Title + price, with badge display, compare-at-price color/background, and an option to hide the shipping note |
| Title with vendor | 1     | Title + vendor, shown as text or as a vendor logo image                                                       |
| Vendor            | 2     | Standalone vendor name/logo, can be placed twice                                                              |
| App block         | —     | Any installed app's block (reviews, size guide, subscriptions, etc.)                                          |

</details>

### Best practices

* Pick one variant of Title, Title with price, or Title with vendor rather than combining them — they cover overlapping ground.
* Reserve the second Vendor block for long layouts where a shopper might scroll past the first one.

## Related

* [Featured products & collections](/docs/volume-themes/sections/products/featured-products-featured-collections-and-featured-collection-grid.md)


---

# 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/sections/products/featured-product.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.