> 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/avante-themes/sections/collections/related-collections.md).

# Related collections

Links shoppers from a product page to its collection and to everything else by the same brand — up to three navigation cards below the product.

A customer who has just looked at one product is at the most useful moment of the visit: they have told you what they like. Related collections turns that moment into navigation — up to three cards that lead back to the collection the product belongs to, and out to everything else by the same brand. It is a short, predictable path to a second product view, and it needs no app and no tagging.

### How to add

{% stepper %}
{% step %}

#### Open a product template

Go to **Online Store → Themes → Customize** and open a **product** template. The section is only available there — you will not find it on the home page or on collection templates.
{% endstep %}

{% step %}

#### Add the section

Click **Add section** and choose **Related collections** from the Collections category.
{% endstep %}

{% step %}

#### Choose the cards

Decide which of the three links to show, and optionally set a **Main collection**.
{% endstep %}

{% step %}

#### Set the images

Upload a custom image for each card, or let the theme pick one.
{% endstep %}
{% endstepper %}

### Good to know

**The section has no blocks, and the cards are collection links.** It renders at most three fixed links, built from one collection and the product's vendor — an image, a label and a destination, with no prices, swatches or quick view.

**The main collection is resolved in order.** First the section's **Main collection** setting, then the product's `custom.main_collection` metafield, then the first collection assigned to the product. The section setting wins whenever it is filled in — despite the editor hint, the metafield does not override it. Leave the setting empty if you want per-product control.

**The last fallback has no guaranteed order.** A product that sits in several collections can surface an unexpected one. Set `custom.main_collection` when these links matter.

**Two of the three links need a main collection.** If the theme cannot work out which collection a product belongs to, those links disappear and the section can shrink to a single card.

| Link                    | What it needs                                                                                                                  |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Shop by brand**       | Always works. It opens the vendor page for the product's brand.                                                                |
| **Collection by brand** | Needs a main collection and the **Vendor** filter enabled in Search & Discovery. Otherwise it opens the unfiltered collection. |
| **Shop the collection** | Needs a main collection. It opens that collection without filters.                                                             |

**Brand images follow a filename convention.** For **Shop by brand** the theme searches **Content → Files** for a `.png` named exactly after the vendor. It does not find JPG files, and falls back to a price-tag placeholder. A custom card image skips the convention entirely.

**Card labels are fixed storefront strings.** Translate them in **Content → Languages**; they cannot be edited per section.

### Customization ideas

* Set the `custom.main_collection` metafield on every product and leave the section's own collection setting empty. One section configuration then behaves correctly across the whole catalogue.
* On a single-brand store, turn off **Shop by brand** and **Collection by brand** and keep only **Shop the collection** — the other two add nothing when every product has the same vendor.
* Upload a logo per vendor to **Content → Files**, named exactly after the vendor with a `.png` extension, and the brand cards become a visual brand index rather than three identical tiles.
* Give the section a heading that frames it as discovery — "More from this maker", "Keep exploring" — rather than the technical default.
* Place it below the product details and above reviews: after the buying decision, before the social proof.
* Keep custom card images in the same crop and style as your collection images so the row reads as one component.

***

### Related

* [Featured collection with product grid](https://staylime.com/docs/avante-themes/sections/collections/featured-collection-with-product-grid.md)
* [Default product](https://staylime.com/docs/avante-themes/templates/default-product.md)
* [Image & video size recommendations](https://staylime.com/docs/avante-themes/faq/performance/image-and-video-size-recommendations.md)
* [Collections](https://staylime.com/docs/avante-themes/sections/collections.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/avante-themes/sections/collections/related-collections.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.
