Yes, staff can distinguish an item-specific preparation request from an order-wide note if the POS presents the instruction beside the correct dish and makes its scope clear wherever staff need to read it. Do not assume that happens just because the note looks right on the order-entry screen. Check what happens after an edit and what the preparation station actually sees.
Use the same sample order with each vendor. Have a server and a kitchen lead judge it together: the server knows what was entered, while the cook can say whether the instruction is clear enough to act on. The result should show both what the software displays and what your team must do when a request is ambiguous.
Build an order that makes note placement visible
Use this hypothetical practice order throughout the evaluation: one grilled chicken sandwich and one vegetable wrap. The guest asks for the sandwich to be cut in half. The wrap has no special instruction. The question is whether staff can see that “cut in half” belongs to the sandwich, not the wrap or the whole order.
Ask the vendor to enter the request as a free-text item note, rather than choosing a preset modifier. A modifier may be useful for common requests, but it does not answer whether staff can place and read an open note. Ask whether the system also has an order-wide note field and how its display differs.
Run the exercise in a demo, training environment, or other controlled setup. Confirm in advance that the simulated order cannot take a real payment, send a guest message, or dispatch a courier. If kitchen printers or screens are connected, tell staff that the ticket is practice and must not be prepared. The vendor can show the relevant output without sending a real order into service.
Start with the entry screen. Can the server tell which dish is selected before typing? After saving, can the server see the note beside the sandwich without reopening a separate field? Have the kitchen lead read the resulting ticket or screen without being told the answer. Ask which dish needs cutting and whether the wrap needs any action.
Then enter a separate order-wide instruction, such as “pack items together,” if the demonstration supports it. The distinction should be apparent to a person reading the order: the preparation instruction belongs to one dish, while the packing instruction applies to the order. If both appear in the same undifferentiated block, ask how staff are expected to determine their scope.
Change the quantity and seat, then check again
An order can be correct when first entered and confusing after a guest changes it. Keep the original practice order, then ask the vendor to demonstrate each edit separately. Return to the original state between checks so you know which change caused each result.
- Increase the sandwich quantity. Change it from one sandwich to two. Does the note apply to both, only one, or is its scope unclear? Ask how staff would specify that only one should be cut.
- Reduce the quantity. Return the sandwich quantity to one. Check that the remaining dish and its instruction still match the guest's request.
- Change the seat. If your restaurant uses seat assignments, move the sandwich to another seat. Check the note and seat on both the entry view and the kitchen output.
- Reopen the order. After saving the edit, ask another staff member to open the practice order and explain what must be prepared. This checks what a handoff looks like, not just what the original server remembers.
Record the steps the vendor took, including whether a quantity change edited an existing line or created a separate line. Those paths may produce different results. Ask for the demonstrated behavior in writing, along with any configuration or device needed to reproduce it. Keep a screenshot or a clearly marked practice ticket if the vendor permits it.
Do not treat an explanation like “the kitchen should know” as evidence that a note is attached to the intended item. If the system cannot clearly represent one cut sandwich and one uncut sandwich on a quantity-two line, ask whether staff can enter separate item lines and whether the kitchen display keeps them distinct. A practical workaround can be acceptable, but only if staff can perform it reliably during service.
Compare what the server and kitchen actually see
For the sample order, compare the entry view with every output your team would rely on: a kitchen screen, printed ticket, or both. Also ask which preparation station receives each dish under the proposed setup. A note visible to the server is not enough if the person preparing the sandwich cannot see it.
The table below is a worksheet for recording the same scenario across vendors. The example observations describe a possible demonstration, not a claim about any product. Replace them with what your team observes.
| Check | Example observation | Decision implication |
|---|---|---|
| Order entry | “Cut in half” appears under the sandwich; the wrap has no note. | The server can review the intended placement before saving. |
| Quantity edit | Two sandwiches appear on one line, but the note's scope is unclear. | Ask to demonstrate separate lines or another clear way to request one cut sandwich. |
| Seat change | The sandwich and its note appear together under the new seat. | Check that the kitchen output reflects the same assignment. |
| Preparation output | The sandwich station sees the item but not its note. | Do not accept the workflow until the vendor demonstrates a reliable correction or your team accepts a documented workaround. |
The last row is a decision-changing exception. Even a clean order-entry screen cannot make up for an instruction missing at the station where it is needed. Ask whether the output can be configured differently, then repeat the same practice scenario. If the instruction becomes visible only on a ticket at another station, decide who will relay it and how that handoff will be confirmed.
Include readability in the comparison. Is the note close enough to the item to be understood at a glance? Can a cook distinguish it from an order-wide note? Does it remain legible when the order has several items? Ask the kitchen lead to interpret the output before the server explains it. If they reach different conclusions, record the mismatch rather than assuming training alone will fix it.
Set a note checklist and escalation rule
Before choosing a system, agree on a short pass list with the people who will enter and prepare orders. For each candidate, check that:
- The server can select the intended item and enter an open preparation note.
- The saved order shows which item owns the note and distinguishes it from an order-wide instruction.
- Quantity and seat edits produce an understandable result, or there is a demonstrated procedure for handling them.
- The intended preparation station receives a readable instruction alongside the correct item.
- A second staff member can interpret the order without relying on the original server's memory.
- The vendor documents the setup and any steps needed to reproduce the demonstrated result.
For an unclear request, use a manual escalation instead of guessing. The server should pause, clarify the guest's intent, and update the order using the agreed entry method. If the order has already reached the kitchen, the server should also tell the kitchen lead directly and confirm that the correction was understood. The lead can then tell the relevant station. If the request cannot be represented clearly, use your restaurant's approved manual handoff and record the limitation for the vendor.
For example, “no sauce” on a two-item order could mean no sauce on one dish or on both. Do not turn that into an order-wide note based on an assumption. Ask which dish is affected and whether the guest wants sauce omitted entirely. For an allergy or another safety-sensitive request, follow your restaurant's established escalation procedure rather than relying on a free-text note alone.
Compare the evidence, not just the number of steps. A system that needs an extra separate item line may still meet your needs if the kitchen sees an unambiguous instruction and staff can use the method consistently. A shorter entry path may be a poor fit if it leaves the note's scope uncertain. Ask each vendor about printer or screen configuration, seat handling, and the exact workflow for changes; make those answers part of your requirements before signing.
For broader questions about how the POS fits daily operations, review Fleksa's POS questions and consider how it fits your restaurant management software. Then request a demo of the restaurant POS system using the sample order. Ask the vendor to document the note placement, edit behavior, station output, and any workaround your team would need.
Frequently asked questions
What is the difference between an item note and an order note?
An item note describes an instruction for a particular dish. An order note applies to the order more broadly. Check that both the entry screen and preparation output make that difference clear to staff.
Should one note apply to every item in a quantity-two line?
That depends on the guest's request and the system's behavior. Ask the vendor to show how to represent one modified item and one unmodified item clearly, including whether separate lines are needed.
Is a successful practice order enough to launch?
It is useful evidence, but it covers only the scenario and setup demonstrated. Before a live service pilot, agree on staff responsibilities and escalation steps. A simulated check must not trigger a real payment, guest message, or courier dispatch.
