SaaS vs Custom

Mid-size craft brewery (Brisbane, 8-person team, $800k annual revenue). Thursday 7:00am: brew day. Head brewer Jack: water heating (65L mash tun, 68°C strike water). 2-row pale malt + caramel 60 (grain bill recorded on whiteboard, photo backup as sole record). Mash doughing-in: 45kg pale, 8kg caramel (scales used, no production log). Mash thickness: 2.5 liters water per kg grain (eyeballed, Jack's experience). Sparge: 48L water, 40-min fly-sparge (manual, no timer alert). Wort collected: ~60L (target 65L, 5L shortfall untracked = yield loss, costs $35 in grain waste). Boil: 90 mins, kettle temperature estimated (no probe). Hops: 25g Simcoe 60-min (written note), 15g Citra 15-min (photo), 10g Amarillo flame-out (verbal, Jack memorizes). No logging system. Fermentation: wort cooled (chiller, 20°C in 30 mins), yeast pitched (2 smack packs eyeballed, viability unknown, no rehydration). Tank 4 (100L conical) logged via Post-It "OG 1.042, Day 1." Day 3: bubbling visible, no gravity check. Day 7: gravity dipped (hydrometer = 1.010, recorded on Post-It). Day 10: cold-crash initiated (tank dialled to 2°C by hand, no alert). Day 12: kegging (siphon transfer, sediment included, keg pressurized ~22 psi estimated). Tap room POS: 4 house taps + rotating guests. Tuesday evening: 120 customers, 240 pints estimated (Jake counts by hand, ±10% variance). Square reader: $2.8k revenue logged. Food sales: snacks untracked (shoebox receipts, month-end reconcile pain). Inventory: Tank 4 depleting, Jack guesses "3 taps running, ~2 kegs/week each, maybe 1 week left?" Reactive brewing scheduled (no advance plan). Wholesale: 8 bottle shops contacted (hand-written notes, one call per shop). Crafty Bottle Shop: "20 cases IPA, deliver Tuesday." Real Ale House: "10 cases, Friday pickup." Brewery Mate: "pass, overstocked." No order form, no manifest, no delivery confirmation. Invoices: hand-printed (product, quantity, price = $54/case, no ABV, no excise cert). Cash paid (no receipt). RSA: bartender Jake serves 120+ customers (some tipsy, no ID logged, no refusal record, liability zero-documented). Customer over-served (5+ beers), drives away, police stop, breathalyzer 0.15 BAC. Customer sues (over-service claim). Insurer demands: RSA logs (zero found). Claim denied. Legal liability $35k. Excise compliance: each batch needs (1) batch number, (2) ABV calculated, (3) excise tax per litre ($47.50/L × ABV%). Year-end tax: accountant asks "total litres Q4? ABV per batch? Excise liability?" Tim: "I have Post-Its and photos." Accountant: "audit risk $3–5k penalty if batches undocumented." Food safety: kitchen (chip fryer, pretzel warmer). Health inspector (random, June): "temperature logs? Traceability? Cleaning schedules?" Checklist blank May–July. Fine: $2.5k + retraining 8 hours. Total friction: batch cert liability ($3–5k audit risk), RSA liability ($35k exposure, claim denied), excise uncertainty ($12k unverified), food safety fine ($2.5k), wholesale chaos (2 orders cancelled = $2.16k lost), tap room waste (3 kegs unused = $600), POS leakage (10% variance = $4.8k/year). **Total: $48.2k annually**. Tim evaluates: custom brewery software ($35k build + $3k/year ops).

Six Features Custom Brewery Software Delivers

1. Brew-Day Production Schedule — Grain Bill Entry, Water Volume + Temperature, Mash Profile, Sparge Timer, Boil Timeline, Hop Schedule, OG/FG Gravity Logging, Batch Numbering, Yield Calculation

Current: whiteboard + Post-It + photos, no traceability, 5L yield loss per 60L batch untracked. New system: brew-day dashboard. Thursday 6:00am: Jack selects "New Brew." System prompts: (1) batch name (IPA #23), (2) grain bill (45kg 2-row, 8kg caramel 60, system auto-calculates expected gravity 1.042, colour 25 SRM), (3) water volume (65L, temperature target 68°C). Jack confirms (system shows "strike water heating 65L to 68°C — [START/ALERT when ready]"). Alert: water at 68°C, system notifies (phone buzz). Mash dough-in: Jack doughed grain + water, system timer starts (mash duration target 30 mins, displays countdown [30:00 → 00:00]). At 30-min mark: system alert "mash complete, begin sparge." Sparge: Jack inputs (target runoff volume 65L, sparge water temp 76°C [system calculates for mashout step, optional]). Timer: 40-min fly-sparge countdown. System receives (optional flow meter on sparge valve, or Jack logs manually every 10 mins "current runoff: 45L at 20-min mark"). Runoff complete: Jack logs "total runoff collected: 62L" (system notes: expected 65L, actual 62L = 3L shortfall [acceptable, <5%], system highlights "yield 95% normal"). Boil: kettle heating, system timer 90 mins (displays countdown [90:00 → 00:00]). Hop schedule: Jack inputs (hop 1: 25g Simcoe @ 60-min [system alerts at 60-min, 45-min, 15-min countdown], hop 2: 15g Citra @ 15-min [alerts], hop 3: 10g Amarillo @ flame-out [alerts]). System records every hop addition (timestamp, weight, IBU contribution auto-calculated based on alpha acid % [Simcoe 12.5% = 25g × 12.5% × utilization = ~20 IBUs, system totals ~28 IBUs final]). Flame-out: system timer ends, Jack confirms "boil complete, cooling initiated." Gravity: Jack dips hydrometer (OG 1.042, logs into system). System records: "batch #IPA23, OG 1.042, expected FG 1.008 (ABV = 4.5%)." Batch ID: system auto-assigns (BREW-20260612-IPA-023). Multi-batch concurrent: Friday, Jack brews 2 batches (IPA #24 + Stout #15). System manages both (separate timers, schedules, logs). Batch IPA #24: BREW-20260613-IPA-024, OG 1.041. Batch Stout #15: BREW-20260613-STOUT-015, OG 1.065. Inventory: system links batches to tank assignments (IPA #23 → Tank 4, Stout #15 → Tank 2). **Value: brew-day traceability (every batch timestamped, gravity logged, hop schedule verified = zero guessing), multi-batch management (concurrent brews tracked separately, no confusion), yield calculation (5L shortfall identified, cost $35 saved via efficiency insight, repeated batches prevent waste), ABV auto-calculated (enables excise cert generation + tap room alcohol content labelling for compliance).**

2. Fermentation Tank Tracking — Temperature Logging, Gravity Readings, Days Fermenting Countdown, Cold-Crash Scheduling, Carbonation Status, Tank Status Dashboard, Alerts (Off-Flavor Risk, Stuck Fermentation), Ready-to-Package Timeline

Current: Post-It on tank, gravity hydrometer dipped 2–3 times, cold-crash set manually, no automated alerts. Risk: stuck fermentation (yeast dies, batch unsalvageable, $300+ loss undetected). New system: fermentation dashboard. Thursday brew day (IPA #23 pitches yeast, OG 1.042, Tank 4). System creates: fermentation profile (target FG 1.008, estimated fermentation timeline 10–14 days, expected ABV 4.5%). Temperature: Tank 4 equipped (optional wireless sensor, or Jack logs daily). System logs (day 1 sensor: 20°C ambient, yeast pitched). Day 2: sensor reads 21°C (exothermic fermentation heating), system notes "normal vigour, yeast healthy." Day 3: sensor reads 22°C, system alert "fermentation temp peak, monitor for diacetyl risk if temp >23°C." Gravity: Jack dips hydrometer every 2–3 days (logs manually or scans barcode on hydrometer [optional]). Day 3: gravity 1.030 (system calculates attenuation 28%, plots trajectory [1.042 → 1.030 in 3 days = on pace for FG 1.008 by day 12]). Day 7: gravity 1.012 (attenuation 71%, pace check: "2 days behind, likely done day 14"). System timeline: (1) day 1–3 = active fermentation (vigorous), (2) day 4–10 = steady fermentation (quiet), (3) day 10–12 = finish phase (gravity stable <0.004 change day-to-day). Day 10: gravity 1.008 (stable, system alert "fermentation complete, ready for cold-crash"). Cold-crash: Jack sets Tank 4 temperature target (2°C, duration 48 hours). System monitors: day 10 2:00pm cold-crash initiated, day 12 2:00pm complete (alert "tank ready for kegging"). Off-flavor risk: system tracks (fermentation days 1–12 at 21–22°C = clean lager temperature, low phenolic risk). If temp spiked >24°C, system flags "off-flavour risk (fusel alcohols or esters), recommend cold-conditioning 5 days, sensory panel test before packaging." Stuck fermentation: system models (attenuation 1.042 → 1.012 in 7 days = normal pace, FG 1.008 expected day 12). Day 12 gravity check: 1.009 (not dropping toward target 1.008, system alert "fermentation stalled, possible stuck yeast, investigation required"). Jack: pitches yeast energizer, stirs tank (aeration), re-checks day 13 (gravity 1.008, alert clears "fermentation resumed, on track"). Carbonation: packaging kegs (pressurized CO2), system notes (22 psi pressure, system recommends "check pressure every 3 days, maintain 22 psi for carbonation stability"). Tank dashboard (visual): Tank 4 = "IPA #23, OG 1.042, current gravity 1.008 (fermentation complete), temp 2°C (cold-crashed 24 hours, ready day 12), ready to keg." Tank status colour: green (ready). Tank 2 = "Stout #15, OG 1.065, current gravity 1.020 (fermentation active), temp 22°C, 4 days to cold-crash." Tank status colour: yellow (in-progress). **Value: temperature logging (stuck fermentation detected early, $300+ batch loss prevented), gravity tracking (attenuation modelled, FG prediction accurate, packaging timeline known 5 days advance = inventory plan accurate), off-flavour alerts (batch quality preserved, test-before-packaging prevents customer complaints = reputation intact), cold-crash scheduling (batch pipeline synchronized, kegging day known, tap inventory planned).**

3. Canning & Kegging Line Automation — Batch Packaging Yield, Cans/Bottles Per Batch, Packaging Date (Link to Batch Roast Date), Carbonation Level Tracking, Quality QC Log (Head Space, Sealing, Sample Test), Expiry Labelling, Distributor Manifest Generation

Current: Tank 4 (100L) kegged via siphon, sediment transferred, 22 psi guessed, no QC. Cans: 24-can cartons packed by hand, label printed by hand (no date, no batch number), no expiry. New system: packaging dashboard. Monday (IPA #23 cold-crashed, ready to keg). System shows: "Tank 4 ready → packaging module." System calculates: tank 100L (minus 5% loss to sediment, yeast = 95L usable = 79 pints = 3.3 kegs [assuming 24-pint kegs]). Kegging: Jack selects "keg 1 of 3, IPA #23." System auto-fills (batch ID BREW-20260612-IPA-023, product name "IPA", batch date 12/6/26, ABV 4.5%, packaging date 13/6/26). Jack connects siphon (transfer starts). System monitors (optional pressure sensor, or Jack logs manually "keg 1 filled at 2:00pm"). Keg 1: filled, system records (volume ~25 litres, batch BREW-20260612-IPA-023-KEG-001). Carbonation: system prompts "target carbonation 2.5 volumes CO2, pressure 22 psi at 4°C." Jack logs "CO2 pressure set 22 psi." System records (carbonation date 13/6/26, pressure 22 psi). QC log: system prompts "keg sealed? Purged with CO2 pre-fill? No sediment visible in sample?" Jack confirms (3 checkboxes, system logs QC pass). Keg status: green (ready for tap). System stores: Keg 001 metadata (IPA #23, filled 13/6, carbonation 22 psi, QC pass, ready-to-tap). Canning line: separate batch (Pale Ale #18, cold-crashed). Tank 65L = 54.3L usable = ~228 cans (assuming 240ml per can [6-pack metric]). System calculates: 228 cans ÷ 6-pack = 38 × 6-packs. Canning machine (label input): system generates (batch label "PALE ALE, Brewed 10/6/26, Packaged 13/6/26, ABV 5.1%, Best By 13/9/26 [90-day shelf-life estimate for IPA/Pale, conservative]"). Expiry: system calculates (packaging 13/6 + 90 days = 13/9/26, label printed). Jack loads label into canning machine. Canning process: 6 cans filled per carton, 6 cartons per box (36 cans per box), 38 packs = rounds down to 38 × 6 = 228 cans = 6.3 boxes (38 complete boxes, + 4 overflow cans). System tracks: boxes 1–38 = full (each marked "BOX-1 to BOX-38, PALE-ALE-18"), overflow 4 cans = "PALE-ALE-18-OVERFLOW." QC: Jack opens carton 15 (random check), inspects 6 cans (head space 1cm [target = 0.5–1.5cm, acceptable]), sealing (no leaks, solid), colour (golden, no cloudiness). System logs "carton 15 QC pass, sensory sample taste (light citrus, clean, ABV apparent, shelf-stable assessment PASS)." Distributor manifest: system generates (for wholesale delivery). Example: Crafty Bottle Shop order (20 × 6-packs IPA #23). System pulls (38 × 6-packs Pale Ale #18 available). System asks: "Crafty order is Pale Ale, stock available. System suggests: Pale Ale 20 × 6-packs from batch PALE-ALE-18 [packaged 13/6, expiry 13/9, 92 days shelf-life]. Confirm assignment?" Jack confirms. System generates manifest: (1) order ID CRAFT-IPA-001 (renamed to Pale Ale assignment), (2) product "Pale Ale 6-pack cans", (3) quantity 20 × 6-packs, (4) batch PALE-ALE-18, (5) packaging date 13/6/26, (6) expiry 13/9/26, (7) ABV 5.1%, (8) carton numbers BOX-1 to BOX-4 + overflow (20 packs = 3.3 boxes, system optimizes carton assignment). **Value: packaging yield calculated (100L tank → 79 pints → 3.3 kegs exact, zero guessing), batch traceability per keg/can (Keg 001 links to batch BREW, batch ID, brew date, ABV, expiry — every package labelled), expiry automated (90-day default adjustable per style, label printed, no hand-writing errors), QC logged (head space, sealing, taste checks recorded, batch quality verified before wholesale), distributor manifest auto-generated (batch assignment, expiry visibility, carton numbers tracked = delivery accuracy 100%).**

4. Tap Room POS Integration — Pint Tracking per Tap, Hourly Inventory Depletion, Revenue Reconciliation, Food Sales Tracking, Cash Drawer Reconciliation, Weekly Inventory Snapshot, Reorder Triggers (Keg Depletion Forecast)

Current: Square POS logs revenue, Jake hand-counts pints (±10% variance = $4.8k annual leakage). Food: shoebox receipts, no reconciliation. Inventory: "Tank 4 looks empty soon," reactive brewing. New system: integrated POS. Tap room setup: 4 house taps (IPA, Stout, Pale, Cream Ale), 2 rotating guest taps. Point-of-sale: flow meter on each tap (or Jake logs manually per glass). Flow meter option: tap 1 (IPA) = counter increments 1 per 425ml pour (standard pint). Tuesday evening: customer orders IPA pint, Jake pours, flow meter reads +1 (0425ml = 1 pint recorded). System logs: "19:15, tap 1 IPA, 1 pint, $8 [standard pricing], customer #1." Barcode scanner (optional): Jake scans customer ID (loyalty card) or payment method (tap card). Customer #1: "loyalty member, points awarded 1 (=$0.08)." System tracks customer (repeat visits, favourite tap, lifetime spend). Aggregate: Tuesday evening, 4-hour service (7pm–11pm). Tap 1 (IPA): 45 pints poured, revenue 45 × $8 = $360. Tap 2 (Stout): 30 pints, $9 each = $270. Tap 3 (Pale): 38 pints, $8.50 = $323. Tap 4 (Cream Ale): 25 pints, $7 = $175. Guest tap A: 12 pints, $10 (imported, guest fee) = $120. Guest tap B: 15 pints, $9.50 = $142.50. Total: 165 pints, $1.39k revenue. Square reconciliation: system compares POS tap total (165 pints logged) vs Square transaction total ($1.39k). Match: 100% accurate (no variance, vs 10% hand-count variance = $139 variance eliminated). Food sales: shoebox receipts scanned (camera snapshot, system OCR extracts: "chip bag $3.50, pretzel $4, nachos $5.50"). Manual entry: Jake inputs (chip bag 1 × 3, pretzel 2 × 4, nachos 1 × 5.50 = total $14.50 food revenue). System logs: food revenue $14.50 + tap revenue $1.39k = total $1.40k evening. Cash drawer: 120 customers, 40% cash (48 customers × avg $8.75 [tap + food mix] = $420 cash expected). Jake counts drawer at close (11:15pm): actual cash $415 (vs $420 expected = $5 variance [normal till float ±$10]). System logs: drawer reconcile PASS. Weekly snapshot: system aggregates (Tuesday–Sunday, 7 evenings). Tap 1 (IPA): 320 pints/week, $2.56k revenue. Tap 2 (Stout): 220 pints/week, $1.98k revenue. Tap 3 (Pale): 275 pints/week, $2.34k. Tap 4 (Cream): 180 pints/week, $1.26k. Guests (avg): 95 pints/week, $0.95k. Total: 1.09k pints/week, $8.09k weekly. Inventory: Tap 1 (IPA) serving from Keg 001 (25L = 50 pints, filled Sunday 7/6). Keg depleted (320 pints/week ÷ 50 pints/keg = 6.4 kegs/week). Current: 1 keg (Mon 12/6 = depleted Wednesday 15/6). Reorder trigger: system alert (Monday 12/6, "IPA consumption 320 pints/week, 1 keg active [depletion forecast Wednesday 15/6]. Recommend brew IPA #25 by Friday 14/6, keg ready Friday 15/6, seamless Friday evening service"). Jack schedules brew (Friday, lands keg Saturday morning, tapped Sunday 16/6). Zero tap outage. **Value: pint accuracy 100% (flow meter eliminates hand-counting variance, $4.8k leakage prevented), revenue reconciliation perfect (POS logs match tap pours match cash drawer, no leakage), food integration (shoebox chaos → system logs, reconcile automated), inventory forecasting (consumption 1.09k pints/week, keg depletion predicted 5 days advance, brewing scheduled perfectly, zero tap outages = revenue consistency guaranteed).**

5. Wholesale Distributor Orders & Delivery Tracking — Standing Orders by Venue, Auto-Generate Invoice + Manifest, Batch Assignment, Delivery Schedule, Signature Proof, Payment Tracking, Margin per Venue, Territory Mapping

Current: hand-written notes, 3 phone calls per roast, no invoice, no delivery proof, 2 orders cancelled (chaos). New system: distributor dashboard. Setup: 8 bottle shops registered. Crafty Bottle Shop (owner Sam): standing order (Pale Ale 20 × 6-packs, monthly delivery, net 30 payment, price $54/case). System records: order ID CRAFT-PALE-MONTHLY-001. Rules: (1) product Pale Ale (auto-select latest Pale batch available), (2) quantity 20 × 6-packs, (3) delivery 1st Tuesday monthly, (4) payment net 30. Brewery roasts Pale Ale #18 (Monday 13/6, cold-crash Wednesday 15/6, packaged Thursday 14/6). System scans standing orders: "Pale Ale roasted, Crafty needs 20 × 6-packs, 1st Tuesday delivery (16/6)." System auto-assigns batch PALE-ALE-18 (38 × 6-packs available). Manifest generated: (1) venue Crafty Bottle Shop, (2) product Pale Ale 6-pack, (3) quantity 20 × 6-packs, (4) batch PALE-ALE-18 (packaged 14/6/26), (5) expiry 14/9/26 (90 days), (6) delivery date 16/6 (Tuesday), (7) net 30 payment due 16/7, (8) carton IDs BOX-1 to BOX-4, (9) total invoice $1.08k (20 × 6-packs × 6 cans × $0.90 per can cost + markup = let's simplify: 20 cases × $54/case = $1.08k revenue). Invoice generated: (1) date 14/6/26, (2) due date 16/7/26, (3) line item "Pale Ale 6-pack cans × 20 cases = $1.08k + GST $108 = $1.188k", (4) delivery address Crafty, (5) payment link (online option). Delivery: Jack loads van (40 cartons of 6-packs, ~30kg total). Driver (Jack or Tim) departs 16/6 morning. GPS tracking (optional): system shows van route. Arrival Crafty (11:00am): delivery address, signature app (Sam signs via phone, system logs proof-of-delivery timestamp 11:15am, photo of cartons offloaded). System records: delivery complete, signature Sam (digitally verifiable). Invoice: sent to Sam's email (automated), due 16/7. Sam reviews: "20 × 6-packs, batch PALE-ALE-18, expires 14/9, $1.188k total." Payment: Sam pays online (16/7, system records payment received). Balance: $0. Multi-venue standing orders: (1) Crafty = Pale Ale monthly, (2) Real Ale = IPA bi-weekly, (3) Brewery Mate = Stout monthly, (4) Hop House = Pale + IPA mix quarterly, (5) Craft Central = guest tap rotation (2 × guest-style 6-packs monthly). System manages all (auto-batch assignment, manifest per venue, delivery scheduling, payment tracking). Payment acceleration: net 30 enforced (email reminder day 29, notice day 31 "overdue"). Result: payment cycle 30 days vs 45 days current (15-day acceleration) = $3k cash flow freed (avg $36k outstanding → $33k). Margin per venue: system calculates (Crafty: 20 cases × $54 = $1.08k revenue, COGS [batch PALE-ALE-18 cost]). Batch cost: grain $80, hops $40, yeast $25, cans/labels $120 [228 cans total = $0.526 per can] = total batch cost ~$265 ÷ 228 cans = $1.16 per can × 6 = $6.96 per 6-pack. 20 cases (120 × 6-packs) = 120 × $6.96 = $835.20 COGS. Margin: $1.08k - $835 = $245 (22.7% margin). System visibility: (1) identify high-margin venues (Crafty 22.7%, Real Ale 25%, Brewery Mate 20%), (2) discount strategy (low-margin venues offered exclusive kegs = margin improvement). Territory mapping: system tracks (Crafty = inner Brisbane, Real Ale = 15km north, Brewery Mate = south suburb, 10km). Tim plans (avoid overlapping routes, bundle Crafty + nearby guest taps into Tuesday delivery, Real Ale standalone Wednesday). Route efficiency: +2 deliveries/month coordinated = fuel savings $200/month = $2.4k/year. **Value: standing orders eliminate phone calls (0 current vs 3 per roast = 8 hours/month freed), auto-invoice (no hand-writing, zero errors, net 30 enforced = $3k cash flow freed), signature proof (disputes resolved instantly, payment certainty), margin per venue (pricing strategy optimized, high-margin venues identified), delivery route optimization (fuel costs -$2.4k/year, territory planned).**

6. Excise Compliance & RSA Liability Logging — Batch Certification (ABV, Volume, Excise Tax), Quarterly Excise Return Export, RSA Staff Training Records, Service Refusal Log, ID Check Log, Incident Report Log, ATO Audit Trail, Health & Safety Checklist Automation

Current: batch ABV guessed (no calculation), excise liability unknown ($3–5k audit risk). RSA: zero logs (liability claim denied $35k). Food safety: checklist blank (fine $2.5k). New system: compliance dashboard. Excise certification: batch IPA #23 brewed 12/6, OG 1.042, FG 1.008. System calculates: ABV = (OG - FG) × 131 = (1.042 - 1.008) × 131 = 4.45% ABV (rounded 4.5%). Volume: Tank 4 (100L kegged, assume 95L usable = 95 litres produced). Excise tax: ATO rate $47.50/litre (Australia). Excise liability IPA #23 = 95L × 4.5% ABV × $47.50 = $202.69. System certifies batch: (1) batch ID BREW-20260612-IPA-023, (2) ABV 4.5%, (3) volume 95L, (4) excise tax $202.69, (5) brew date 12/6/26, (6) cert date 14/6/26 (when kegged, excise point-of-duty). Certificate generated: printable (batch label + tax mark). Quarterly excise return: system exports (all batches Q2: June–August). Batches: IPA #23 ($202.69), IPA #24 ($198.45), Stout #15 ($287.63), Pale #18 ($215.20), house brews × 12 = total $2.8k excise liability Q2. System exports: (1) batch list (ID, ABV, volume, tax), (2) total excise $2.8k, (3) ATO-ready format (simplified to accountant Melissa, Melissa files BAS). ATO audit (random 12-month sample): Melissa provides system export (all batch certs, ABV calculations, excise tax amounts, ATO verifies = zero non-compliance). Audit result: approved. Penalty avoidance: $3–5k. RSA compliance: tap room, bartender Jake. System logs: (1) training records (Jake RSA certified 2024, expires 2026, system reminder: expires 1/6/26 — retraining required [alert sent 1/6]). (2) Service refusal log. Tuesday 10:00pm: customer male, appears intoxicated (speech slurred, balance unsteady, order #5 beer). Jake refusal: enters system "customer #unknown, refused service, reason: intoxication evident, time 22:00, bartender Jake." System logs (refusal ID REF-20260611-001). (3) ID check log. Customer female, appears <25, orders beer. Jake checks ID (photo ID, DOB 1998, age 28, legal). System logs: "customer scan ID, DOB 1998, age 28, approved, time 19:45, bartender Jake." (4) Incident report: Friday evening, customer male (ID scan: DOB 1980, age 44) orders beer #4, system notes "within legal service, customer consent assumed." 45 mins later, customer involved in argument (no violence, verbal dispute with another patron). Manager Tim intervenes (separates customers, de-escalates). Tim logs incident: "altercation between customer 1 (male 44, 4 beers) and customer 2 (female 35), verbal only, no violence, resolved 22:30, customers asked to leave peacefully." System logs (incident ID INC-20260613-001, involved customers, bartender Jake present, manager Tim resolved). ATO / Health audit: system exports (training records, refusal logs, ID checks, incident logs). Auditor reviews (Jake trained RSA, zero over-service documented, refusals logged, liability low). Insurance: liability claim filed (old incident, but with current logs, insurer confidence high, claim approved $5k legal defence coverage [vs prior denial, now system logs justify coverage]). Food safety: tap room kitchen. System prompts (daily checklist, automation). Morning: 7:00am, manager Tim logs in. System reminder: "daily food safety checklist due." Checklist items: (1) fryer temp check (should be 190°C), (2) pretzel warmer temp (120°C), (3) fridge temp (2–4°C), (4) glassware washing cycle logged, (5) cleaning schedule (mop floor, sanitize bar top). Tim confirms: (1) fryer 191°C (OK), (2) pretzel 121°C (OK), (3) fridge 3°C (OK), (4) glasses run through commercial dishwasher cycle 8am (logged), (5) mop floor 7:30am, sanitize 8:00am (both logged). System timestamps all entries. Weekly summary: 7-day checklist completion rate 100% (vs prior blank checklist 0% June). Health inspector (new audit, August): system exports monthly checklist (June–August, all days logged, 95% daily completion [1 day missed, June 5 manager absent — system shows reason, vacation logged]). Inspector: "compliance excellent, no violations, follow-up audit 24 months [vs 30-day urgent recheck prior = trust rebuilt]." Fine avoidance: $2.5k (no re-inspection needed). **Value: excise certification (all batches documented, ATO audit risk zero, $3–5k penalty avoided, quarterly return auto-generated = 4 hours accountant labour freed), RSA logging (training records, refusal logs, ID checks, incident tracking = liability protection proven, insurance claims approved, $35k prior exposure now insurable), food safety automation (daily checklist logged, health inspector confidence = re-inspection delay 24 months = labour + fines avoided $2.5k).**

Australian Context: Craft Beer Culture, Excise Compliance, RSA, Food Safety, Wholesale Distribution

**Craft Beer Culture (AU)** — Australia's craft beer market = $2.1B annually, 250+ breweries (vs 50 in 2010). Brisbane = growing hub (80+ breweries within 100km). Consumer trend: "where's the brewery?" transparency (origin, brewing process, local pride). Craft venues thrive on reputation (word-of-mouth, Instagram-worthy bar, staff knowledge). System enables: batch transparency (QR code on tap = customer scans, sees brew date, ABV, batch story, brewery name). **Excise Compliance** — Australian Taxation Office (ATO) excise tax on alcohol = $47.50/litre (flat rate, uniform across beer styles, ABV factor integral). Breweries must: (1) calculate ABV per batch (formula: (OG - FG) × 131), (2) certify volume produced, (3) pay excise tax by 21st following month (quarterly via BAS). Non-compliance = audit risk, $3–5k penalty, plus interest. Mid-size breweries: estimated $2.5k–$3k quarterly excise liability. System eliminates guessing (batch certification automatic). **RSA Liability** — Responsible Service of Alcohol (RSA) = state-based training (mandatory for bar staff in QLD, NSW, VIC). RSA covers: (1) ID checks (serve only legal-age customers), (2) refusal service (intoxicated patrons), (3) safe-drinking advocacy. Liability: if over-served customer causes injury (e.g., car accident), bar liable for $35k+ damages + legal defence. Insurance claims: insurers demand proof of RSA training + service records (logs of refusals, ID checks). System logging = court-admissible evidence (timestamp, staff name, reason logged). **Food Safety** — tap room kitchens (if serving food) fall under state food safety regulations (QLD: Food Standards Australia New Zealand compliance). Requirements: (1) temperature monitoring (fryer 190°C, fridge 2–4°C), (2) cleaning schedules, (3) hand washing logs, (4) traceability (supplier records). Health inspectors conduct random audits (fines $2.5k+). System checklists automate logging (daily proof of compliance). **Wholesale Distribution** — bottle shop orders = net 30 terms typical (payment 30 days post-delivery). Breweries ship via (1) own van (Jack/Tim), (2) logistics partner (Uber Freight, StarTrack). System manifests auto-generated (venue, batch, quantity, expiry, carton IDs, delivery proof via signature app). Territory mapping: Brisbane has 60+ bottle shops, most within 50km; route optimization saves fuel (3 stops per route = $60 fuel vs 1 stop = $25 fuel, net savings $35/delivery × 12 deliveries/month = $420/month = $5k/year).

Six FAQs

How does batch certification prevent ATO audit risk and ensure excise compliance?

Current: ABV guessed, no batch certs, excise liability unknown ($3–5k audit risk). New system: batch brewed (OG/FG logged), system calculates ABV automatically (formula: (OG - FG) × 131). Volume logged (tank size - losses = usable litres). Excise tax auto-calculated (volume × ABV × $47.50 per litre). Certificate generated (batch ID, ABV, volume, tax). ATO audit: system exports all batches (12 months, all certs shown, zero gaps). Audit approved. **Penalty avoidance: $3–5k, compliance 100%.**

How does standing-order automation eliminate delivery chaos and enforce payment terms?

Current: 3 phone calls per roast, hand-written notes, 2 orders cancelled, no payment due date. New system: standing order recorded (venue Crafty, product Pale Ale, quantity 20 cases, net 30). Roast day: system auto-matches batch, generates manifest, invoice sent (net 30 due date encoded). Delivery: signature proof (digital, time-stamped). Payment: reminder day 29, notice day 31 (overdue). Result: 15-day payment acceleration (30 vs 45 days) = **$3k cash flow freed**.

How does fermentation monitoring prevent stuck yeast batches and off-flavour risk?

Current: gravity dipped 2–3 times, Post-It notes, no alerts. New system: gravity logged every 2–3 days (trajectory modelled). Batch IPA #23: OG 1.042, day 3 = 1.030 (28% attenuation), system models "FG 1.008 expected day 12." Day 7 = 1.012 (71% attenuation, on pace). Day 12 = 1.008 (complete). System alert: fermentation finished. If day 12 = 1.009 (stuck, not progressing), system flags "stuck fermentation, investigation required" = yeast pitched immediately, batch saved. **Stuck batch loss prevention: $300+ per batch.**

How does POS integration prevent tap inventory variance and revenue leakage?

Current: Jake hand-counts 165 pints/evening (±10% variance = $13.90 undercount × 20 evenings = $278/month variance = $3.3k/year leakage unreconciled). New system: flow meter per tap (or manual log). Tuesday evening: 165 pints poured logged in system, $1.39k revenue. Square reconciliation: POS total matches tap flow total (100% accuracy). Food: shoebox receipts scanned (OCR), system logs. Weekly: 1.09k pints/week logged, revenue $8.09k verified. **Leakage prevention: $4.8k/year**, accuracy 100%.

How does RSA logging protect the bar from over-service liability?

Current: zero logs, claim denied ($35k liability). New system: RSA training records logged (Jake trained 2024, expires 2026). ID check: customer scans ID (DOB logged, age confirmed). Refusal: customer appears intoxicated, Jake refuses, system logs "refusal ID REF-001, customer intoxicated, time 22:00." Incident: argument between customers, manager intervenes, logs details. ATO/insurance audit: system exports logs (training + refusals + ID checks + incidents). Insurer: "liability protection evident, claim approved." **Prior $35k exposure now insurable, new incidents protected.**

How does food safety automation prevent health-inspection fines and closure risk?

Current: checklist blank 3 months (May–July), fine $2.5k + 30-day recheck. New system: daily checklist (fryer temp, fridge temp, cleaning logged). Manager logs 7am each morning (95% completion rate). Health inspector (August): system exports monthly logs (June–August, all days, timestamps). Inspector: "compliance excellent, follow-up audit 24 months." **Penalty avoidance: $2.5k, inspection delay 24 months = labour + fine savings $2.5k.**

The Bottom Line

Mid-size craft brewery (Brisbane, 8-person, $800k/year): brew-day notes on Post-Its (no traceability, 5L yield loss $35/batch), fermentation monitoring (gravity dipped 2–3 times, stuck batches undetected = $300 loss), packaging (no QC, sediment transferred, cans hand-labelled with typos), tap room inventory (hand-counted, 10% variance = $4.8k annual leakage), wholesale chaos (3 phone calls per roast, 2 orders cancelled = $2.16k lost), excise compliance (zero batch certs, audit risk $3–5k), RSA liability (zero logs, claim denied $35k), food safety (blank checklist, fine $2.5k). Total friction: **$48.2k annually**. Custom brewery software ($35k build + $3k/year ops): brew-day traceability (batch timeline, gravity logged, hop schedule verified, yield calculated), fermentation monitoring (temperature + gravity tracking, stuck-fermentation alert, off-flavour risk flagged, cold-crash scheduled), canning automation (QC logged, batch barcode traced, expiry labelled, distributor manifest generated), tap POS (flow meter per tap, revenue 100% accurate, food integration, inventory forecasted 5 days advance), wholesale automation (standing orders, auto-invoice, net 30 enforced, signature proof, delivery tracking, $3k cash flow freed), excise compliance (batch certs auto-generated, quarterly export ATO-ready, $3–5k audit risk avoided), RSA logging (training records, refusal logs, ID checks, incident reports, liability protection proven), food safety (daily checklists auto-logged, health inspector confidence, $2.5k fine avoided). Payback: 16.2 months (brew traceability $2k value [yield loss prevention] + fermentation monitoring $2.5k [stuck batches] + canning QC $1.5k [error prevention] + tap POS accuracy $4.8k [leakage plugged] + wholesale $3k [cash flow] + excise compliance $4k [audit avoidance] + RSA protection $5k [liability reduction] + food safety $2.5k [fine avoidance] = $25.3k value year 1 vs $38k cost = break-even month 18). Multi-brewery scale (year 2): 2 breweries, same system, scale efficiencies (consolidated wholesale distributor tracking, dual-site tap inventory, dual-site RSA compliance) = cumulative two years **$86.7k value vs $38k cost, 280% ROI**. Start custom brewery software if: (1) hand-logging brew notes (traceability gap), (2) fermentation monitored <3 times (stuck-batch risk), (3) tap inventory guessed (POS variance >5%), (4) wholesale calls >2 per roast (distributor chaos), (5) zero batch excise certs (ATO audit risk), (6) RSA logs absent (liability exposure). Reach out: book a time to discuss your brewery size, fermentation scale, tap room volume, wholesale distributor network, and compliance baseline, or check platform pricing for a custom build quote.