> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/products/catalog/creating-new-product/simple-products.md).

# Simple products

Create a simple product, the basic product type with no relations or variants, by filling in the Create product window.

This is the most basic product type, with no relations or variants (until you assign them). The product can exist as a separate item, as a variant of another product, or as part of a product group. The main goal of this product type is to keep it simple and easy to manage.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2F6CpXUbaIHVpubfZrkYVn%2Fimage.png?alt=media&#x26;token=e21c30a1-7b4e-4f17-a789-16ee6386e343" alt="" width="563"><figcaption></figcaption></figure>

Fill in all fields; the SKU can be created automatically for you if you enable the [**Generate SKU automatically**](https://usermanual.ergonode.com/system/settings/sku) option in settings. In that case, the ***SKU*** field is not shown in this window.

Choose the product template that will be used with this product. If the template doesn't exist yet, choose ***Add new template*** at the top of the list, type its name and click the green check icon.

Choosing categories is optional. In ***Category***, tick the ones you want; choosing a category tree only filters the list. To tick a category together with its subcategories, use ***Select branch***. The list works like the ***Category*** quick filter, described in [Quick filters](https://usermanual.ergonode.com/products/catalog/quick-filters).

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FFWVU6h4N8zPzx5ZbUFjM%2Fimage.png?alt=media&#x26;token=baa1974a-a9f5-4e57-86b6-6919ddee4a33" alt="" width="563"><figcaption></figcaption></figure>

Click ***Create***, or ***Create & Edit*** to go straight to the edit mode for the newly created product. It opens on the ***Template*** tab.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2F4bdZIDFEd7N76MwbaPcn%2Fimage.png?alt=media&#x26;token=115eec0f-cbe6-498a-af87-81a41fa29e8f" alt="" width="563"><figcaption></figcaption></figure>

You will see multiple tabs where you can add extra information about this product: [**General,**](https://usermanual.ergonode.com/products/catalog/general)[**Template**](https://usermanual.ergonode.com/products/catalog/template)**,** [**History**](https://usermanual.ergonode.com/products/catalog/history)**, and** [**Comments**](https://usermanual.ergonode.com/products/catalog/comments) **(**&#x61;vailable from the icon in the title bar)**.**


---

# 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://usermanual.ergonode.com/products/catalog/creating-new-product/simple-products.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.
