Kitchen Batches
Cook in batches and track the plates.
Overview
A kitchen batch is a production record for a menu dish cooked ahead and sold by the plate. The kitchen requests ingredients, the storekeeper issues them from the warehouse (refused if stock is short), plates sold are tallied against the oldest issued batch of the branch, and the chef closes the batch with the plates wasted or left over. If the gap between expected and accounted plates is beyond the tolerance, a written explanation is needed. A batch cancelled before any plate is sold returns the issued stock.
A plate sold from a batch is booked at the batch’s cost per plate, so cost of sales follows the real ingredient cost. Recipes that are made to order deduct their ingredients on every sale instead.
When to use kitchen batches
- You cook dishes in bulk.
Step by step
Screenshot for this step has not been captured yet — run npm run docs:flow.
What you see on the screen
- The screen says: “Request ingredients, say how many plates you expect, then tally every plate sold against the pot.”
- The screen says: “Ingredients leave the warehouse when the storekeeper issues them. A plate sold on the POS counts against the oldest batch that is on sale.”
- Columns: BATCH, DISH, EXPECTED, SERVED, INGREDIENTS COST, STATUS.
- Actions on the screen: Request ingredients, Requested, Cooking / on sale, Closed.
Permissions
These permission keys control access (granted to roles in Administration → Roles & Permissions):
- pos.restaurant.manage
- pos.restaurant.read