1. Restaurant POS System
  2. Features
  3. Meal orders
Feature · Meal orders

Meal orders

An accepted order is a promise about the menu, the portions and the time the team can serve them. Service Lead uses Meal orders to make that promise visible to the kitchen and the service team. Each order carries its operating organization, assigned owner and service location. The actual acceptance time stays with the planned service time, so a later review can distinguish what was planned from what happened.

OverviewMy Meal Orders
Restaurant POS System · Meal orders

My Meal Orders

Meal orders

New
Record numberSubjectStatusServe atCounterpartyOwner
MO-30546Draft mo-288Draft14 OctSL-110
MO-50014Accepted mo-213Accepted06 OctSL-110
MO-11379Preparing mo-115Preparing09 OctSL-110
MO-64452Ready mo-960Ready05 OctSL-120
MO-31345Served mo-415Served24 OctSL-140
6 of 6 records
Draft mo-288Meal orders · MO-30546
Draft
Serve at14 Oct
CounterpartySL-110
Example screen with sample data

What you can do

Accept a feasible order

The service team begins with a draft and adds the menu items and requested portions. Before acceptance, Service Lead checks that the products are active, that the allergen declarations are understood and that the requested service time has capacity. The order amount is calculated from the accepted scope. Acceptance records the actual time and a receipt for the guarded change. A screen that merely looks complete is not the team’s acceptance decision.

For example, a dining room order may ask for several portions at a busy service time. Service Lead checks the product selection and portion count before confirming the time. If the request changes while still in draft, the team can revise it before making the commitment. Once accepted, the current revision gives Kitchen Lead a clear starting point for the kitchen ticket.

How the work is organized

  • Order header. The number, subject, owner, location, planned service time, amount and status identify the commitment.
  • Meal lines. Each line records the menu item, portions, price and allergen declaration used for the meal.
  • Operation receipt. The acceptance action has a stable key, expected revision and recorded outcome for later checking.

What to agree during setup

Agree who can own an order, which service locations can accept orders and how the team checks capacity at the planned service time. Set the menu product and allergen review practice before accepting the first live order. Decide who handles an order that changes after the kitchen has begun work. An accepted order and its revision should be visible to the people who will prepare it.

The organization and service location need to reflect where the meal will be handled. For a multi-outlet operation, the service team should rehearse a case at each outlet before relying on a shared menu. The team should also agree how customer references are captured when a delivery channel sends an order into the operation.

Check the handoff on an actual case

Take a representative order with a stated service time and several meal lines. Have Service Lead check the items and allergens, accept it, then ask Kitchen Lead to open the same order. Confirm that the lines, amount, owner, service location and accepted time still describe the decision made. Repeat with a changed portion count before acceptance and verify that the accepted scope is the scope sent onward. A correction after acceptance follows a reviewed path with the earlier work retained.

What your team sees

  • Open Meal Orders — Orders in accepted, preparing or ready states, with the service time and owner visible.
  • My Meal Orders — The assigned service lead’s orders for the current shift and follow-up.
  • Meal Order Board — A status grouping for moving work from draft toward readiness.

Follow the work through

Follow order acceptance into kitchen release, then review the service handoff. The implementation plan helps the team rehearse its first operating cycle.

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.
Organizations
Operating organizations within the food and beverage group.
Team members
Staff members linked to an organization and platform identity.
Service locations
Dining rooms, outlets, venues and delivery destinations served by the operation.
Products
Sellable menu products and packaged goods.
Operation receipts
Durable receipts for guarded operations and their outcomes.

Who uses it

Permissions
Service Lead
Enters and accepts the order.
Kitchen Lead
Receives the accepted scope.
Operations Reviewer
Handles a later guarded correction.
Admin
Maintains the organization, staff and location references.

Set up Restaurant POS System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started