The official Menulyn app listing describes connected ordering, waiter and kitchen workflows. For a restaurant, the important test is whether the information needed to prepare and serve an order reaches the right person at the right stage.
Make the order type obvious
Dine-in, pickup and delivery orders have different completion points. Prepare the required information for each type and identify who checks it. The team should not have to infer whether an order needs a table handover or collection arrangement from an unstructured note.
Test changes after submission
A customer may add an item or correct a choice after the initial order. Agree who can make that change and how the kitchen sees it. Walk through the amended order from both roles so that the preparation record and final customer record remain consistent.
Finish with a clear handover
Define what counts as ready and what counts as completed. A prepared pickup order may still be waiting for collection. Review those distinctions during training, and include a question or delayed order in the trial so staff know how to escalate it.
Make each handover explicit
An order can be accepted, prepared and collected at different times by different people. Agree the meaning of each operational state and who changes it. Use a sample that is amended after submission to check how the kitchen and service team stay aligned. If the customer asks about progress, staff should be able to find a clear answer from the record. The trial is successful when the next action is understandable from each role, including the point where an exception requires a manager rather than another automatic status change.
What to prepare
For waiters, kitchen teams and restaurant managers, preparation starts with order details, modifiers, service types and preparation handovers. Choose a small, representative sample that includes a normal case and an exception. Identify the person who can approve each part of that sample. If two colleagues interpret the same record differently, resolve the definition before treating it as an implementation requirement.
- Order-type requirements
Collect the relevant information and check it with the person who maintains it. Use an agreed example so the team can identify omissions before the work moves into a larger rollout.
- Authorised amendment process
Write down the expected result and who is responsible for it. Include any dependency on another person, device or service, so the requirement can be demonstrated rather than left as an assumption.
- Kitchen and service status meanings
Include this in the walkthrough with an ordinary user. Record what worked, what needed clarification and what requires a separate decision before the organisation relies on the workflow.
- Collection and exception handover
Assign an owner for the follow-up and keep the outcome with the project notes. Make the information available to the people responsible for operating and supporting the agreed process.
A practical walkthrough
Submit a pickup order with a modifier, amend it through the authorised role and follow it to collection. Ask the kitchen and service team to explain the same order from their respective views.
Run the example using the role that would perform the work in practice. Compare the result with the expected outcome and retain the relevant reference or review note. Then repeat the part affected by a correction or handover. A successful walkthrough should leave another authorised colleague able to understand the result without reconstructing a separate conversation.
Questions to discuss
Should kitchen staff use the same permissions as managers?
Use roles appropriate to the work. Test that kitchen staff can act on the orders they need without receiving unrelated administrative access.
What should we confirm before moving forward?
Confirm the scope for Menulyn ordering workflows, the required records and roles, and any setup or integration work. Keep demonstrated functionality separate from requested additions, and agree how unresolved questions will be answered before implementation.
Discuss your next step
Tell us about your team, current process and the outcome you need. We can help you identify the relevant demonstration or service scope.


