> For the complete documentation index, see [llms.txt](https://story.groupthought.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://story.groupthought.com/siblings/product-siblings/how-to-setup-siblings.md).

# How to setup siblings

> Feature introduced in Story 3.2.0

There are four main components to setting up product siblings:

1. Creating individual products. Each product can have variants like sizes. 
2. Group the siblings products into a collection.
3. Define two custom metafields to link each product together which will automatically create linked product swatches.
4. Update the metafield information for each product. 

### Individual products

Create individual products that are similar. Use the same name for the product title with each product:

![](/files/eTB1Kg8xLvlkY6BTh2ts)

Once connected to each other as siblings, they will appear with linked swatches to each other:

![](/files/l4yYtbVJ6f5BkCV9352Z)

Each product can have its own images, inventory, prices, description, variants like Size:

![](/files/4KKkOSwm1xoM3OztDKo4)

A **Color** variant isn't required as that will be replaced by image swatches and a metafield is used to display the color.

{% hint style="success" %}
Tip: Create the first product with sizes and prices, then duplicate that product and add new images for each variation and adjust the description, inventory, and prices. Only the product name needs to be the same for all products.  
{% endhint %}

### Collection for siblings

After creating the products, place them all in one collection. The collection does not need to be used for any other purpose:

![](/files/SbsNjrsgfZZNZNX1wx6i)

The collection is not displayed in the store like other collections, you can keep the collection details very simple:

![](/files/MNWd2lcYbbL1Q57wY9ar)

{% hint style="success" %}
We recommend you use the word "**Siblings**" in the title of the the collection. This will help in the next step where we can hide collections globally that contain a keyword.
{% endhint %}

### Theme settings

Story includes a new feature where you can hide collections to customers when viewing your site. Open **Theme settings** from the Theme Editor - **Located at the bottom left**:

![](/files/zNUxyQb6B0Gjl45AtMN7)

Next, open the **Advanced** section:

![](/files/q0rs2ALlzKurxUWRRwl2)

Add the keyword "sibling" or "siblings" (lowercase is fine) to the second section - **Exclude collections if they contain**.

**Save** your changes. 

### Metafields

The next step is to create two product metafields which are used to connect all the products and information together:

{% content-ref url="/pages/tRI5Qs1bkzlMma2Cw989" %}
[Cutline](/siblings/product-siblings/cutline.md)
{% endcontent-ref %}

{% content-ref url="/pages/ujg62BwEKsyoKNaLtA7Z" %}
[Siblings collection](/siblings/product-siblings/siblings-collection.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://story.groupthought.com/siblings/product-siblings/how-to-setup-siblings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.