One batch, three formats, three sales channels
Spreadsheets break on a simple question: how much of the latest IPA is left, across every format, and what's shipping first to the bar that orders weekly? A given batch splits into kegs, bottles and cans, each with its own sell-through rate and its own channel — bars take kegs, bottle shops take bottles, the taproom sells everything by the piece.
There's also a production calendar to track: a batch has a brew date, a fermentation period, a packaging date, before it's even available to sell. Beer still in the tank isn't stock yet — it's a promise of stock, and confusing the two means announcing availability that doesn't exist yet.
Your batches, your formats, your clients: structured
Describe your brewery: "We brew regular recipes and one-off special batches. Each batch has a brew date and stock per format (keg, bottle, can). We sell to bars and bottle shops at trade prices, and direct at the taproom. Orders draw down stock per format. I want to see stock by batch and format, orders to prepare, and revenue per sales channel."
The generated application follows this structure exactly: batches with their recipe and date, stock per format, clients with their category, orders that decrement the right format's stock, and a dashboard that answers questions from the fermentation cellar as much as the office.
- Batches, recipes and production dates
- Stock per format (keg, bottle, can)
- Trade clients (bars, bottle shops) and individuals
- Orders and stock movements per format
- Dashboard: stock, orders, revenue per channel
A fermenting batch isn't stock yet
A brewery that describes its production statuses (fermenting, conditioning, packaged, available) gets a tool that separates "what exists" from "what's for sale" — a batch still in the tank never shows up as available stock until it clears that step, so nobody promises a bar a beer that isn't ready.
The generated demo data simulates a living brewery (batches, varied clients, order history) so you can judge the tool right away.
The brewery's own tool, not a distributor's subscription
The application belongs to the brewery: exportable code (ZIP, GitHub push), hosting wherever you choose, or the dedicated URL provided. The client file and production history stay part of the business's assets.
Free Discovery plan for your first application; Pro (€25/month) and Max (€149/month) to iterate, with cost shown before every generation.
Typical entities generated
- Batch
- Recipe
- Client
- Order
- Stock per format
Generated screens
- Stock by batch and format
- Client record: category, order history
- Orders to prepare
- Batch tracking (brewing, fermentation, packaging)
- Brewery dashboard
Dashboard indicators
- Remaining stock by batch and format
- Batches currently fermenting
- Orders in preparation
- Revenue per channel (bars / bottle shops / taproom)
Frequently asked questions: craft brewery
Can regular batches be distinguished from special ones?
Yes: describe your batch types (regular recipe, limited edition, collaboration) and the generated structure distinguishes them, each with its own production tracking.
Could a fermenting batch show up as available by mistake?
No, provided you describe it: a production status (brewing, fermentation, conditioning, packaged, available) means only stock that's actually packaged counts as available to sell.
Are trade prices (bars, bottle shops) handled separately from taproom pricing?
Describe your client categories and their prices: they become structuring fields on client records and orders.
Does the application cover regulatory matters (excise duty, declarations)?
No, regulatory filings have their own dedicated tools. The application covers your production and sales tracking; its structured data makes those filings easier all the same.
Does the brewery own the tool?
Yes: exportable code (ZIP, GitHub), hosting wherever you choose. The tool and its production history are part of the brewery's assets.