> 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/bottling-schedule.md).

# Bottling Schedule

Transactional file delivering forward-looking planned bottling runs. One row per planned run at the item × location × date × quantity grain.

The planned bottling schedule, a forward-looking production plan. One row per planned bottling run, expressed as a finished-good item × location × date × quantity.

## 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>item_name</code></td><td>true</td><td>The finished good being bottled, at the <strong>planning level</strong>. Must match an <code>item_name</code> from the Finished Good Items file (not a <code>vintage_name</code>).</td><td><code>122</code></td></tr><tr><td>2</td><td><code>location_name</code></td><td>true</td><td>The site where the bottling run will occur. Must match a <code>location</code> from the Locations file.</td><td><code>ZAM-WINERY</code></td></tr><tr><td>3</td><td><code>date</code></td><td>true</td><td>The planned bottling date (or the period start, depending on <code>timing_interval</code>), as <code>YYYY-MM-DD</code>.</td><td><code>2026-05-12</code></td></tr><tr><td>4</td><td><code>quantity</code></td><td>true</td><td>Planned production quantity. Numeric value. Decimals fine, whole numbers fine. No thousands separators.</td><td><code>1500</code></td></tr><tr><td>5</td><td><code>uom</code></td><td>true</td><td>Unit of measure (e.g., <code>9LE Case</code>).</td><td><code>9LE Case</code></td></tr><tr><td>6</td><td><code>timing_interval</code></td><td>false</td><td>One of: <code>Day</code>, <code>Week</code>, <code>Month</code>. Duration the plan covers. Defaults to <code>Day</code>. Use <code>Week</code> if the schedule is published at week-grain; in that case <code>date</code> should be the Monday of that week.</td><td><code>Day</code></td></tr></tbody></table>

## Header row

```
item_name,location_name,date,quantity,uom,timing_interval
```

## Sample data

```csv
item_name,location_name,date,quantity,uom,timing_interval
122,ZAM-WINERY,2026-05-12,1500,"9LE Case",Day
122,ZAM-WINERY,2026-05-19,2000,"9LE Case",Day
124,ZAM-WINERY,2026-05-13,800,"9LE Case",Day
123,ZAM-WINERY,2026-05-26,1200,"9LE Case",Day
```

{% hint style="info" %}
`item_name` is the planning level (`122`, `124`), not the vintage level (`122-16`). See the [Finished Good Items](/integrations/inbound-file-feed/finished-good-items.md) spec for the distinction.
{% endhint %}

## Snapshot semantics

* Full forward-looking snapshot every delivery. Every active planned run for any future date should appear in every file.
* Past-dated runs may be omitted once they're realized as actual bottling work plans.
* Plans are matched on the key (`item_name`, `location_name`, `date`); re-delivering the same key overwrites the prior plan.
* A previously-delivered plan absent from a new snapshot will be marked cancelled.