Inventory Management

Stock that knows when you 86'd it.

Recipe-level depletion, low-stock alerts, supplier orders — and yes, it tells every marketplace the second something runs out.

One source

Inventory that lives in the same place as your menu.

Most restaurant POS systems treat inventory as a side project. An Excel sheet that talks to the POS sometimes. A separate module with its own login. A nightly batch job that hopes nothing changed between 11pm and the morning prep.

dojofood does not work that way. Your catalog, your orders, and your stock all live in the same place. When the waiter app fires a burger ticket, the bun, the patty, the cheese, and the lettuce drop from inventory in the same write. When the kitchen marks an item out, every marketplace knows in the same second. There is no batch job. There is no module that wakes up late.

One source for the menu, the order, and the stock behind it. That's the whole point.

Recipe-level depletion

A burger is seven movements, not one.

A burger isn't a burger to your inventory. It's a bun, a patty, cheese, lettuce, tomato, sauce, and the foil it gets wrapped in for takeaway.

dojofood depletes at the recipe level. Sell one burger and the system writes seven small movements — one per ingredient — against your stock ledger. Sell a smash double and the patty count drops by two. Sub the cheese, and the swap is recorded in the same line.

For operators who run modifier-heavy menus — build-your-own bowls, pizzas, breakfast plates — this is the difference between a stock count that means something and a stock count that lies to you. The system follows the recipe; the recipe follows the menu; the menu lives in one catalog.

Auto-86

Close it in one channel. It closes in all of them.

86 an item from the kitchen — one tap on the KDS or one toggle on the back office — and the item goes unavailable on dine-in, takeaway, Yemeksepeti, Trendyol Go, Getir Yemek, Migros Yemek, Wolt, Bolt Food, Uber Eats, and your QR menu at the same time.

Same in reverse. When recipe-level depletion hits zero on the brioche bun, dojofood pulls every dish that needs a brioche bun off every channel automatically. The smash burger, the chicken sandwich, the breakfast bun — all marked unavailable until the bun is back in stock.

Wolt doesn't keep selling the dish you ran out of. Trendyol doesn't keep collecting orders the kitchen can't fire. The operator doesn't run between four tablets trying to remember which menu they need to mark. One toggle. Every channel. Same second.

Par levels

Par levels and low-stock alerts that fit your week.

You don't want an alert every time a bottle of olive oil dips. You want an alert when you're three burgers away from running out on the busiest night of the week.

Par levels are set per ingredient, per branch, with a re-order point that knows the rhythm of your operation. Brioche buns reorder at 60 on a Friday morning and 30 on a Tuesday afternoon. The low-stock alert fires to the manager on duty, not to a generic inbox no one reads.

For multi-branch operators, par levels are template-able — set the rhythm once for the brand, override per branch where reality differs.

Supplier side

Supplier records, purchase orders, receiving.

The supplier side of inventory is where most POS systems give up. dojofood treats it as part of the same ledger.

Supplier records

Contact, payment terms, lead time, minimum order, per-item price history.

Purchase orders

Generated from low-stock alerts or built manually, sent by email or downloaded as PDF, with the order's line items pre-filled from the catalog.

Receiving

Scan or tick the items that arrived, mark short or damaged quantities, and the stock count moves the same second. If the supplier's invoice price changed, recipe costs and per-channel margins update automatically downstream.

Reconciliation

What was ordered vs. what was received vs. what was invoiced, side by side, no spreadsheet required.
Waste tracking

Waste tracking that makes the next week cheaper.

Waste is a number every operator promises themselves they'll track and almost no one does, because the typing-it-into-Excel friction kills the habit. dojofood puts waste in front of the line cook.

A drop-down on the KDS, a button on the back office — log what got dropped, burned, comped, or aged out. The cost flows into the same ledger as the recipe and the sale. By the end of the week, your cost-of-goods-sold report shows you what walked out the door uneaten, by ingredient and by station.

That's the report the operator actually uses to fix Monday's order sheet.

Multi-branch

Multi-branch stock, transfers between branches.

For operators running more than one location, dojofood gives you the multi-branch view: stock levels across every branch on one screen, with per-branch par levels, alerts, and supplier orders.

When one branch runs short and another is sitting on a surplus, log a transfer — the stock moves between the two branches in the ledger, the receiving branch confirms arrival, and both par levels update accordingly. No phone calls, no "I think we have some at Karaköy", no double-counted inventory.

For franchise operators, the same view splits by entity — HQ sees the brand-wide picture, each franchisee sees their own books. Authorization keeps the line clean.

Cost of goods

Cost of goods, moving in real time.

Every recipe depletion writes a cost line. Every supplier price change rewrites every recipe that uses that ingredient. Every channel sale lands against the right margin once marketplace fees are accounted for.

The result is a cost-of-goods report that's not a month-end exercise. It's the number the operator sees at 11am the next morning, alongside last night's sales. What you sold, what it cost to make, what the marketplace took, what's left.

Said plainly

What we don't do (yet).

Live

  • Recipe depletion, auto-86 to every connected marketplace, par levels, low-stock alerts.
  • Supplier records, purchase orders, receiving, waste tracking.
  • Multi-branch transfers, cost-of-goods movement.

In flight

  • Automated supplier order placement (today you send the PO; the auto-send pilot is next quarter).
  • Barcode scanning on receiving for dry goods.
  • Weight-based depletion for bulk items.

On request

  • Integration with a supplier's order portal if your distributor exposes an API.
See the screen the kitchen uses

See the stock screen the kitchen actually uses.

20 minutes with our team. Bring your menu, a recipe you're proud of, and the marketplaces you sell on. We'll show you what one 86 toggle looks like across all of them. Real human, your language, under 2 hours if it ever breaks. Monthly billing. No hidden module fees on the inventory side — it's part of the same product.