These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Recipe Management System
- Features
- Kitchen production
Kitchen production
Record prepared lines and actual ingredient use against the accepted order.
OverviewProduced Batch Lines×
Recipe Management System · Kitchen production
New
Produced Batch Lines
Production lines
| Parent | Line number | Menu item | Portions | Prepared at | Served portions | |
|---|---|---|---|---|---|---|
| PO-70454 | 700 | MI-519 | 900 | 13 Oct | 380 | |
| PO-24043 | 550 | MI-826 | 270 | 07 Oct | 390 | |
| PO-97565 | 40 | MI-680 | 210 | 09 Oct | 530 | |
| PO-60719 | 800 | MI-383 | 390 | 09 Oct | 510 | |
| PO-28606 | 70 | MI-579 | 40 | 15 Oct | 300 |
6 of 6 records
MI-519Production lines · PL-11314
ParentPO-70454
Line number700
Portions900
Prepared at13 Oct
Served portions380
What you can do
Prepare the accepted scope
The Kitchen Operator works from the lines of an accepted production order. Each line carries its menu item, portions, price and allergen declaration. The workflow freezes the approved menu recipe revision when the lines are released to the kitchen. The operator records when a line was prepared and how many portions were served. Those facts stay distinct: food can be prepared without yet being delivered or served.
A useful service rehearsal starts with an accepted order that has more than one menu item. The operator checks the approved recipe card for each item, the intended yield and ingredient quantities. When preparation begins, the operator records the prepared time on each performed line. If a portion is wasted, the signed stock consumption records the ingredient movement separately. The served portion count reflects what actually reached service.
How the work is organized
- Line identity. Keep each line number and parent order together so a preparation update reaches the correct service commitment.
- Frozen recipe. Use the approved revision selected for the released scope, even if a future revision is being prepared.
- Actual work. Record prepared time, served portions and signed ingredient consumption after the action occurs.
What to agree during setup
Agree who releases lines and how kitchen staff identify the approved recipe revision for the service. Define how portions are counted when a batch is partly prepared, partly served or wasted. Set a consistent unit for stock consumption and identify the source line in each movement. Rehearse a correction before service and a correction after service; they require different evidence and review.
The team should also agree when the order header is marked Preparing, Ready and Served. Those statuses summarize the work but do not replace line times or served portion counts. A header marked Ready can still need a final service confirmation. A batch ticket marked Approved can still need execution and verification before completion. Review those distinctions with both the kitchen and service team.
Check the handoff on an actual case
Choose an order in Open Production Orders. The Kitchen Operator prepares one line and records its actual time. Another line remains unprepared. The Order Coordinator can see that the order is in progress, while the supervisor can tell which scope is still safe to change. When the first line is served, its served portions are entered separately. A Fulfillment Event may show delivery of a menu item, but the event’s quantity and occurrence time must be reconciled with the local order rather than assumed from the header status.
If the venue cancels the unprepared line, preserve the performed line and its stock movement. If a prepared portion is wasted, record its signed consumption and keep it separate from the number served. This gives the Reconciliation Analyst a traceable explanation for a later discrepancy without changing the original order line into a fictional clean result.
What your team sees
- Produced Batch Lines — Inspect lines with a recorded preparation time and their served portions.
- Open Production Orders — Follow the parent order through preparation and service.
- Delivered Fulfillment Events — Compare external delivery events with local performed scope.
Follow the work through
Follow order to service and batch review when a ticket controls release.
What it keeps track of
Data model- Production orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Production lines
- Individual menu item lines within a meal order.
- Recipe cards
- Versioned recipe headers for products, with yield and approval state.
- Ingredient yields
- Ingredient quantities required per recipe yield.
- Stock consumptions
- Signed inventory movements for ingredient consumption and waste.
- Fulfillment events
- Allocation, picking, shipping, delivery and return events.
Who uses it
Permissions- Kitchen Operator
- Prepares and records actual work.
- Order Coordinator
- Follows the order commitment.
- Kitchen Supervisor
- Reviews changed or disputed scope.
- Reconciliation Analyst
- Checks event and consumption evidence.
Set up Recipe Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.