Kitchen control: order, usage and sales

Loading… · ·

As of the — stock count, — items need ordering today and — more soon. Of the — ingredients checked against the recipes, — were used more than the dispatched items explain. Sales on — were about —.

1 · Order today

—

items, plus — to order soon

2 · Used more than expected

—

of — ingredients checked; — used less

3 · Approx sales, —

—

— vs the — a day of the 7 logged days before

Approx sales, this month's tab

—

est. platform payout —

Outcome 1

What to order, and how much

Grouped by type, most urgent first in each group. Daily use is the average fall in the chef's count over the last 7 days, leaving out days a delivery came in. Predicted use is that rate over the days an order should cover: — for the fruits tab, — for ingredients and — for packaging. Order is predicted use minus what is in stock, or enough to reach twice your amber level if that is more.

Item In stock Unit Daily use Days left Call Predicted use Order Why

Stock history for one item

The chef's daily count, with your amber and red levels. A ring marks a day the count went up, which is a delivery.

—

Outcome 2

Is anything being used more than expected?

Expected use is what was dispatched times the quantity of each ingredient in "Real Cost of Each Bowl", including the fruit grams inside its cost formulas. Used is how much the counted stock fell on the same days, over the last — days; days with a delivery are left out on both sides. A gap of more than — is called out, or — where fruit counted in pieces is converted with an assumed weight per piece. More than expected points to heavy portions, wastage, use in drinks that have no recipe row, or a recipe that understates.

Used vs expected, % difference (bars stop at 150%)

—

The numbers behind it

Ingredient Expected Used Unit Difference Reading Days compared Conversion

Outcome 3

Approx sales per day

Items dispatched times the selling price in "Real Cost of Each Bowl", taking the average of the Swiggy and Zomato price because the dispatch sheet does not say which platform an order came from. This covers — of the — items dispatched this month; — items have no price row in the sheet and add nothing. The dashed line is the daily average.

Approx sales per day

—

By menu item, month to date

Menu item Dispatched Price used Approx sales Share Price from

Stock entries worth a second look

Counts that look like a unit or typing change, and items that have not been counted for two days or more.

Item Stock tab Date What to check
How these numbers are worked out, and what is assumed
  • Use is read from the chef's counts: when an item's count falls from one day to the next, the fall is that day's use. When it rises, a delivery came in, and that day's use cannot be seen, so the day is left out.
  • Order today means under 1 day of stock at the recent rate of use, or at or below the red level on the Inventory Sheet's Dashboard tab. Order soon is under 3 days, or at or below amber. An item at zero with no use or delivery for 14 days is treated as not stocked and left off the order list.
  • The groups in the order list are made from item names (for example anything with "sticker" goes to Stickers).
  • Fruit is counted in pieces or packets but the recipes are in grams, so each has an assumed weight per piece or packet, shown in the Conversion column. The edible share comes from the Mapping Prices tab (price per gram against price per kg). Wrong weights shift those rows, so treat them as a prompt to check.
  • Chocolate bars, nibs, lavash, cocoa and microgreens are in the recipes but their stock units cannot be converted yet, so they are not checked.
  • Minis and beverages use their own rows in the recipe sheet; Mini (Fruit) is read as the mini Fruit bowl. Cucumber in the buttermilk and mint in the detox water are entered as rupees there, not grams, so that use still shows up as extra.
  • Sales use the current selling prices, averaged across Swiggy and Zomato; where an item is listed on one only, that price is used. Payout uses the platform payout columns the same way. Discounts, ads and Ownly orders are not modelled.
  • A count is taken to be the closing stock for its date, so it is paired with that date's dispatches.
  • Dispatches come from the current month's tab in Daily Orders Tracking (any tab whose name starts with the month, such as "Nov" or "December"), picked automatically. The Cook expense tab is not included.