Fragile Excel
Yields, dual units, and last week’s WAC live in someone’s laptop. One version. No tablet. No audit trail.
For restaurant groups in the Philippines
StockPot digitizes a 30-year kitchen cost model: buy, receive, prep, sell, and reconcile in one closed loop — so owners see theoretical vs actual COGS, and the line can work on a tablet.
Create your kitchen today. Card billing is not live yet — you get full V1 access while we turn subscriptions on.
Most operators are stuck between a spreadsheet that cannot scale and an ERP that asks chefs to think like accountants.
Yields, dual units, and last week’s WAC live in someone’s laptop. One version. No tablet. No audit trail.
The restaurant adapts to the software. Staff avoid it. Food cost stays a monthly surprise.
The model already matches how kitchens buy bags, count bulbs, and explode recipes into raw use.
Purchasing, receiving, preparation, and sales stay synchronized so COGS has a period you can stand on.
Purchase orders follow par, not guesswork. Dual units keep “1 bag” honest against “35 bulbs.”
Dock-side receiving updates stock. Weighted average cost lands when the PO is received.
Sub-components nest. Recipes explode. Expected yield accounts for shrinkage before you count.
POS sales (CSV today) reverse-deduct through the recipe graph. Theoretical vs actual. Period-anchored COGS.
Raw materials, sub-components, and recipes share one catalog. Packaging factor and expected yield sit on the item — not in a sidebar note.
Pars back-calculate from what you actually plate. POs are a consequence of the menu, not a weekly argument.
Beginning + purchases − ending, anchored by a committed reconciliation. Variance is a drill-down, not a feeling.
No stock photography. The numbers in the hero are an illustration of the COGS formula, not a live customer dashboard.
Buy a bag. Count bulbs or grams. A packaging factor bridges the two so receiving and inventory stay in the same language.
Sauces and doughs nest. Cycle detection keeps the graph honest. Recipes reference both raw and prep.
Shared tablet, staff PIN, offline-capable PWA. The back office stays on a laptop; the line does not.
Independent restaurants and small groups in the Philippines. Not a global 250-branch pitch.
We will not invent restaurant counts or awards. Here is what the system already does.
Makeup / breakup thinking: raw → prep → plate → reverse deduct. Digitized, not reinvented.
Receiving updates WAC. Inventory value follows the goods, not last invoice price.
A committed reconciliation freezes ending inventory. That snapshot is the next period’s beginning.
Open the app, create an account, and run the setup wizard. Existing staff can log in to the same product.