# Best Practice Product Structuring

When it comes to structuring products, often brands can get confused because they want to understand the best way to set up variants for operations, but also the best way for customers to discover their products.

<figure><img src="/files/6MhQVafQa4UamwyRKAhB" alt=""><figcaption></figcaption></figure>

For example - in fashion - if you are selling a summer dress in 4 colours, and 10 sizes, you should split the 4 colours into seperate products, even though they have the same style, the 10 sizes then become a size variant group on each product.

This configuration ensures that customers can then filter and search by colour as well as style.

To illustrate this when done incorrectly - imagine you have the same product - 4 colours, and 10 styles.

A user navigates to the collection page and filters by red, but your default image is the black dress.

You are not able to dynamically change the image based on a users filtering, so they get a confusing experience, and will not click.

**Sale Tags**

When it comes applying tags, it is usually best practice to discount a style, not a size. So such tags to indicate sales should be applied to a product, not a specific variant.

In the case that you only have a few sizes left of a product, then you can still just apply this to the full product, but it only actually impacts a few sizes, because the others are sold out.


---

# Agent Instructions: 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:

```
GET https://docs.almond.studio/configuration-guides/best-practice-product-structuring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.