> 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/non-real-varieties.md).

# Non-Real Varieties

There are times where sales demand is requested and it’s non-variety specific. The identifying characteristic is typically based on Species/Color. An example would be Roses White. While there are 20+ varieties of white roses - they can all be used to fulfill the demand of a white rose.

In these cases, the farm will take the demand order as a generic product. Using the example above, Roses White. This is the Rose Species with the color attribute of white. Any of the above 20+ varieties can be used to fulfill the order.

The farm will track which varieties are going into the demand (important from a cost/sales tracking metric at the farm level). They will take Mondial, Akito, Creme de la Creme and process it against a generic Rose White product. Variety will always be known on the supplier level.

<figure><img src="/files/fnwN6vy4qsxV4OeW2229" alt=""><figcaption><p>Rose White (non-real variety)</p></figcaption></figure>


---

# 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/non-real-varieties.md?ask=<question>&goal=<endgoal>
```

`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.
