> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-product-structures.md). # How to use Product structures Product models are one of the most powerful aspects of Struct PIM. Using the built-in no-code interface you can build any product data model you need by adding attributes one by one Product structures are the blueprints for products, variants and variant groups in the system. A product structure defines tabs, sections and attributes that are available to products, variants and variant groups using that product structure. Product structures can be created and updated directly in the UI of Struct PIM, which allows for easy configuration of the underlying data models of products, variants and variant groups. {% embed url="" %} Product models (duration 3:11 min) {% endembed %} ### Guides covering Product structures * [How to set up and edit a product model](/tutorials/guides/how-to-use-product-structures/how-to-set-up-and-edit-a-product-model.md) * [How to set up variant model](/tutorials/guides/how-to-use-product-structures/how-to-set-up-a-variant-group-model.md) * [How to set up a variant group model](/tutorials/guides/how-to-use-product-structures/how-to-set-up-a-variant-group-model.md) * [Working with product models using the API](/tutorials/guides/how-to-use-struct-pims-api/working-with-product-models-using-the-api.md) --- # 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.struct.com/tutorials/guides/how-to-use-product-structures.md?ask=&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.