Before choosing a POS, ask two questions: Can its traffic be separated from guest Wi-Fi, and who will keep that separation working? A vendor may supply the POS while your internet provider, landlord, or local technician controls the network. Unless those boundaries are clear, a busy service can turn into a chain of calls with nobody able to make the necessary change.
Start with a network ownership and access worksheet. List the devices, the people who can change the network, and what each provider must demonstrate. Get agreement on the result you need before signing a contract or changing a working setup.
Define the network decision before a demo
Picture a server taking an order on a handheld while guests connect to Wi-Fi and a kitchen printer receives tickets. The owner needs the ordering devices to reach the services they require without giving guest devices the same access. If something stops working, staff need to know whom to call and what they can safely do while waiting.
That decision covers more than the POS screen. Make an inventory of terminals, handhelds, payment devices, printers, kitchen displays, kiosks, routers, access points, and any guest network equipment. Note who owns each item and who administers it. A device may be restaurant property while a provider holds the administrator account.
Ask what network connections each device needs, including connections between devices in the restaurant and connections to outside services. For example, a printer may need to receive tickets from a POS terminal. Separation should protect the environment without accidentally cutting off that necessary path.
With a restaurant POS system, define the result staff need at the point of service: an order reaches the intended kitchen device, the payment status is clear, and a network problem has a named escalation route. Do not assume a POS vendor also manages the router or internet connection.
Compare the setup against a real service workflow
Guest Wi-Fi separation
Ask the network provider to show how guest devices are separated from POS devices, not merely that the networks have different names. Ask which equipment enforces the separation and who can change it. Have the provider explain any connections that must remain open for printing, payments, or other approved functions.
Check the entire path. A separate guest network is less useful if another access point or shared router connects devices in a way no one has reviewed. If the building provides Wi-Fi, ask the landlord or building provider what they control and what evidence they can provide.
Updates and remote access
For routers and access points, ask who installs updates, how staff are warned about planned interruptions, and who checks that the POS and printers reconnect afterward. Identify a fallback if the usual administrator is unavailable. An update policy that depends on one person remembering to act is an operating risk.
For remote support, ask who can connect, how access is approved, what systems are in scope, and how access is removed when it is no longer needed. Ask whether the restaurant can see or request a record of remote access. Also ask how emergency access works outside normal support hours.
Devices, dependencies, and support boundaries
Walk through each device and role: a server using a handheld, a manager calling support, and the technician responsible for the router. Ask which setup functions are available, which require another provider, and whether a particular plan or payment processor is needed. Record an unavailable function rather than treating it as a future promise.
The POS hardware inventory matters here. Fleksa's catalog includes terminals, handhelds, printers, kitchen displays, and kiosks, but compatibility depends on the device, operating system, printer connection, and processor. Get written confirmation before counting an existing tablet or terminal as part of the new setup.
Finally, ask each provider where its responsibility ends. If a terminal cannot reach a printer, who checks the application, who checks the network, and who coordinates the handoff? A support number alone does not answer that question.
Use a network ownership and access worksheet
The following is a hypothetical example for one restaurant with a counter terminal, a handheld, a kitchen printer, and guest Wi-Fi. The restaurant owns the router; a local technician administers it; the POS provider supports the POS application. These assignments are examples, not assumptions about any vendor's service.
Before testing, the owner gets each party to agree to the acceptance criteria and the fallback. The table records the desired result, not a completed test. Add a date, tester, and actual result to your own copy only after an authorized check.
| Area | Owner and fallback | Acceptance criterion | Check or exception |
|---|---|---|---|
| Guest Wi-Fi | Technician; owner contacts backup technician | Guest devices cannot reach the POS devices through the agreed network paths | Authorized technician checks separation; investigate any reachable device |
| Router updates | Technician; backup technician | Update window and post-update checks are agreed with the manager | Manager confirms terminal, handheld, and printer connections after the change |
| Remote access | Technician manages network access; owner approves authorized people | Access has an identified purpose, owner, and removal process | Review the access list and escalation route for an unknown account |
| Order routing | POS provider checks application; technician checks network | A simulated order appears at the intended kitchen device with a clear status | If it fails, providers identify the handoff and manager uses the agreed fallback |
For the simulated order, agree on a training environment or another safe method with the provider first. The exercise must not charge a card, send a guest message, or dispatch a courier. Ask the provider what screen or report should show the simulated order and what the kitchen device should display. If the system cannot safely simulate the workflow, record that limitation and agree on another authorized check; do not present an unrun scenario as a pass.
For network separation, the owner should not try to probe equipment without permission. The authorized technician can perform the agreed check and report the result in plain language: what was checked, what could be reached, and what needs correction. A failed check remains open until the responsible party fixes it and an authorized retest confirms the criterion.
Keep the worksheet where the manager and backup can find it. It should identify the network administrator and support contacts without exposing passwords or other sensitive credentials in a shared service binder.
Set operating rules and handle exceptions
Turn the worksheet into a short service rule: staff report the symptom and affected device to the designated contact; the application and network providers follow the agreed handoff; the manager records when the issue began and which ordering methods are affected. Agree on an approved fallback for taking orders while the issue is investigated. Do not assume card payments or other functions will work offline.
Set a separate rule for changes. A new printer, access point, payment device, or remote support account should have an owner and an approval path. After an authorized change, check the affected workflow as well as guest separation where relevant. A device that prints correctly can still be on the wrong network.
Review exceptions before committing. Who has administrator access if the restaurant changes technicians? Can the restaurant obtain its configuration and access records? What happens if the landlord will not allow changes to shared equipment? Ask for the support scope, responsibilities, response arrangements, and any required equipment or service costs in writing. Compare quoted setup and recurring costs alongside any separately quoted support or change fees; do not treat an incomplete quote as the full operating cost.
If the parties cannot explain or demonstrate the required separation, or no one accepts responsibility for maintaining it, resolve that gap before relying on the setup. A qualified network professional can assess a complex or shared environment. Ask a qualified adviser about contract terms when ownership or support obligations are unclear.
Bring your device list and completed acceptance criteria to a restaurant management software discussion. Request a POS demo using the worksheet, and ask the provider to identify which checks it can perform and which belong to your network administrator.
Frequently asked questions
Is a different Wi-Fi name enough to separate guest and POS traffic?
Not by itself. Ask the network administrator to explain what enforces separation and to perform an authorized check of the relevant paths.
Who should be responsible for POS network security?
Assign responsibility by component. The POS provider may support its application, while a technician, internet provider, or landlord controls network equipment. Name an owner and fallback for each task.
Can staff test an order without processing a payment?
Ask the provider for a safe simulation method. It must not create a real card charge, guest message, or courier dispatch. If no suitable method is available, agree on another authorized check.
