> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/documentation-simax-anglais/functional/items-and-pricing/the-range.md).
# The range
## Context
The "EcoVibes" association, committed to promoting sustainability and environmental respect, has decided to launch an awareness campaign. To do this, it wants to create a series of custom t-shirts that can be worn by its members at events.
"EcoVibes" wants to offer various options to its members:
Color choices: White, Green, Yellow, and Red.
Collar types: Round and V-neck.
## Implementation in Simax
First, the item « T-shirt » must be created, then go to **\[Features]**, **\[\[Other features]]** and **\[\[New]]**.
Since the feature « Collar » does not exist yet, it needs to be created with the possible values.
Below is the list of attributes created for the "T-shirt" item.
To create the variations according to the customer’s request, stay in **\[Feature]** but click on **\[\[Create ranges]]**.
We can see that there are 8 possible variations. To create the variations, click on **\[\[Create]]**. They will appear in the item list and each will have its own reference.
We can also view the variations in **Files > Item > Range list** and filter by the base item.
---
# 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://doc.simax.fr/documentation-simax-anglais/functional/items-and-pricing/the-range.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.
