After moving a restaurant kiosk, verify its location in two places: the device’s assigned location in the management system and the destination reached by an order. Then compare the live menu and hours with the new site’s approved settings. A kiosk that displays the right restaurant name is not enough; it must also send the right items to the right fulfillment point.
Keep the kiosk out of guest service until an owner or designated manager has reviewed the evidence. Start with a simulation that cannot charge a card, message a guest, or dispatch a courier. If a live service pilot is needed afterward, run it separately under the restaurant’s normal operating controls.
1. Inventory the kiosk before and after the move
Record the device’s identity before disconnecting it. Use the serial number or another identifier that distinguishes it from every other kiosk. Note its old location assignment, physical position, network connection, payment device, and the printer or kitchen display that normally receives its orders.
Also record the intended destination: the new address, the name used for that location in the software, the physical spot for the kiosk, and the kitchen or counter that should fulfill its orders. Location names can be similar, so pair the name with an address or internal location ID.
Ask the vendor who is responsible for changing the device assignment and whether a reassignment affects payment configuration, receipts, reporting, or connected equipment. Request a record showing the device identifier and its new location assignment. If access is restricted, arrange for an authorized person to show the setting to the manager responsible for sign-off.
Before moving anything, agree on a fallback. Staff might take orders at a staffed register while the kiosk is unavailable. Confirm which team owns that process and how guests will be directed there. If the old location remains open, make sure its remaining devices are identified separately so a change to the moved unit does not accidentally affect them.
For context, compare the kiosk assignment with the location records used in your restaurant management software. Do not assume that a matching display name proves the back-end assignment is correct.
2. Verify the destination menu, hours, and network
At the new site, compare the kiosk screen against an approved menu for that specific location. Check item names, prices, available options, modifiers, and any items that should not be sold there. Review at least one item with a required choice, such as a sandwich with a bread selection, and one with an optional add-on.
Then check the schedule. The relevant question is not simply whether the kiosk is on during business hours. Ask which time zone and location schedule govern ordering, what guests see outside those hours, and how a temporary closure or menu change is applied. Have the vendor show where those settings are controlled and how the team can confirm an update has reached the device.
Check the destination network with the person responsible for it. Confirm that the kiosk connects to the intended network and that the order path works through that connection. A connected indicator alone does not prove an order can reach the kitchen. Ask what the device displays if connectivity fails, what happens to an order in progress, and how staff should switch to the fallback. Do not assume offline ordering or payment is available.
Review the physical setup as well. The screen should be reachable and readable from its intended position, with space for guests to move around it. Confirm that power and network cables are secured and that the payment device, if used, is the one assigned to this kiosk. Ask the vendor to confirm compatibility and configuration for the actual equipment at the new site.
3. Trace a simulated order to fulfillment
The strongest check follows one identifiable order from the kiosk screen through the receiving system. Ask the vendor to provide a simulation or test mode that prevents a real card charge, guest message, and courier dispatch. Agree in advance where the test will appear and who will clear any test record afterward.
Hypothetical example: A kiosk moves from the Oak Street dining room to the Pine Avenue counter. Pine Avenue sells a turkey sandwich with a required bread choice and does not sell Oak Street’s soup. The owner wants Pine Avenue staff—not Oak Street staff—to receive kiosk orders.
In the simulation, select the turkey sandwich, choose rye, and review the order before submitting it. Confirm that the soup is absent from the Pine Avenue menu. Record the test order identifier and follow it to the receiving screen or printer. Pine Avenue’s designated fulfillment point should show the sandwich and rye choice; Oak Street’s fulfillment point should not receive it.
The worksheet below turns that example into a decision. The evidence column identifies what the vendor or site team should show, while the acceptance column states what the owner must see before opening the kiosk to guests.
| Check | Evidence to review | Owner’s acceptance criterion |
|---|---|---|
| Device assignment | Device ID paired with Pine Avenue’s location record | The moved device is assigned to Pine Avenue, not Oak Street. |
| Menu and schedule | Approved Pine Avenue menu and hours beside kiosk screens and settings | Turkey and its rye choice are correct; Oak Street soup is absent; hours match the approved schedule. |
| Order routing | Test order ID and receiving screen or printout | Pine Avenue receives the sandwich with rye; Oak Street does not receive the test. |
| Safe simulation | Vendor explanation of test-mode controls and test record | No real payment, guest message, or courier dispatch occurs. |
| Failure response | Demonstration of the agreed connection-failure procedure | Staff can identify the problem and direct guests to the staffed register. |
For your own move, replace these sample criteria with the destination’s actual menu, equipment, and receiving point. Include a check for every fulfillment path the kiosk is expected to use. If some orders should go to a different station, trace a separate simulated order there rather than assuming all items follow the same route.
Ask how the kiosk connects to the restaurant POS system and how the team can distinguish a test record from a guest order. If the vendor cannot provide a safe simulation for a particular step, leave that step open and agree on an alternative verification method. Do not run a practice scenario that triggers a real payment, message, or dispatch.
4. Sign off, clean up the old site, and monitor service
Give one person authority to accept the move. Record the device ID, new location, date, people present, evidence reviewed, and result of each check. For a failure, note the owner of the correction and the time for a retest. A photo of a screen or a saved test record can help, provided it does not expose unnecessary guest or payment information.
Use a clear decision: accept when every required criterion passes; hold when an essential check is missing or fails. For example, the Pine Avenue kiosk stays out of guest service if its menu is correct but the test order reaches Oak Street. A successful screen review cannot substitute for a failed routing check.
At the former location, remove or update signs that direct guests to the moved kiosk. Check floor markers and any staff instructions that still describe its old position. If another kiosk remains there, make sure the updated signs point to the correct device. Confirm that the moved kiosk’s old assignment has been removed or changed as intended, without removing another device by mistake.
If the simulated checks pass, decide whether a short live service pilot is appropriate. This is real service, not a simulation: assign a manager to watch the first orders, confirm they reach the intended fulfillment point, and keep the staffed fallback ready. Follow the restaurant’s normal payment and guest-service procedures. Stop using the kiosk if an order routes incorrectly or staff cannot resolve a problem promptly; document the issue and retest the affected path before reopening it.
Keep the completed worksheet where the site manager can find it. Revisit the relevant checks after a location reassignment, major menu change, network change, or receiving-equipment change. For a broader purchase decision, the self-order kiosk break-even guide can help frame installed costs alongside operational capacity.
Next step: Adapt the worksheet to your destination and compare its requirements with Fleksa’s restaurant kiosk. Ask Fleksa to confirm the location assignment, safe test workflow, and order-routing evidence for your equipment before buying.
Frequently asked questions
Is the correct restaurant name on the screen enough to approve a move?
No. Match the device identifier to the destination’s location record, then trace a simulated order to the intended fulfillment point. Also verify the destination menu and hours.
What should staff do if a simulated order reaches the old kitchen?
Keep the kiosk out of guest service, record the test identifier and receiving location, and ask the responsible vendor or administrator to correct the routing. Repeat the affected checks before sign-off.
Can we test the move without charging a card?
Ask for a simulation that prevents a real payment, guest message, and courier dispatch. Confirm those controls before starting. A later live service pilot is a separate decision using normal service procedures.
