Product
One loop. From bag to COGS.
StockPot is not a pile of modules. It is a closed path: what you buy becomes what you prep, what you plate, and what you should have left.
Raw materials with dual units
Purchase unit and inventory unit are first-class. A packaging factor (1 bag = 35 bulbs) keeps receiving and counts in the same model. Expected yield accounts for trim before you argue about variance.
Sub-components nest
Sauces, doughs, and batches are their own recipes. They can reference other sub-components. The graph is a DAG — cycles are rejected, not papered over.
Recipes explode to raw use
A plated dish points at raw materials and preps. Par portions back-calculate what the storeroom should hold. This is the same graph reconciliation uses later.
Purchase to par, receive on the dock
POs follow the catalog. Receiving updates on-hand. When a PO is marked received, weighted average cost is computed — not last price, not a guess.
Sales in, theoretical out
Upload POS CSV sales. Reverse deduction walks the recipe graph and tells you what should have been used. Compare that to a physical count.
Commit the period
A committed reconciliation freezes ending inventory. That snapshot is the next period’s beginning. COGS is beginning + purchases − ending — anchored, not floated.
What we will not sell you yet
- Live POS or accounting connectors — CSV sales today.
- AI invoice scanning and predictive prep — roadmap, not current.
- A 24/7 global support center we do not operate.
See pricing for what you can start now.