For restaurant groups in the Philippines

Food cost without the ERP.

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.

Two bad options. One kitchen-shaped way out.

Most operators are stuck between a spreadsheet that cannot scale and an ERP that asks chefs to think like accountants.

Fragile Excel

Yields, dual units, and last week’s WAC live in someone’s laptop. One version. No tablet. No audit trail.

Generic ERP

The restaurant adapts to the software. Staff avoid it. Food cost stays a monthly surprise.

StockPot

The model already matches how kitchens buy bags, count bulbs, and explode recipes into raw use.

The product is the loop — not a feature list.

Purchasing, receiving, preparation, and sales stay synchronized so COGS has a period you can stand on.

  1. Buy

    Purchase orders follow par, not guesswork. Dual units keep “1 bag” honest against “35 bulbs.”

  2. Receive

    Dock-side receiving updates stock. Weighted average cost lands when the PO is received.

  3. Prep & cook

    Sub-components nest. Recipes explode. Expected yield accounts for shrinkage before you count.

  4. Reconcile

    POS sales (CSV today) reverse-deduct through the recipe graph. Theoretical vs actual. Period-anchored COGS.

Three things owners actually need

Recipe & yield costing

Raw materials, sub-components, and recipes share one catalog. Packaging factor and expected yield sit on the item — not in a sidebar note.

Purchasing that follows par

Pars back-calculate from what you actually plate. POs are a consequence of the menu, not a weekly argument.

Theoretical vs actual COGS

Beginning + purchases − ending, anchored by a committed reconciliation. Variance is a drill-down, not a feeling.

Built the way kitchens already count

No stock photography. The numbers in the hero are an illustration of the COGS formula, not a live customer dashboard.

Dual units

Buy a bag. Count bulbs or grams. A packaging factor bridges the two so receiving and inventory stay in the same language.

Sub-components as a chain

Sauces and doughs nest. Cycle detection keeps the graph honest. Recipes reference both raw and prep.

Kitchen-first access

Shared tablet, staff PIN, offline-capable PWA. The back office stays on a laptop; the line does not.

Who it is for

Independent restaurants and small groups in the Philippines. Not a global 250-branch pitch.

  • Owners who want daily food cost, not a month-end surprise.
  • HQ chefs who govern recipes once and let locations execute.
  • Managers who receive and count on a shared device.

Trust the process, not a logo wall

We will not invent restaurant counts or awards. Here is what the system already does.

30-year cost model

Makeup / breakup thinking: raw → prep → plate → reverse deduct. Digitized, not reinvented.

Weighted average cost

Receiving updates WAC. Inventory value follows the goods, not last invoice price.

Period-anchored COGS

A committed reconciliation freezes ending inventory. That snapshot is the next period’s beginning.

Questions we actually get

Does it include a POS?
No. Sales come in as a POS CSV today. Live connectors are on the roadmap — we will not pretend they ship now.
Does it work offline?
The restaurant app is a PWA with Firestore’s native offline persistence. Marketing this site does not need a network to read; the kitchen app is built for a dropped connection on the dock.
Multi-location?
Yes: organization → brand → location. HQ governs master data; locations execute and count.
What does it cost?
Per store, not per seat. Create an account to start. Card billing is still being turned on — see pricing.

Set up your kitchen.

Open the app, create an account, and run the setup wizard. Existing staff can log in to the same product.