Ingredients, quantities, sub-recipes, ingredient cost and food cost. The card follows the menu, not a separate binder; a stock or a dough is built once.
Explosion on sale
When the ticket closes, the recipe drops stock — solids and liquids, lot by lot (nearest use-by first). The consumption report rereads the service: theoretical, actual, variance.
Tablet count
Counts on the floor or in the store, including what is left in the bottle. The variance is measured when the line is counted; sales during the count are not erased.
Waste and dashboard
Breakage, expired, comped, prep error: every outbound has a reason. The dashboard reads revenue, real food cost, waste, stock alerts and cost drivers.
Inside the app
app.brigades.io/dashboard
Dashboard: revenue, real food cost, waste and stock alerts for the service.
app.brigades.io/recipes
Recipe cards: ingredient cost and food cost across the whole menu.
app.brigades.io/inventory
Stock: movements, waste and counts reviewed in the office.
app.brigades.io/sales/consumption
Consumption: theoretical, actual and variance per product.
Count: bottles and remains, variance at the time of counting.
What changes
Plate cost is computed on every sale, not once a quarter.
Stock drops on its own: no double entry between POS and Excel.
Inventory happens on a tablet, during or after service.
