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
1
varietal_group_name
Top-level grouping. Same value repeats across every crop under it.
CAS
2
varietal_group_description
Long-form description of the varietal group. Shown in tooltips and used in search.
Cabernet Sauvignon
3
crop_name
The specific crop. Must be unique across all rows in the file and across the Finished Good Items and Bulk Wine Items files. Referenced by Recipes as an ingredient.
CAS-A
4
crop_description
Long-form description of the crop. Shown in tooltips and used in search.
Cabernet Sauvignon - A Grade
Header row
varietal_group_name,varietal_group_description,crop_name,crop_descriptionSample data
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_namemust be unique across all rows in the file and across the Finished Good Items and Bulk Wine Items files.All
NameandDescriptioncolumns should be populated.Descriptionvalues appear in Claret's UI (tooltips, search, exports) and improve usability for the people working in the grids.
Last updated
Was this helpful?