Yes, guests may be able to find ingredient and allergen information before selecting a kiosk item, but the answer depends on the system, its setup and the menu information your restaurant maintains. Ask to see the actual guest journey before you buy. A label on an order review screen is too late for someone who needs to check an item first.
Start with the information your team can confidently maintain, then follow a guest from the menu category to the details and back. Check what happens when information is missing or a guest needs help. A kiosk can communicate menu information; it cannot guarantee an item is safe for a particular guest.
Decide which menu information you will maintain
Before looking at screens, identify the source and owner of each field. Your chef or another designated menu owner may approve ingredient details, while a manager handles changes in the ordering system. The important point is that someone is responsible for both accuracy and updates.
List the information you want guests to see: ingredients, relevant allergen information, available substitutions and any dietary descriptions your restaurant uses. Ask the vendor which fields can appear on the kiosk, where they appear and whether they can be maintained for individual variations. Do not assume a field in the back office is visible to guests.
Use a hypothetical example throughout the checks below. Your restaurant offers a grain bowl with a standard dressing and an optional sesame topping. The menu owner has approved the ingredient details for the bowl and dressing, but the topping information has not yet been confirmed. The expected result is that a guest can see the approved details before adding the bowl and is not shown an unsupported claim about the topping.
The table turns that example into a short worksheet. It separates what your team knows from what you need the kiosk to do. Bring a version with your own menu to a demonstration.
| Menu detail | Restaurant input | Expected guest result |
|---|---|---|
| Grain bowl | Approved ingredient list | List is available before the item is added |
| Standard dressing | Approved ingredient details | Guest can identify the dressing and find its details before deciding |
| Optional sesame topping | Information not yet confirmed | No unsupported safety or dietary claim; guest is directed to staff for help |
| Recipe change | Manager receives an approved update | Updated information appears wherever the guest sees the affected item |
Ask how an update reaches the kiosk and whether the same item can carry different information in another ordering channel. A shared restaurant management software setup may be relevant to your workflow, but confirm the actual fields and publishing steps for each channel. Also decide who checks the live menu after an approved change. A vendor cannot keep your recipes current for you.
Follow the guest from category to details and back
Run the demonstration as a guest would, not as someone who already knows the menu setup. Start at the home screen, open the category containing the grain bowl and look for a way to inspect it. The guest should be able to find the ingredient details before selecting an option that commits the item to the order.
Ask the vendor to show exactly what selection means in its interface. Opening an item detail screen may be different from adding it to a cart. If the only way to see ingredients is to add the item, the guest has to undo a choice before deciding whether it is suitable. That extra step is worth recording as a failed requirement if advance access matters to your restaurant.
Next, inspect the dressing and optional topping. Can the guest find details for each relevant choice without losing the main item? If the information is on a separate screen, can the guest return to the bowl without starting over? If a guest changes a choice, ask whether the displayed information changes with it. The expected result is a clear connection between the choice on screen and the information describing it.
Finally, return to the category and choose a different item. The expected result is that the guest can leave the bowl without adding it or accidentally keeping an unwanted selection. If a product uses icons or short labels, ask to see what each means in plain language. A symbol alone may not tell a guest whether it refers to an ingredient, a recipe choice or a broader dietary description.
Fleksa's restaurant kiosk page describes menu browsing, item customization and order review. For dietary details, ask to see the specific fields and navigation in the setup you would use; those general ordering steps do not establish where ingredient information appears.
Check missing information, accessibility and staff help
A blank field is a useful test. In the example, the sesame topping has not been confirmed. Ask what the guest sees: an empty space, a message that information is unavailable, or a prompt to speak with staff. The expected result is that missing information is not presented as proof that an ingredient or allergen is absent.
Agree on a staff path before the kiosk goes live. A guest who cannot find an answer needs to know whom to ask. The team member at the counter should know where to find the current approved menu information and when to involve the menu owner or manager. If the answer remains uncertain, staff should say so rather than guess. A guest can then decide whether to proceed, choose something else or leave the order.
Ask the vendor how guests can request assistance from the kiosk and whether that request changes anything on the order. If there is no suitable on-screen option, plan a visible counter handoff and train staff to notice guests who may need help. Do not depend on a free-text note reaching the right person unless you have confirmed how the complete workflow handles it.
Check accessibility at the kiosk location, not just on a vendor's laptop. Can a guest read the details from a comfortable position? Are controls easy to distinguish and operate? Ask about text size, contrast, screen-reader support, language options and any alternate ordering method your guests need. Have staff try the path without coaching, and invite feedback from people with relevant access needs where practical. A readable list does not help if a guest cannot reach it or return to the menu.
Keep practice separate from service. In a simulated check, use a vendor demo or a clearly isolated practice environment and stop before any real payment, guest message or courier dispatch. Ask the vendor how the environment prevents those actions. For a live service pilot, use your normal staffed procedures and monitor the handoff; real orders and payments should occur only as part of ordinary service, not as pretend test actions.
Set acceptance criteria before choosing a kiosk
Turn the demonstration into a short pass, fail or follow-up record. Write down the exact screen and action for each result. A vendor may offer a workaround, but your team should decide whether the extra work is realistic during a rush.
- Before selection: Can a guest open approved ingredient and allergen information before adding the item? Can they return to browsing without an unwanted item in the order?
- Choices: Can the guest connect information to the standard item and relevant options? If an option changes, is the information still clear?
- Unknowns: When a field is missing, is the absence of information clear? Is there a practical route to staff?
- Maintenance: Can an authorized employee update the information and check the guest-facing result? What happens across other ordering channels?
- Access and fallback: Can guests read and operate the path, and can staff take the order another way when they cannot?
For the grain bowl, a reasonable decision follows the requirements. If guests can inspect the approved bowl and dressing details before adding the item, but the unconfirmed topping appears to have a reassuring dietary label, do not accept that configuration as ready. Correct the menu information or remove the unsupported label, then repeat the check. If the system cannot make the distinction clear, ask for a workable alternative and consider another setup.
Dietary filters can help narrow choices, but a filtered result should not be treated as a medical guarantee. Ingredients, substitutions and preparation practices can change, and a guest's needs may require a conversation with staff. Ask your menu owner how the restaurant will handle those questions and keep its information current.
Also check how the kiosk fits your order workflow. Ask whether item choices and relevant notes reach the restaurant POS system in a form staff can understand, and how staff handle a question before an order is sent. Include hardware, software, installation and support in a written quote. The kiosk break-even guide can help you frame the wider cost decision without treating a dietary-information check as proof of savings.
Next step: Bring a real menu item, an option with different ingredients and one deliberately unconfirmed field to a Fleksa demonstration. Compare your requirements with the displayed workflow and confirm current availability before choosing a setup.
Frequently asked questions
Should guests have to add an item to see its ingredients?
If checking before selection is your requirement, no. Ask the vendor to show ingredient details before an item is added and to demonstrate how the guest returns to browsing.
Who should update kiosk allergen information?
Assign a menu owner to approve the information and an authorized employee to publish changes. Check the guest-facing result after updates and make sure staff know where to find the current details.
Can a kiosk tell a guest an item is safe for them?
No kiosk display can guarantee that. It can present the restaurant's maintained information and direct guests to staff when they need more detail or an answer is uncertain.
