Free OpenClaw skill · No signup · v1.0.0
Free OpenClaw Skill for Distilleries: Production and TTB Agent (Download)
A working OpenClaw skill for craft distilleries running 50 to 5,000 proof gallons per month. Owns the mash bill production schedule, the TTB DSP compliance workload, the COLA / FONL / MOR filings, and the wholesale distributor handoff, all from one SKILL.md drop-in.
Built and maintained by Adhiraj Hangal, OpenClaw Consult. Code I wrote runs inside OpenClaw's source, merged by the project's creator.
Free OpenClaw skill for distilleries
12 KB file. Free for any use. Drop it into your OpenClaw setup and your agent knows your business in 60 seconds.
We email you a copy plus the install notes. One email, no list, no spam.
What this skill does for your distilleries
- Drafts the next production cycle's mash bill, ferment, distillation, and barrel-fill plan from WhiskeySystems or DistillerySoft, with proof gallon math at every step.
- Compiles the monthly TTB DSP Reports of Operations on Forms 5110.40 (production), 5110.43 (storage), and 5110.74 (processing) with the variance from last month flagged.
- Tracks COLA (Certificate of Label Approval) submission status and FONL (Formula and Process for Nonbeverage Products) timing for each SKU.
- Manages NDP (Non-Distiller Producer) sourcing disclosure language across the label and the website for the brands that source distillate.
- Drafts the distributor handoff packet (lab cert, COLA, sample case, account-by-account placement plan) for each new release.
What's inside this OpenClaw skill
The full file you download, indexed below for search engines and for operators who want to read before they install.
---
name: distillery-production-and-ttb
description: Mash bill production scheduling, TTB DSP compliance (Forms 5110.40, 5110.43, 5110.74), COLA and FONL tracking, NDP disclosure management, and distributor handoff for craft distilleries. Integrates with WhiskeySystems, DistillerySoft.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/distilleries
---
# OpenClaw Skill: Distillery Production and TTB Compliance Coordinator
## Overview
This skill turns the OpenClaw agent into the production and TTB compliance
operator for a craft distillery. It owns the mash bill production schedule,
the monthly Reports of Operations on TTB Forms 5110.40 / 5110.43 / 5110.74,
the COLA and FONL filing tracker, the NDP source-state disclosure language,
and the distributor handoff packet for each new release.
By design the skill never auto-submits to TTB. The operator files; the
skill prepares the filing. This matches the way every craft distillery we
have scoped wants compliance work to run.
Designed for craft distilleries running 50 to 5,000 proof gallons per
month on WhiskeySystems, DistillerySoft, Distil-X, or OrchestratedSPIRITS.
## What this skill does
1. Drafts the next production cycle's mash bill, ferment, distillation, and barrel-fill plan
2. Maintains a running proof gallon ledger across production, storage, and processing
3. Compiles the monthly TTB Forms 5110.40 (production), 5110.43 (storage), 5110.74 (processing)
4. Tracks COLA submission status and FONL filing timing per SKU
5. Manages NDP source-state disclosure language across label, shelf talker, and website
6. Drafts the distributor handoff packet for each new release
## Triggers
```yaml
triggers:
- type: heartbeat
schedule: "0 7 * * 1" # Mondays 7am, weekly production schedule
action: weekly_production_schedule_draft
- type: heartbeat
schedule: "0 9 1 * *" # 1st of month 9am, TTB compilation
action: monthly_ttb_report_compile
- type: heartbeat
schedule: "0 14 * * 3" # Wednesdays 2pm, COLA and FONL status check
action: cola_fonl_status_review
- type: on_event
event: production.distillation_run_completed
action: update_proof_gallon_ledger
- type: on_event
event: production.barrel_filled
action: log_to_storage_ledger
- type: on_event
event: production.bottling_run_completed
action: log_to_processing_ledger_and_check_cola_status
- type: on_event
event: cola.approval_received
action: alert_operator_and_unblock_release
```
## Workflow: production schedule
Every Monday at 7am the agent:
1. Reads the rickhouse state (filled barrels, open barrel positions, barrel ages)
2. Reads the current fermenter and still state
3. Reads the upcoming release calendar (bottling dates, distributor commitments)
4. Drafts the production schedule for the upcoming 4 weeks: mash bills, ferment dates, distillation dates, barrel fills
5. Computes the proof gallon projection at each step
6. Routes to the master distiller for approval
The schedule respects mash bill, fermentation, and distillation rules:
```yaml
production_rules:
bourbon_mash_bill: "min 51% corn, balance rye and malt"
rye_mash_bill: "min 51% rye"
fermentation_days: [3, 7]
distillation_per_batch_hours: [12, 18]
barrel_fill_proof_max: 125
barrel_age_minimum_for_bourbon_labeling_years: 2
```
## Workflow: proof gallon ledger
Every distillation run, gauging, transfer-in-bond, barrel fill, withdrawal,
and bottling event updates the running PG ledger:
```yaml
pg_ledger_transformations:
- event: distillation_run_completed
delta: produced_pg
- event: gauging_completed
delta: gauge_adjustment
- event: transfer_in_bond_inbound
delta: +inbound_pg
- event: barrel_filled
delta: -wine_gallons_to_storage
- event: withdrawal_taxpaid
delta: -withdrawn_pg
- event: bottling_run_completed
delta: -bottled_pg
```
The ledger reconciles daily against your WhiskeySystems or DistillerySoft
figure. Any divergence above the operator-set threshold (default 0.5 PG)
is flagged for review.
## Workflow: TTB monthly compilation
On the 1st of each month at 9am the agent:
1. Aggregates the previous month's production events into Form 5110.40 (Report of Production Operations) categories
2. Aggregates storage events (barrel fills, transfers, losses) into Form 5110.43 (Report of Storage Operations)
3. Aggregates processing and bottling events into Form 5110.74 (Report of Processing Operations)
4. Computes variance vs prior 3 months
5. Drafts the report in the TTB-required format
6. Queues for operator review
The skill DOES NOT submit. The filing window for the previous month closes
on the 15th of the current month. The skill nags daily after the 10th if
the draft has not been operator-approved.
## Workflow: COLA and FONL tracking
Every Wednesday at 2pm the agent:
1. Reads COLA submission status from the TTB Online account (or the operator's manual log)
2. Flags any pending submission past the typical 30 to 60 day review window
3. Flags any SKU in the release calendar without an approved COLA
4. Flags any FONL filing past its review window for formulated products (gin, flavored whiskey, liqueurs)
5. Drafts the operator's weekly compliance digest
The skill does not file COLA or FONL. The operator submits through TTB
Online. The skill's job is to make sure no SKU is bottled or released
without the required approvals in hand.
## Workflow: NDP source-state disclosure
For brands that source distillate from another DSP (Non-Distiller Producer
model, increasingly common in the craft segment), the skill maintains:
1. Source DSP per SKU with the source state
2. Required label language: "Distilled in [STATE]" or equivalent
3. Shelf talker and website disclosure language
4. The TTB-required disclosure cadence
When a new SKU comes through with NDP sourcing, the agent flags it before
the COLA application goes out and drafts the required disclosure language.
## Workflow: distributor handoff
When a new release approaches its launch date, the agent drafts the
distributor handoff packet:
1. Lab certificate of analysis (proof, congeners, allergens if applicable)
2. Approved COLA copy
3. Sample case count and shipping plan
4. Account-by-account placement plan based on the distributor's book
5. Marketing collateral checklist (shelf talker, case card, social assets)
6. PR sample list for trade publications
The handoff packet is operator-approved, then sent to the distributor 14 to
30 days before the release date.
## Message templates
```yaml
templates:
weekly_production_schedule:
channel: slack
body: |
WEEK OF {week_start} PRODUCTION SCHEDULE
Mash bills: {mash_bills_planned}
Ferment dates: {ferment_dates}
Distillation dates: {distillation_dates}
Barrel fills: {barrel_fills}
Estimated PG produced: {estimated_pg}
Rickhouse positions filled: {rickhouse_positions}
ttb_monthly_report_ready:
channel: slack
body: |
TTB MONTHLY REPORT READY FOR REVIEW
Month: {month}
Form 5110.40 production PG: {production_pg}
Form 5110.43 storage delta: {storage_delta_pg}
Form 5110.74 processing PG: {processing_pg}
Variance vs prior 3 months: {variance_summary}
Filing window closes: {filing_window_end}
Draft link: {draft_url}
cola_status_alert:
channel: slack
body: |
COLA STATUS ALERT
SKU: {sku_name}
Submitted: {submission_date}
Days pending: {days_pending}
Typical review window: {typical_window}
Release scheduled: {release_date}
Recommended action: {recommended_action}
ndp_disclosure_flag:
channel: slack
body: |
NDP DISCLOSURE REVIEW NEEDED
SKU: {sku_name}
Source DSP: {source_dsp}
Source state: {source_state}
Required label language: "{required_label_language}"
Shelf talker draft: {shelf_talker_draft}
Website disclosure draft: {website_disclosure_draft}
distributor_handoff_packet:
channel: email
subject: "Release handoff: {sku_name} for {distributor_name}"
body: |
Hi {distributor_contact},
Attaching the release handoff for {sku_name}, launching {release_date}.
In the packet:
1. Lab COA: {coa_url}
2. Approved COLA: {cola_url}
3. Sample case ship date: {sample_ship_date}
4. Account placement plan: {placement_plan_url}
5. Marketing collateral: {collateral_url}
Reach back any time on questions.
{distillery_name}
```
## Memory keys
```yaml
memory:
- key: distillery.production_runs[{run_id}]
description: Each production run with mash bill, dates, PG produced
schema: { mash_bill: string, ferment_start: date, distillation_date: date, pg_produced: number }
- key: distillery.rickhouse[{barrel_id}]
description: Each barrel with fill date, mash bill, position, current state
schema: { fill_date: date, mash_bill: string, position: string, status: string }
- key: distillery.pg_ledger
description: Running proof gallon ledger across production, storage, processing
schema: { production_pg: number, storage_pg: number, processing_pg: number, last_reconciled: datetime }
- key: distillery.cola_status[{sku_id}]
description: COLA submission status per SKU
schema: { submitted: date, status: string, approved: date, expires: date }
- key: distillery.fonl_status[{sku_id}]
description: FONL filing status for formulated products
schema: { submitted: date, status: string, approved: date }
- key: distillery.ndp_disclosure[{sku_id}]
description: NDP sourcing disclosure per SKU
schema: { is_ndp: bool, source_dsp: string, source_state: string, disclosure_language: string }
```
## Required integrations
| Integration | Purpose | Read | Write |
|--------------------------|--------------------------------------------------|------|-------|
| WhiskeySystems / DistillerySoft | Production database (rickhouse, runs) | yes | optional |
| TTB Online account portal | COLA and FONL submission status (read-only) | yes | no |
| Distributor portal | Account placement and order data | yes | optional |
| Email provider | Distributor and operator messaging | no | yes |
| Slack | Operator alerts | no | yes |
| OpenClaw Memory | PG ledger, COLA status, NDP disclosure | yes | yes |
| OpenClaw Heartbeat | Weekly and monthly cadences | yes | yes |
Write-backs to WhiskeySystems or DistillerySoft are optional. Most
distilleries start read-only.
## Compliance notes
The skill compiles TTB Forms 5110.40, 5110.43, and 5110.74 for operator
review. It does not file with TTB. The operator submits through TTB Online
or TTB Pay.gov.
The skill tracks COLA and FONL submission status but does not submit COLA
or FONL applications on the operator's behalf.
The three-tier system (producer / wholesaler / retailer) compliance is
jurisdiction-specific. The skill flags any proposed action that would
cross a tier line and routes the final call to the operator.
NDP source-state disclosure language follows current TTB labeling
regulations as of the last skill update. The operator is responsible for
re-checking the disclosure rules against the latest TTB guidance for each
SKU release.
## Configuration
```yaml
config:
distillery_name: "Your Distillery"
dsp_number: "DSP-XX-12345"
monthly_pg_target: 500
primary_mash_bills:
- id: bourbon_house
ratio: "70/20/10 corn/rye/malt"
- id: rye_house
ratio: "95/5 rye/malt"
- id: single_malt
ratio: "100/0 malt"
rickhouse_position_count: 480
barrel_type: "53-gal char #4 new American oak"
management_system: whiskeysystems # or "distillerysoft", "distil_x"
ndp_sourcing_enabled: false # set true if any SKU sources from another DSP
approval_mode: operator_approves_all # TTB filings ALWAYS operator-approved by design
autonomous_template_allowlist:
- weekly_production_schedule
- distributor_handoff_packet
ttb_filing_window_nag_days: [10, 12, 14]
pg_ledger_variance_alert_threshold: 0.5
```
## Quick install
```bash
mkdir -p ~/.claude/skills
mv distilleries.md ~/.claude/skills/distillery-production-and-ttb.md
# Edit the config block to match your DSP
```
Launch OpenClaw and the skill is live. Trigger it manually with
`compile TTB monthly report` or `draft weekly production schedule` or wait
for Heartbeat to fire on the configured cadence.
## Want it wired to your stack?
This SKILL.md is the starting point. If you want it plugged into your
specific DSP setup, mash bill lineup, rickhouse, and distributor mix on a
fixed-price two-week clock, the door is at
https://www.adhirajhangal.com/work
Install in 60 seconds
- 1
Drop the file into your OpenClaw skills directory
Save the downloaded distilleries.md as ~/.claude/skills/distillery-production-and-ttb.md (or your project-level .claude/skills/). OpenClaw picks up new skill files on next agent launch.
- 2
Connect WhiskeySystems or DistillerySoft and your TTB account portal
Edit the integrations block to point at your WhiskeySystems or DistillerySoft export, your TTB account portal (read-only for COLA status), and your distributor portal if your wholesale partner exposes one. Read access is enough to start; the skill never auto-files with TTB.
- 3
Launch in approval mode and keep all TTB filings operator-approved
Start with the operator approving every production schedule, distributor message, and TTB report draft for the first two weeks. The skill's default is to always route TTB Form 5110.40 / 5110.43 / 5110.74 filings, COLA submissions, and FONL changes to a human. After two weeks, flip the distributor handoff drafts and the routine production schedule to autonomous; TTB filings stay human-approved by design.
Example conversation
You
Compile last month's TTB Form 5110.40 production report and tell me where the variance is.
Agent
TTB Form 5110.40 (Report of Production Operations) compiled for April 2026. Total proof gallons produced: 1,847 PG. Breakdown: bourbon mash bill (70/20/10 corn/rye/malt) 1,210 PG, rye mash bill (95/5 rye/malt) 412 PG, single malt 225 PG. Versus March 2026: bourbon +8%, rye -12%, single malt new this month. Versus same period 2025: total +22% (consistent with our annual growth plan). Storage: 1,847 PG entered new barrels (642 new 53-gal char #4, 1,205 PG split into the existing rickhouse positions). Lost in production: 18 PG (0.97%, within normal range). Draft is queued for your review. I have NOT submitted to TTB; the filing window for April is May 1-15.
Founder-led · 14 days
Want this production and TTB compliance coordinator live in your distillery in 14 days?
Adhiraj ships OpenClaw AI agents into real businesses. Short discovery to map it to WhiskeySystems and the TTB account portal, build in 14 days, then optional ongoing support so your OpenClaw system keeps working.
Build it with meCommon questions
Will this work for a 50 PG/month nano distillery or a 5,000 PG/month craft producer?
+
Both. The skill is designed for the 50 to 5,000 proof gallon per month range. Below 50 PG the TTB compliance workload is light enough that the skill is overkill. Above 5,000 PG the distillery typically has a dedicated compliance officer and the skill is a starting point that needs operator-specific extension.
Does this file with TTB on my behalf?
+
No. By design, the skill never auto-submits to TTB. It compiles the production, storage, and processing data into the format of Forms 5110.40, 5110.43, and 5110.74, surfaces the variance from prior months, and queues the draft for operator review. The final filing through TTB Pay.gov or TTB Online stays in the operator's hands. The same applies to COLA submissions and FONL filings.
Which distillery management systems does it integrate with?
+
WhiskeySystems and DistillerySoft are the dominant craft distillery compliance management tools and the skill includes integration prompts for both. Distil-X and OrchestratedSPIRITS also work through CSV export. For operators running on a custom spreadsheet (still common at the nano scale), the skill works directly off the spreadsheet.
How does the proof gallon math work?
+
The skill carries the standard PG calculation: wine gallons times proof divided by 100. Every transformation (production, gauging, transfer-in-bond, withdrawal, bottling) updates the running PG ledger. The skill cross-checks the ledger against your WhiskeySystems or DistillerySoft figure each day to catch divergence early.
Does it handle NDP disclosure?
+
Yes. For brands that source distillate from another DSP (the NDP model), the skill tracks the disclosure language required on the label, on the back-bar shelf talker, and on the website. TTB requires the source-state disclosure (the 'Distilled in [STATE]' language) on the label. The skill flags any new SKU that touches NDP sourcing before the COLA goes out.
Can it handle FONL filings for botanical or flavored products?
+
It compiles the FONL data (Formula and Process for Nonbeverage Products) for the operator to file. It does not file the FONL on your behalf. For gin, flavored whiskey, liqueurs, and other formulated products, the FONL filing window matters and the skill flags the timing against your launch calendar.
Can I modify this skill?
+
Yes. MIT licensed. Edit the mash bill templates, the rickhouse positions, the distributor handoff packet, the NDP disclosure language. Most distilleries fork it within the first month to match their specific lineup and brand voice.
What does this cost to run on top of OpenClaw?
+
Token cost is light. A representative single-DSP distillery producing 500 PG per month sees monthly token spend in the $25 to $60 range. The skill batches the monthly TTB report compilation to minimize per-day inference.
How does this compare to WhiskeySystems and DistillerySoft directly?
+
WhiskeySystems and DistillerySoft are excellent at the production and reporting database job each was built for. The OpenClaw skill reasons across production, TTB compliance, COLA timing, NDP disclosure, and distributor handoff at the same time. Most distilleries keep their management system and add this skill on top for the cross-system operator workflows.
Can OpenClaw Consult build a customized version for my distillery?
+
Yes. The free SKILL.md is the starting point. If you want it wired into your specific DSP setup, mash bill lineup, rickhouse, and distributor mix on a fixed-price two-week clock, the door is at openclawconsult.com/hire.
Want the full implementation playbook?
Read the deep-dive guide for distilleries
The playbook covers workflows, software integrations, compliance, ROI math, and a four-week rollout plan. The skill file above is a working slice of that build.
Read the distilleries playbook →Related free skills
Free OpenClaw Skill for craft breweries
A working OpenClaw skill for production craft breweries running 500 to 15,000 BBL annual volume. Owns the brewhouse production schedule, distributor reorder coordination, taproom event operations, and Brewers Association reporting, all from one SKILL.md drop-in.
Free OpenClaw Skill for bakeries
A working OpenClaw skill that runs the custom-order and wholesale workload for a working bakery. Custom cake intake, decorator calendar, lead-time enforcement, wholesale DSD coordination, cottage-food compliance routing, all from one SKILL.md drop-in.
Free OpenClaw Skill for juice bars and smoothie shops
A working OpenClaw skill for juice bars, smoothie shops, and cold-press operations. Owns the 1/3/5-day cleanse subscription cadence, the HPP cold-press production schedule, the corporate wellness account book, and the açaí bowl daily ops, all from one SKILL.md drop-in.
Want it wired to your stack?
The free skill is the starting point. If you want it plugged into your actual software, on a fixed-price two-week clock, with the founder writing every line, this is the door.