> For the complete documentation index, see [llms.txt](https://manual.unosofbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.unosofbooks.com/taxonomy-definitions/products/varieties.md).
# Varieties
For many species, there will be multiple varieties that exist within that species. Each of which may contain different characteristics that separate and define it from its peers. Attributes such as shade of color, head size, stem sturdiness, resistance to disease, longevity etc.
Farms will always plant and track based on variety. There are also royalties that can be tied to specific varieties that need to be paid out to breeders based on sales.
\
Farms send out their inventory availability sheets which are variety specific. If you are looking to do ecommerce from the farm perspective, variety is an important defining part of a product. Varieties are typically associated with a color (which can vary based on perspective). White or Cream?
It is also the basis of Floricode (Species/Variety = Floricode ID)
Different types of varieties:
Example of farm inventory sheet:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://manual.unosofbooks.com/taxonomy-definitions/products/varieties.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
