> 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/product-design/product-templates.md).

# Product templates

Design the layout of product cards with templates, sections and completeness sets, the three tabs of Product templates.

With product templates, you can easily create and manage different layouts for different types of products, and ensure that they have all the necessary information and attributes.

Product templates are not meant to be exported to your eCommerce platform. They are only for your internal use in Ergonode PIM, to help you organize and enrich your product data in a user-friendly way.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2F8qlfE58kIGVL7BDidMlc%2F09169c6416d3.png?alt=media&amp;token=6cd34648-5fa7-44e6-bce3-94f3fcb36126" alt=""><figcaption></figcaption></figure>

For that reason, we have created a tool that allows for the design of the layout of a product card in a completely innovative way.

{% hint style="info" %}
This product page layout will not be sent to your eCommerce. It's here to help people working in Ergonode PIM to make their work more streamlined and effortless.
{% endhint %}

When entering this page you will find three tabs:

* [**Main templates**](https://usermanual.ergonode.com/product-design/product-templates/main-templates): Here you can see all the existing product templates, and create new ones by clicking on the “*New template*” button. You can also edit, or clone (the cloning option is available through ***three dots*** menu - when in edit mode) any product template by clicking on the ***edit (pen)*** icon next to it. Or delete it by clicking on the ***bin icon***.
* [**Sections**](https://usermanual.ergonode.com/product-design/product-templates/sections): Here you can define the sections that will appear on your product cards, such as “General”, “Images”, “Specifications”, etc. You can create new sections by clicking on the “*New section*” button, and edit or delete existing ones by clicking on icons next to them. When created sections can be drag and drop to change their order on the Template designer.
* [**Completeness sets**](https://usermanual.ergonode.com/product-design/product-templates/completeness-sets): Here you can create and manage the completeness sets that will help you track the progress of your product enrichment. A completeness set is a group of attributes that are required for a product to be considered complete. You can create new completeness sets by clicking on the “*New completeness set*” button, and edit or delete existing ones by clicking on the icons next to them. You can also assign a completeness set to a section.

Product templates are a great way to make your product management easier and more efficient in Ergonode PIM. You can use them to create consistent and attractive product cards that suit your needs and preferences.<br>

{% hint style="info" %}
To learn more about the features available from the product card, [click here](https://usermanual.ergonode.com/products/catalog/template).
{% 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://usermanual.ergonode.com/product-design/product-templates.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.
