How Bev Deck works

Follow every beverage from plan to payment.

Plan production, make it, package it, track what you have, move it, sell it, get paid, report on it, and file it. Then feed what you learned back into the next plan.

Start Free Trial Book a Walkthrough

Where the work happens

One system, however many places you make and store your product.

In Bev Deck every site is a record in its own right: each one is configured for the work that actually happens there, and every production batch, inventory movement, order, and report carries the facility it belongs to.

Unlimited facilities and sub-locations under one company

Mark a facility company owned, third-party contract, or third-party storage (3PL)

Enable production, cellar, and taproom operations per facility

Filter any report to one facility without running separate instances

Plan it

See the week, open the work.

Production runs, packaging, transfers, and releases sit on one calendar, colored by product and filtered by facility. The same records drive a chronological agenda for the day ahead and a top-down map of what is in every tank right now, so nobody keeps a private copy of the schedule.

One calendar for brewing, cellaring, packaging, and release events

Filter to a single facility or a single activity type without leaving the view

A chronological agenda for the day, and a top-down cellar map of every tank

Give sales and operations the same forward-looking plan

Bev Deck production calendar for September showing brew, packaging, transfer, and release events across facilities

Coordinate the release

Get sales and marketing involved in the release before it ships.

Getting a new product out the door takes production, marketing, sales, and logistics each finishing their part in the right order. The readiness board puts every product in the window on a row and every one of those inputs in a column, so the thing actually holding up the release is a red cell everyone sees.

Every product in the window scored across label, beer info, allocation, packaging, and release

Cells read complete, action due, or action overdue — no status meeting required

Workflow templates raise tasks off the release date and assign them to an owner

Task notifications delivered in app or as a Slack DM

Bev Deck readiness board showing per-beer readiness across production, label, beer info, allocation, packaging, and release

Produce it

Track production batches from planned work to finished product.

Whether product is made in-house or coordinated with a contract facility, batch activity stays connected to the rest of the operation. The cellar reads as a top-down map rather than a list: every fermenter and brite tank, what is in it, and how long it has been there.

Track production timing, status, and facility activity

Every tank on one map, with the batch in it and its age

Keep product, packaging, and release context on the same batch record

Bev Deck cellar view showing every fermenter and brite tank as a top-down map, each with the batch it holds and how long it has been there

Package it

Package what sales already promised.

Set packaging targets by channel before the run, share them to Slack so the crew sees the same plan, and let Bev Deck carry the call on what to cut and what to fill when the tank comes in short or long.

Plan packaging targets by format and channel

Share the run to Slack so the floor works from one plan

Get a decision on over and under runs before the line starts

Bev Deck packaging summary for a run in progress, showing taproom and distributor targets by format, units filled against them, and guidance on which format to prioritize if the run falls short and which to put the overage into

Track it

Know what is on hand, where it is, and how old it is.

Finished goods are tracked by date-coded lot, so the on-hand grid shows count and freshness.

On hand by product, format, and facility, graded cell by cell on the freshness of the oldest lot behind it

Graded against the date code printed on the can — the only identity the person holding it can read

Lot detail carrying both the batch number and the printed date code

Physical counts taken by SKU where the stock is, resolved to lots back at the desk where the lot list is on screen

Bev Deck beer on hand grid by beer and package format with per-cell freshness indicators

Move it

A shipment is never held up by paperwork that has not caught up.

Transfers between facilities, sub-locations, taprooms, and 3PL are all one document type, so a pallet moving anywhere is the same record. When the book and the floor disagree, the movement still goes out: the exception is recorded against it, and the correction can be made from whichever screen you are already in rather than by unwinding the shipment.

Transfers between facilities, sub-locations, taprooms, and 3PL on one document type

Ship on a stock position that is behind, with the exception recorded against the movement

Bills of lading with load photos, returned empty kegs, and a PDF out to email or Slack

Correct from any screen that touches the activity, without reversing the shipment

Multi-warehouse wholesale movements carry the facility they left from on every line

Bev Deck inventory movements ledger showing taproom depletions, distributor shipments, and internal transfers between facilities as one document type, with completed and in-flight movements side by side

Decide what is next

Decide what to package next with the whole chain in view.

Coverage reads recent sell-through against the stock that is actually on hand, then projects it forward week by week against the production plan. Potential out-of-stocks and overstocks surface in time to adjust the plan.

Days of cover per product and format, projected forward by week

Flags for out of stock, code risk, below target, and overstocked

Taproom and wholesale read separately against the same packaged stock

Packaging targets netted against what was actually packaged and moved

Bev Deck production planner wholesale coverage grid, every beer and format with its days of cover projected forward six weeks, colour-coded where the weeks run to out of stock, code risk, below target and overstocked

Sell it

From order to paid invoice without re-keying anything.

An order carries its own pricing and its allocated lots, and the invoice is projected from the order itself. QuickBooks stays the accounting system: Bev Deck re-prices the order against your current price lists every time you open the sync dialog and tells you whether the invoice already sitting in QuickBooks still matches — before you send anything, not after a customer queries it.

Pricing groups, with scheduled changes that activate on their own date

Allocation down to the lot, with batch number and date code on every line

One-click invoice sync, triggered when the sales work is finished

Re-checked against your price lists every time you open it

Bev Deck order allocation showing order lines drawn from specific lots with batch numbers and date codes

Stay traceable

Every invoice line still points at the stock that filled it.

An order raises one fulfillment movement, the movement carries the bill of lading that rode with the truck, and the invoice is projected from the order itself. The figure in QuickBooks and the pallet that left the dock are the same record followed forward, not two systems reconciled by hand.

One order, one fulfillment movement, no double entry

Lot and date code recorded where the stock actually left

Invoice checked against the order every time you open it

Sales order
Customer, lines, pricing channel, terms.
Entered once.
Fulfillment movement
One per order.
Proposes the oldest lots; records the ones actually picked.
Bill of lading
Signed consignee.
Kegs out against empties back.
QuickBooks invoice
Re-checked against the order every time you open it.

Projected from the order, not from the shipment

Bev Deck re-prices the order and compares it to the stored invoice before the sync dialog shows you anything.

Report it

Build the report once, then stop rebuilding it.

Report configurations save as named views — kept private or shared with everyone at your company, and one can open by default. Every report reads the operational record directly, so production and sales answer on the same axis instead of being reconciled in a spreadsheet afterwards. And every view answers in barrels, case equivalents, or units on one control, so the number on screen is already in whatever unit the conversation is being had in.

Saved custom views across production, sales, inventory, and revenue reporting

Barrels, case equivalents, or units — with yield — by facility, format, and period

Produced against sold on one period axis, split by facility and by channel

Year-over-year comparison on any monthly, quarterly, or annual view

Bev Deck production report showing a saved monthly view named Monthly Barrelage, read in case equivalents, with brewed, packaged, and average yield by facility

File it

The filing is already written when the quarter closes.

The filings read the same operational records the reports do. The quarter opens at the prior quarter's filed ending, the operational lines come out of production and removals, and the federal form is filled and downloadable — populated rather than transcribed.

TTB Brewer's Report of Operations and the federal excise return as auto-filled PDFs

Each quarter opens at the ending balance the previous quarter was filed on

Arizona Form 835 generated line by line from in-state distributor invoices

Production-to-inventory controls checked before the return is filed, not after

These are beer forms. Cider, RTD and additional state reporting are on the roadmap

Bev Deck TTB Quarterly Brewer's Report of Operations showing the quarter opening at the prior quarter's filed ending, operational lines in barrels, and a matched production-to-inventory control

Optimize it

Close the loop: what a SKU earns, and what the plant can actually run.

Two reviews that set up the next plan rather than the current week. Most systems built for this industry stop at gross profit. Bev Deck carries ingredient cost, packaging cost, excise tax, and freight down to gross profit per unit, then allocates facility overhead per volume to reach the net profit the SKU actually contributes. Scenarios modelled against a saved baseline test what a price, volume, or facility-split change would do to it. Alongside it, the capacity planner measures what the plant actually ran — tank utilization, turn times, and labor against a working day — to plan production optimizations for your product mix, equipment, and staff.

Revenue, ingredient cost, packaging cost, excise tax, and freight per unit

Facility overhead calculated per volume

Net profit per SKU, weighted by the volume actually produced

Scenarios for price, volume, and facility split, measured against a saved baseline

Fermenter and brite utilization by volume and by time

Turn times, yield, and labor utilization over any date range

Model a change in product mix against your historic data

Bev Deck profitability planner comparing a saved costing baseline against a November price increase scenario, showing base and scenario price per unit, projected output in barrels, net profit per barrel, and the change in total net for each beer and format, with the production split between two facilities on every line

And the parts of the business that are not on every operation's list.

These run on the same records as everything above, so turning one on does not mean maintaining a second version of your inventory.

Taproom and draft

Square transactions pull daily and map to your SKUs. Kegs deplete by the glass from a service lot, and draft loss lands per keg and per brand.

Barrel program

Barrel inventory with supplier detail and aging duration, filled by rack logs recorded against the batch that went into them, and blended barrel to barrel.

Cask room

Every cask tracked as its own asset through the statuses a cellarman works in, with QR asset and fill tags, and filled-against-returned reconciled per facility.

Keg deposits

Deposits linked to their invoices and mapped to a QuickBooks liability account, debited and credited automatically on shipment and return.

Roles and access

Fine-grained permissions per area of the app, so the person counting the cold room and the person closing the books do not need the same access.

Before you book a call

What Bev Deck does not do yet.

The scope is deliberate. Bev Deck is strongest when production is outsourced, or when there are more facilities, brands and partners than one system was built to hold. These are the gaps, so you find them now instead of three weeks into an evaluation.

Raw materials, purchase orders and vendor management. If you buy and receive ingredients yourself, that stays wherever it lives today. It ships with the production module, targeted for Q4 2026.

Recipes, brew logs and fermentation tracking. Bev Deck starts at the batch — the production module is in build underneath what you would adopt now, targeted for Q4 2026.

Compliance outside beer. The TTB report, the federal excise return and Arizona Form 835 are beer forms. Other products and other states get built when a customer needs them.

Bev Deck is built for many facilities. It does not require them.

Set up the facility you run today and add brands, partners and locations as they come — or book a walkthrough and we will map Bev Deck to how you already work.