PayMyDineWaiter ordering
Create the order from the waiter or guest flow and attach the correct table, items, modifiers and notes.
Ordering, Kitchen & Menu
Move every order from entry to ready status with menu context attached.
Use 7 controls - waiter entry, KDS, preparation status, ready status, menu management, modifiers and sold-out items - from order capture to service handoff.
PayMyDineOrdering, Kitchen & Menu
KDS
Place incoming tickets in a focused KDS queue with item detail, timing and priority context.
Preparation status
Show received and preparing states so kitchen and management can see what is waiting and what is active.
Ready status
Publish ready status to service staff so the completed ticket has a clear next owner.
Ordering, kitchen & menu
The kitchen receives the complete preparation context, not a copied order summary.
Item detail, modifiers, ticket age and current state remain visible in the preparation queue during service.
See the 5-step operating flow
Ordering, kitchen & menu
Menu availability prevents the next avoidable ticket problem.
Menu, modifier and sold-out changes update the ordering context so unavailable or incorrectly configured items do not continue into preparation.
See the 5-step operating flowOrdering and kitchen scope
Seven controls connect order capture, preparation status and menu availability.
The purpose is to reduce missing context between service staff, the kitchen and the menu state guests or staff see.
workflow controls
Waiter ordering, KDS, preparation status, ready status, menu management, customisation and sold-out information are included.
critical handoffs
The order moves from service to preparation, then ready status moves back to the service team.
order contexts
Table, item or modifier detail and preparation status remain attached to the same work.
shared menu state
Menu changes and sold-out information should reach the people and channels that depend on them.
From order to ready handoff
How the kitchen receives complete work and returns a clear status.
The useful outcome is not another ticket screen. It is a readable preparation queue with a reliable handoff.
Capture the order
Record the table or channel, ordered items, modifiers and notes in the service workflow.
Present the preparation work
Show the kitchen the order detail and priority context needed to begin work without unrelated admin information.
Update preparation status
Move work through received and in-progress states so managers and service teams can understand what is happening.
Mark ready for service
Return a clear ready status to the role responsible for collection or table service.
Maintain menu availability
Update items, customisation and sold-out information so new orders reflect what the restaurant can serve.
What each role sees
The same order is presented differently to service, preparation and management.
Each role should see the detail required for its action without losing the table and order identity behind the work.
Service staff
Captures items, modifiers and notes, then follows preparation and ready status for the right table.
Kitchen and KDS
Works from a focused queue with item detail, notes, elapsed time and preparation status.
Manager
Sees workload, delayed tickets, ready handoffs and menu availability exceptions during service.
Menu administrator
Maintains menu items, customisation and sold-out state for the configured ordering channels.
Measure the workflow
Measure the handoffs, not only the final ticket time.
A restaurant should agree when each timer starts and stops before comparing performance.
Order-to-kitchen visibility
Measure the interval between order confirmation and the preparation view receiving the work.
Preparation duration
Track time from the agreed preparation start event to ready status by item, category or service period where available.
Ready-to-serve wait
Measure how long completed work waits before the service handoff is acknowledged.
Sold-out update delay
Measure the time between an availability decision and the updated menu state reaching the relevant channel.
Configuration and data requirements
Define the menu and status model before measuring kitchen performance.
Preparation reporting is only comparable when item structure, status events and channel ownership are consistent.
Menu items, categories, modifiers and preparation notesKDS views and the roles responsible for each queueReceived, in-progress and ready status definitionsService staff acknowledgement and service handoff rulesSold-out ownership and channel-update requirementsPOS or ordering integration source-of-truth decisions
Practical questions
What to clarify before choosing the scope.
The exact answer can depend on the restaurant setup, selected modules and connected systems.
Is the KDS the same as the manager dashboard?
No. The kitchen view is focused on preparation work, while management keeps the wider service and exception picture.
Can sold-out information update ordering?
Yes, where menu control and the relevant ordering channels are part of the configured setup.
Are modifiers and notes included?
The product scope includes menu customisation and order notes that need to travel with preparation work.
Can different order channels use the same kitchen flow?
They can contribute to one preparation picture while retaining their channel and table or takeaway context.
7 order, kitchen and menu controls
Give service staff and kitchen the same ticket status without giving them the same screen.
The ticket carries table, item, modifier and timing context into the kitchen while menu and sold-out changes prevent unavailable items from continuing through the flow.
Waiter orderingKDSPreparation statusReady statusMenu managementMenu customizationSold-out info
Map the real operation
Want to see Ordering, Kitchen & Menu in action?
We can show waiter ordering, KDS preparation, menu management, customization and ready-status handoff around your operation.