> For the complete documentation index, see [llms.txt](https://docs.claret.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claret.app/integrations/inbound-file-feed/crops.md).

# Crops

Master data file delivering crop master records (varietal groups and crops) used as recipe ingredients for bulk wine.

Crops master. Each row is one **Crop** (the lowest, most granular level: typically a varietal × grade or varietal × source classification used in bulk-wine recipes), with its parent **Varietal Group** flattened across columns on the same row.

## About the hierarchy

The crop hierarchy is **fixed at two levels**: a Varietal Group and its Crops. If your naming convention differs from `Varietal Group` / `Crop` (e.g., you call them `Grape` and `Lot Grade`), you can substitute your own labels in the column names, using the pattern `{Level} Name, {Level} Description` for each level. The depth, however, must remain two levels.

By default, Claret expects short codes for the varietal group names with the full varietal name in the description:

* **Varietal Group:** `CAS` (Cabernet Sauvignon), `PIN` (Pinot Noir)
* **Crops:** `CAS-A` (Cabernet Sauvignon - A Grade), `CAS-B`, `CAS-C`, `PIN-A`, ...

If you adapt the labels, email `help@claret.app` describing your level names so the labels can be applied in Claret's UI.

## Schema

<table><thead><tr><th>#</th><th>Column</th><th data-type="checkbox">Required?</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td>1</td><td><code>varietal_group_name</code></td><td>true</td><td>Top-level grouping. Same value repeats across every crop under it.</td><td><code>CAS</code></td></tr><tr><td>2</td><td><code>varietal_group_description</code></td><td>false</td><td>Long-form description of the varietal group. Shown in tooltips and used in search.</td><td><code>Cabernet Sauvignon</code></td></tr><tr><td>3</td><td><code>crop_name</code></td><td>true</td><td>The specific crop. <strong>Must be unique across all rows in the file and across the Finished Good Items and Bulk Wine Items files.</strong> Referenced by Recipes as an ingredient.</td><td><code>CAS-A</code></td></tr><tr><td>4</td><td><code>crop_description</code></td><td>false</td><td>Long-form description of the crop. Shown in tooltips and used in search.</td><td><code>Cabernet Sauvignon - A Grade</code></td></tr></tbody></table>

## Header row

```
varietal_group_name,varietal_group_description,crop_name,crop_description
```

## Sample data

```csv
varietal_group_name,varietal_group_description,crop_name,crop_description
CAS,"Cabernet Sauvignon",CAS-A,"Cabernet Sauvignon - A Grade"
CAS,"Cabernet Sauvignon",CAS-B,"Cabernet Sauvignon - B Grade"
CAS,"Cabernet Sauvignon",CAS-C,"Cabernet Sauvignon - C Grade"
PIN,"Pinot Noir",PIN-A,"Pinot Noir - A Grade"
```

## Snapshot semantics

* Full snapshot every delivery. Include every currently-active crop.
* A crop omitted from a new snapshot is treated as retired; its history is preserved but no new recipe rows referencing it will be accepted.
* `crop_name` must be unique across all rows in the file and across the [Finished Good Items](/integrations/inbound-file-feed/finished-good-items.md) and [Bulk Wine Items](/integrations/inbound-file-feed/bulk-wine-items.md) files.
* All `Name` and `Description` columns should be populated. `Description` values appear in Claret's UI (tooltips, search, exports) and improve usability for the people working in the grids.