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

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

Header row

item_name,location_name,date,quantity,uom,timing_interval

Sample data

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

item_name is the planning level (122, 124), not the vintage level (122-16). See the Finished Good Items spec for the distinction.

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.