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.
- Restaurant POS System
- Features
- Preparation and service
Preparation and service
Kitchen preparation and guest service happen at different times. Kitchen Lead records when each meal line was prepared. Service Lead records how many portions were actually served and when the order reached service. Those facts let the team resolve a partial order without calling every prepared portion a served portion.
OverviewServed Meal Lines×
Restaurant POS System · Preparation and service
New
Served Meal Lines
Meal lines
| Parent | Line number | Menu item | Portions | Prepared at | Served portions | |
|---|---|---|---|---|---|---|
| MO-42492 | 480 | MI-209 | 800 | 27 Oct | 880 | |
| MO-50758 | 810 | MI-498 | 830 | 20 Oct | 540 | |
| MO-75758 | 130 | MI-641 | 30 | 19 Oct | 950 | |
| MO-47882 | 680 | MI-849 | 120 | 14 Oct | 170 | |
| MO-67752 | 800 | MI-763 | 620 | 03 Oct | 490 |
6 of 6 records
MI-209Meal lines · ML-92181
ParentMO-42492
Line number480
Portions800
Prepared at27 Oct
Served portions880
What you can do
Follow actual portions
An approved kitchen release gives the kitchen the reviewed scope. Kitchen Lead checks the approved recipe revision and prepares against the meal lines. A preparation time shows when the kitchen work happened. The meal order moves through preparation and readiness as the team works. Its planned service time remains visible beside the actual service time, allowing the service team to spot a commitment that needs attention.
For a party whose meal is prepared in stages, the kitchen can complete some lines before the rest. The service team should record the portions actually delivered to guests on each line. An order may have a prepared dish held back or a dish that is never served. Later cancellation or correction must preserve those facts and account for waste separately. The order’s served state follows the actual service result.
How the work is organized
- Preparation record. Meal line preparation time and the approved recipe basis support the kitchen’s actual work.
- Service record. Served portions on each line and the order’s actual service time identify the guest outcome.
- Movement record. Ingredient movements show consumption and waste associated with the source meal line.
What to agree during setup
Agree when the kitchen marks a line prepared, who confirms served portions and how service time is entered. Define the procedure for a partly served order when another line is cancelled. The team should agree the units and timing for ingredient movements so that physical use and waste can be reconciled to prepared scope. Decide who resolves a discrepancy between a ready order and a missing guest service record.
The kitchen and service teams should rehearse an order that contains both a prepared line and an unprepared line. That is the most useful case for testing the handoff because the cancellation path must preserve the first line while changing only eligible remaining work.
Check the handoff on an actual case
Take an approved ticket for an accepted order with several meal lines. Kitchen Lead records preparation time on one line and the ingredient movements for that work. Service Lead then records fewer served portions than the line’s ordered portions and the actual service time. Compare the line’s ordered portions, preparation time and served portions before completing the order. If the unserved portion is cancelled, confirm that waste is accounted for separately and that the served history stays intact.
What your team sees
- Served Meal Lines — Lines with an actual served portion count for service review.
- Open Meal Orders — Accepted, preparing and ready orders grouped for the shift.
- Meal Order Board — A status view for the service lead and kitchen lead handoff.
Follow the work through
Use preparation and service for the full handoff. When the remaining scope changes, follow correction and reconciliation.
What it keeps track of
Data model- Meal orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Meal lines
- Individual menu item lines within a meal order.
- Kitchen tickets
- Kitchen tickets submitted for review and release against a meal order.
- Menu recipes
- Versioned recipe headers for products, with yield and approval state.
- Recipe ingredients
- Ingredient quantities required per recipe yield.
- Ingredient movements
- Signed inventory movements for ingredient consumption and waste.
Who uses it
Permissions- Kitchen Lead
- Records preparation and ingredient movements.
- Service Lead
- Records portions served and the actual service outcome.
- Kitchen Supervisor
- Has already decided the ticket release; Operations Reviewer examines a later correction.
Set up Restaurant POS System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.