> 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/bulk-wine-items.md).

# Bulk Wine Items

Bulk wine (WIP) item master. Each row is one **child WIP** (the lowest, most granular level: a specific vintage of a bulk wine), with its full parent hierarchy **flattened across columns on the same row**.

## About the hierarchy

By default, Claret expects a two-level hierarchy for bulk wine: **Parent WIP → Child WIP**. For example:

* **Parent WIP:** `ZAMNVCAS` (WIP - ZAM Napa Valley Cabernet Sauvignon)
* **Child WIPs:** `ZAMNVCAS16`, `ZAMNVCAS17`, ... `ZAMNVCAS24` (one per vintage year)

The bulk wine hierarchy is **fixed at two levels**: a parent WIP and its child WIPs. If your naming convention differs from `Parent WIP` / `Child WIP` (e.g., you call them `Wine` and `Vintage`, or `Lot Family` and `Lot`), 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.

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>parent_wip_name</code></td><td>true</td><td>Top-level grouping. Same value repeats across every child WIP under it.</td><td><code>ZAMNVCAS</code></td></tr><tr><td>2</td><td><code>parent_wip_description</code></td><td>false</td><td>Long-form description of the parent WIP. Shown in tooltips and used in search.</td><td><code>WIP - ZAM Napa Valley Cabernet Sauvignon</code></td></tr><tr><td>3</td><td><code>child_wip_name</code></td><td>true</td><td>The vintage-specific WIP. <strong>Must be unique across all rows in the file and across the Finished Good Items file.</strong> Referenced by Inventory, Recipes, and Work Plans.</td><td><code>ZAMNVCAS19</code></td></tr><tr><td>4</td><td><code>child_wip_description</code></td><td>false</td><td>Long-form description of the child WIP. Shown in tooltips and used in search.</td><td><code>WIP - ZAM Napa Valley Cabernet Sauvignon 2019</code></td></tr></tbody></table>

{% hint style="info" %}
**Which level do other files reference?**

* **Inventory** always uses `child_wip_name`.
* **Recipes** may reference either `parent_wip_name` or `child_wip_name`, depending on the level at which the recipe is defined.
* **Work Plans** may reference either `parent_wip_name` or `child_wip_name`, depending on whether the work targets a generic parent wine (e.g., a future blend) or a specific vintage.
  {% endhint %}

## Header row

```
parent_wip_name,parent_wip_description,child_wip_name,child_wip_description
```

## Sample data

```csv
parent_wip_name,parent_wip_description,child_wip_name,child_wip_description
ZAMNVCAS,"WIP - ZAM Napa Valley Cabernet Sauvignon",ZAMNVCAS16,"WIP - ZAM Napa Valley Cabernet Sauvignon 2016"
ZAMNVCAS,"WIP - ZAM Napa Valley Cabernet Sauvignon",ZAMNVCAS17,"WIP - ZAM Napa Valley Cabernet Sauvignon 2017"
ZAMNVCAS,"WIP - ZAM Napa Valley Cabernet Sauvignon",ZAMNVCAS18,"WIP - ZAM Napa Valley Cabernet Sauvignon 2018"
ZAMNVCAS,"WIP - ZAM Napa Valley Cabernet Sauvignon",ZAMNVCAS19,"WIP - ZAM Napa Valley Cabernet Sauvignon 2019"
ZAMNVCAS,"WIP - ZAM Napa Valley Cabernet Sauvignon",ZAMNVCAS20,"WIP - ZAM Napa Valley Cabernet Sauvignon 2020"
CLMCCPIN,"WIP - Clairemont Central Coast Pinot Noir",CLMCCPIN21,"WIP - Clairemont Central Coast Pinot Noir 2021"
FNESLPNO,"WIP - FNE St Lucia Pinot Noir",FNESLPNO26,"WIP - FNE St Lucia Pinot Noir 2026"
```

## Snapshot semantics

* Full snapshot every delivery. Include every currently-active bulk WIP item.
* A WIP omitted from a new snapshot is treated as retired; its history is preserved but no new transactional rows referencing it will be accepted.
* `child_wip_name` must be unique across all rows in the file and across the [Finished Good Items](/integrations/inbound-file-feed/finished-good-items.md) file.
* 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.


---

# 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://docs.claret.app/integrations/inbound-file-feed/bulk-wine-items.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.