Alibi — Logged & Verified
Saved
Quick Entry
Ready
COGS%
—
Food+NA net
Purchases
—
Ingredients + Products
End Inv
—
Value on hand
Δ vs Target
—
Target 30% COGS
This Month
—
Auto-saved
Net Sales (Food+NA)
$0
Net Sales (Total)
$0
Ingredients COGS
$0
Products COGS
$0
COGS% vs Food+NA Net
—
Exceptions
Stuff that will wreck your numbers
Quick Add Item
For “we just bought this” or “why is this here?”
Tip: You can refine units later per section (Dry vs Line) on the Counting tab.
Variance Heat Map
Fast anomaly scan: biggest movements by $ (begin + purchases − end)
Best-effort
Kitchen Map
Discovery Mode: build as you walk
Section
Pick a section to count
Adds to the end of the section path (sheet → shelf). Drag reorder comes later; v8 learns the order you add them.
Running Notes
Persistent during counting (stash / weird items / transfers)
Findings show up in Reports → Findings Queue
Invoices
Card-style entry • fast on mobile
Invoice Editor
Create or select an invoice
Recipes
Portion + Batch (batch auto-shows as inventory item)
Recipe Editor
Create or select a recipe
COGS Summary
Actual COGS (Begin + Purchases − End)
Begin (Ingredients)
$0
Purchases (Ingredients)
$0
End (Ingredients)
$0
COGS (Ingredients)
$0
COGS% vs Food+NA Net
—
Theoretical COGS (Toast PMIX) is next module; recipes are already here.
Findings Queue
From counting notes + quick saves
Unmatched Invoice Lines
Fix these so costs & categories stop being wrong
Advanced COGS Tools & Controls
Optional deeper controls (kept out of the main flow so the app stays calm during busy shifts).

COGS

Actual COGS
$0.00
Begin + Purchases − End
Theoretical COGS
$0.00
PMIX × Portion Recipes
Variance
$0.00
PMIX (Toast) — paste CSV

Manager Actions

    Monthly Summary

    Sales
    $0.00
    Actual COGS
    $0.00
    Theoretical COGS
    $0.00
    Variance
    $0.00

    Period

    Settings
    Single kitchen • Auto theme • Purple accent
    About this build

    v8 is the first build where the UI is card-style end-to-end (invoices, counting, recipes, reports).

    ZIP exports use JSZip. If you’re offline and JSZip can’t load, the app falls back to exporting JSON + CSV as separate downloads.

    Advanced
    Aliases, normalization, and power controls.
    Item setup (advanced)

    Item setup

    Case Study — Alibi — Logged & Verified

    Short skim first. Then the medium story. Deep dive if you want the mechanics.

    Skim (30–45 sec)

    • Broken frame: Inventory is treated as a static list.
    • Why it fails: Real inventory is messy: drift, shortcuts, lagging paperwork, mislabeled items.
    • Reframe: Inventory is a state machine with uncertain provenance.
    • System: Transition-first tracking + anomaly visibility + confidence (trust gradients).
    • Signal: I model reality instead of forcing fiction into a spreadsheet.

    Medium (2–3 min)

    Most inventory systems collapse the world into counts and pretend the record is truth. In real ops, the record is often a hypothesis.

    Alibi treats changes as events (transitions), not just totals. It’s designed to surface what’s unverified, what’s suspicious, and what’s known — so you can recover trust instead of losing it.

    This is failure-aware design applied to operational truth: represent the mess, don’t punish the user for it.

    Deep dive →
    Ask Althea (offline Q&A)