Food Costing.

Vendor catalogs instantly turned into live menu costing and kitchen production sheets.

One shared ingredient catalog — 101 products — feeds both menus on this page: a nine-sandwich deli menu and fifteen house salad dressings. Every recipe is matched to a catalog product, the pack price is divided by the pack size, and each dish is costed to the cent. Change a pack price once, in a recipe or in the catalog, and every sandwich and dressing that uses it reprices instantly.

Close-up of the top half of a ciabatta sandwich, showing melted cheese, cured meats, greens and tomato spread
Sandwiches sold
–
demo period quantities
Revenue
–
menu price × qty sold
Food cost
–
–
Net profit
–
revenue − food cost
Best margin
–
lowest food cost %

The vendor raises a price. Now what?

This is the moment the catalog earns its keep. Pick a product, drag the increase, and watch which sandwiches take the hit and what it does to the bottom line — before the new price ever reaches the menu.

0%

How the costing works

Three steps, no new data entry. The catalog a restaurant already orders from becomes the costing engine for both menus.

1

Match the ingredient

Each ingredient on either menu is matched to a real catalog product — cheapest match when the catalog lists several. Where there's no exact match, the closest product stands in and is flagged as a proxy.

ingredient → catalog item #
2

Price the portion

The pack price is divided by what's actually in the pack to get a unit cost, then multiplied by the amount the recipe uses — 4 oz of protein on a sandwich, a quart of buttermilk in a dressing batch.

unit cost = pack price ÷ pack size
line cost = unit cost × quantity
3

Read the bottom line

Line costs add up to the dish's food cost. Against the menu price — or the 10 oz bottle price — that's the food cost %, and times the quantity sold, it's the profit the plate actually makes.

food cost % = food cost ÷ price