Choose a restaurant order system by following one meal from the waiter’s entry to kitchen acceptance, preparation and collection. Define where each item should appear and who may change its status. Then rehearse corrections and missing tickets before relying on the system during a busy service.
Where should each order go?
Start your specification with the kitchen’s working stations. Write down which station prepares each menu item, whether another station needs visibility, and who assembles the final order. A drinks ticket and a food ticket may need separate destinations while still referring to the same customer order. Make that relationship explicit in your acceptance brief.
The Odoo examples below refer specifically to its version 18 documentation. Odoo 18 preparation displays can be assigned to a particular point of sale. Documentation. That gives you a concrete routing question for a demonstration: which till or ordering point supplies the display being shown? Ask the demonstrator to identify that connection rather than simply present an attractive kitchen screen.
The display configuration can restrict incoming items by POS product category. Documentation. Use this feature as the basis for a menu-to-station exercise. Select an ordinary meal, a drink, an extra side and a special item. Record the intended destination beside each. Include an item that crosses preparation responsibilities so the team has to explain how its parts come together.
Avoid using staff memory as the routing specification. Ask a chef and a front-of-house colleague to complete the exercise separately, compare their answers, then resolve differences. A software configuration should follow the agreed service model. Otherwise the demonstration can look convincing while different people hold incompatible expectations about what the kitchen has received.
What does “ready” mean during your service?
Give each status an observable meaning. Proposed definitions might be received, preparing, awaiting assembly and ready for collection. Decide whether ready refers to an individual dish, a station’s contribution or the entire order. Use the same definitions in the kitchen briefing, training notes and acceptance worksheet.
Preparation stages can have an alert timer specifying expected processing time. Documentation. Treat the timer as a configured prompt whose value your team must choose. Set a different proposed expectation for a simple drink and a meal requiring cooking if your service model calls for it. Record why each threshold was selected, who may alter it and when it will be reassessed.
Preparation order cards include associated tables and order numbers. Documentation. During a demonstration, ask the operator to trace a card back to the customer order using those identifiers. Rehearse two tables ordering similar dishes at nearly the same time. The purpose is to check that the handover uses a specific order identity rather than a shouted description of the food.
Odoo 18 moves a preparation card to the next stage when every item is crossed off. Documentation. This makes the meaning of crossing off especially important. Ask who performs that action and at what moment. If one colleague treats it as “started” and another treats it as “finished”, an otherwise valid sequence will communicate the wrong service state. Write the agreed action beside the stage name.
Recall moves an order back to its previous preparation stage. Documentation. Include a mistaken advance in your rehearsal. Have the operator explain why the correction was made and tell the colleague collecting the order what changed. Your proposed operating procedure should cover the human handover as well as the screen action, particularly when a runner has already responded to the earlier status.
Keep customer status useful
The customer order status screen distinguishes orders ready for pickup from those almost ready. Documentation. Decide what customers should be told at each public stage. A private kitchen distinction need not become another customer-facing label. Write a short explanation that staff can use consistently when someone asks whether an order has been forgotten or is waiting for a final item.
For table service, specify who checks the complete order before taking it out. For collection, specify how a customer identifies the right order. Rehearse the same dish appearing on two separate orders and an order whose items finish at different times. Record which status the customer sees while the final component is still outstanding.
Agree how to communicate a delay before building automatic messages around a stage change. Have the service manager approve the words and the trigger together. Your acceptance evidence should show the underlying order reference and the displayed message side by side, making it possible to assess whether they describe the same event.
Hardware choices need a separate check
A kitchen display and a printer introduce different physical handovers. Ask where each device will sit, who can see or hear it, and what staff will do when output is unavailable. Include the actual proposed model and connection in the equipment schedule rather than asking for “a compatible printer”.
Odoo 18 ePOS printer configuration requires the printer IP address. Documentation. Make the printer address part of the installation record, with an owner for changes. In your proposed test, send an identifiable sample ticket and have the receiving colleague confirm its destination. Preserve the sample reference and the configuration used so a later investigation can repeat the same check.
The documented Epson TM-H6000IV-DT direct support is limited to receipt printing. Documentation. This is a useful reminder to read model-specific qualifications. Do not extend a receipt-printing listing into a promise about every kitchen workflow. Require the supplier’s proposed equipment list to identify the intended printing role and the documentation supporting that particular use.
The Odoo 18 ePOS guide states that Epson printers connecting through Bluetooth are not compatible. Documentation. For the documented Epson setup, check the model and connection method before purchasing equipment for this version. A device name alone is an incomplete specification. Ask for the proposed network or IoT arrangement, installation responsibility and a practical demonstration using the intended connection. Record any unresolved dependency as an equipment decision rather than hiding it inside staff training.
A service rehearsal worksheet
Use this original worksheet as a proposed acceptance exercise. Fill in actual destinations and owners before running it; leave the observed result blank until someone performs the test. Keep failed rows in the record so the next rehearsal can focus on the exact correction.
| Rehearsal | Expected observation | Person confirming | Evidence to retain |
|---|---|---|---|
| Meal and drink on one order | Each item reaches its agreed station | Chef and bar lead | Order reference and both destinations |
| Two similar orders | Staff distinguish the correct table or collection reference | Runner | References and collection decision |
| One component unfinished | Public status follows the agreed readiness rule | Service manager | Stage and customer display |
| Accidental stage advance | Operator recalls and communicates the correction | Shift lead | Before and after state |
| Printer unavailable | Staff follow the written fallback and reconcile later | Duty manager | Exception and recovery record |
For a hypothetical café, suppose a sandwich and two drinks are entered together. The bar finishes first. Use that example once with table service and once with collection. Ask whether the drinks can leave independently, who owns the remaining sandwich, and what the customer is told. These are proposed service decisions to settle during the rehearsal.
Add an exception note for a cancelled item, an amended quantity and a corrected table reference. Ask the demonstrator to show the proposed handling of each without assuming the display and printer behave identically. Require an explicit result for each affected destination. A corrected front-of-house record should be checked against what the preparation team actually sees.
Finish with a short shift handover. Give a colleague who missed the demonstration the worksheet, the status definitions and the fallback instructions. Ask them to describe what they would do with an order awaiting one final item. Their questions are useful evidence for improving the operating guide before the first live service.
If ordering begins on your website, connect this brief to web development and the POS inventory integration guide. Keep stock reconciliation as its own linked decision. Bring your menu routes, device schedule and completed rehearsal brief to get started so the next discussion has a clear service workflow to assess.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.