Yes, a guest can see which items are for here and which are takeaway before payment if the kiosk supports item-level fulfillment and shows those choices on its review screen. A kiosk that asks for one service mode for the entire order may not do that. Ask the vendor to demonstrate the exact mixed cart you need before you buy.
The distinction matters when one guest wants lunch at a table and a packaged item to take away. The screen must make both choices clear to the guest, and the order must carry them to the people preparing and handing over the food. A label on the review screen alone is not enough.
Build a cart with one item for here and one to go
Use a short, repeatable scenario rather than asking for a general tour of the kiosk. In this hypothetical example, a guest orders a $12 sandwich to eat at the restaurant and a $4 cookie to take away. The food total is $16 before any applicable tax or fees. These figures describe the cart only; they do not include fixed equipment costs, variable processing costs, or exception costs such as remakes.
Start at the screen a guest would see before selecting food. Add the sandwich and mark it for here. Add the cookie and mark it takeaway. Then go to the last review screen before payment. The guest should be able to identify the fulfillment choice for each item without relying on color alone or remembering an earlier selection.
Ask the vendor to show the actual item names, choices, and total together. A single heading such as “dine-in order” does not explain that the cookie should be packed to go. A note typed into a general comments field might communicate the request, but it is not the same as a clear item-level choice unless it stays attached to the right item throughout the workflow.
Next, change the cookie from takeaway to dine-in, then change it back. Remove and re-add it. Return from the review screen to the cart. The final review should still show one sandwich for here and one cookie to go, with the $16 food total. If changing a choice clears the cart or changes both items, the guest needs a visible explanation and an easy way to correct the order.
Run these checks in a demonstration or test environment. Stop before a real payment. Do not send a real guest message or dispatch a courier as part of practice.
Check item-level choices on the device
Fleksa’s restaurant kiosk page describes browsing, item customization, and order review. Those functions are useful starting points, but they do not by themselves answer whether a guest can assign different fulfillment modes to items in one cart. Ask for a demonstration of that specific workflow on the proposed setup.
Watch where the choice appears. Is it made when an item is added, edited in the cart, or selected once for the whole order? If the device asks “dine-in or takeaway” at the start, ask whether the guest can override that choice for an individual item later. Also ask whether a default applies and how the guest can see or change it.
Use the following worksheet to compare a demonstration against your requirements. The evidence column describes what the vendor should show; the acceptance column records a practical standard for a restaurant that needs mixed carts. Adjust the standard before comparing systems, not after seeing a sales demo.
| Check | Evidence to request | Owner acceptance criterion |
|---|---|---|
| Item choice | Demonstrate two items with different fulfillment choices in one cart. | Each choice can be set without changing the other item. |
| Prepayment review | Show the final review screen with both item names and their choices. | A guest can distinguish for-here and takeaway items before paying. |
| Edits | Change, remove, and re-add an item; return to review. | The final choices remain visible and can be corrected. |
| Staff and kitchen | Show the resulting test order at every preparation and handoff point. | Staff can identify which item needs takeaway packing. |
| Fallback | Walk through the proposed process if one mixed cart is unavailable. | Staff can explain it and complete the order without guessing. |
The last row is important even when the feature works. A guest may overlook a choice, a device may be unavailable, or staff may need to correct an order. Ask who can make a correction, where it appears, and whether the guest needs to repeat any part of the order.
Check usability with the people who will operate and support the kiosk. Can a guest read the labels from a normal standing position? Is there a clear way to go back? Ask how guests who cannot use the device can place the same request with staff. A mixed-cart feature is less useful if the only practical correction is to abandon the order.
Trace the labels to staff and kitchen
After the review screen, follow the test order through the proposed operating setup. Ask the vendor to show what the cashier or order manager sees, what the kitchen sees, and what the handoff person sees. Depending on your configuration, that may involve a restaurant POS system, a kitchen display, a printed ticket, or a combination.
For the hypothetical sandwich and cookie, the person packing the order needs to know that the cookie goes in takeaway packaging. If the kitchen sees only an order-level label while the kiosk shows item-level labels, ask how the difference is communicated. Do not assume that an item note, modifier, or icon will appear on every screen or ticket.
Request a sample of each output in the intended configuration. Check whether the fulfillment label sits beside the item it describes, whether it survives an edit, and whether it is readable during a busy service. If items route to different preparation stations, ask the vendor to demonstrate what each station receives. A useful label at one station cannot help a second station if it never reaches it.
Then walk through a correction. Suppose the guest changes the cookie to dine-in before payment. The review should show the revised choice, and the test order should carry that same choice to the relevant staff views. If the guest asks for a change after an order is placed, ask how staff record it and alert anyone who has already started preparation. The answer may involve a manual conversation; write that step into the procedure rather than assuming the software handles it.
Keep practice separate from a live service pilot. In simulation, use test outputs and avoid real payments, guest messages, and courier dispatches. If the demonstration meets your criteria, arrange any live pilot with the vendor and staff as a separate, controlled step. Agree on the scope, who handles exceptions, and how staff will record unclear orders before starting.
Choose a fallback and compare the quote
If the kiosk supports only one fulfillment mode per order, decide whether that limitation fits your service. One fallback is to ask the guest to place two separate orders: one for here and one takeaway. Before accepting that approach, check whether the guest must pay twice, whether staff can connect the handoffs, and how you will explain the process at the device.
Another fallback is a staffed order for mixed requests. Put a short instruction near the kiosk and train staff to enter or communicate the two item choices using the tools your restaurant actually has. Ask the vendor to demonstrate the staff workflow; do not assume a general order note will reach every preparation station.
Compare those fallbacks against your acceptance criteria. If mixed carts are an occasional convenience and staff can handle them without confusing the handoff, an order-level kiosk may still be suitable. If a single mixed cart with a clear prepayment review is essential, a system that requires two orders or a staff intervention does not meet that requirement.
Get a written quote for the proposed configuration, including hardware, software, installation, support, and payment compatibility. Ask which charges are fixed, which vary with transactions, and what extra work may arise from exceptions. Processing fees are only one part of operating cost. For a broader cost framework, use the kiosk break-even guide; compare quotes on the same scope rather than treating the lowest processing quote as the lowest total.
Next step: Take the worksheet to a Fleksa demonstration and ask the team to show your mixed cart from item selection through staff handoff. Compare the result and written quote with your requirements before choosing a restaurant management software setup.
Frequently asked questions
Is an order-level dine-in or takeaway choice enough?
Only if every item in that order can use the same mode. For a mixed cart, ask whether each item can have its own choice and whether the review screen shows it.
Can a general order note replace item-level fulfillment?
It can be a fallback if staff can reliably see and act on it. Ask where the note appears and how it stays clear when several items go to different preparation points.
What should I ask to see before buying?
Request the mixed cart on the proposed kiosk setup, its prepayment review, the corresponding staff and kitchen outputs, an edit, and the fallback for an order that needs correction.
