> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/day-to-day-operations/products/catalog-setup.md).

# Catalog Setup

Before you start adding products, take some time to set up your catalog structure. Getting this right from the start saves time and makes reporting much more useful later.

***

### What to set up first

<table><thead><tr><th width="182.796875">What</th><th>Why</th></tr></thead><tbody><tr><td><a href="/docs/day-to-day-operations/products/catalog-setup/product-groups.md">Product Groups</a></td><td>Required for every product. Used for reporting and campaigns</td></tr><tr><td><a href="/docs/day-to-day-operations/products/catalog-setup/brands.md">Brands</a></td><td>Required for every product. Track performance by manufacturer</td></tr><tr><td><a href="/docs/day-to-day-operations/products/catalog-setup/properties.md">Properties</a></td><td>Optional, but needed for variants (size, color)</td></tr><tr><td><a href="/docs/day-to-day-operations/products/catalog-setup/product-types.md">Product Types</a></td><td>Understand the differences before adding products</td></tr></tbody></table>

***

### Quick checklist

Before adding your first product, make sure you have:

* [ ] Created your Product Group hierarchy (2–4 levels recommended)
* [ ] Added all relevant Brands (plus a "house brand" for unbranded items)
* [ ] Set up Properties if you sell products with variants
* [ ] Decided which Product Type fits each type of item you sell

***

{% hint style="success" %}

#### Tips

**Plan your Product Groups carefully** It's tempting to create a few quick groups just to get started, but restructuring later is time-consuming. Think about how you want to filter reports and target campaigns.

**Start simple with Properties** You can always add more later. Begin with the essentials like Size and Color if you need variants.
{% 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://docs.flowretail.com/docs/day-to-day-operations/products/catalog-setup.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.