POS terminals
Use a modern tablet, laptop or touch terminal with a supported evergreen browser, stable power and assigned location/service point.
Device, printer, browser and network expectations for running Limvero in a restaurant.
Limvero is web-based, but reliable restaurant operations still depend on stable devices, network and provider hardware.
Use a modern tablet, laptop or touch terminal with a supported evergreen browser, stable power and assigned location/service point.
Use always-on browser devices with clear station visibility, reliable Wi-Fi or wired network and device heartbeat enabled.
Network ESC/POS printers can be used through the print worker. Test kitchen and receipt print queues before service.
Separate guest Wi-Fi from operational devices where possible and keep terminals, printers and kitchen screens on a stable network.
POS and KDS use offline-aware queues for selected workflows, but payment-sensitive actions update only after server replay.
Acquiring terminals, fiscal devices, delivery tablets and certified provider hardware remain governed by provider requirements.
Use these checks before deploying terminals and kitchen screens into live service.
Do not run POS/KDS in private browsing. IndexedDB and service worker support must be available for offline-aware behavior.
Each operational device should be paired, active, assigned to the correct location and reviewed before go-live.
Run receipt, kitchen ticket, failed-print and stale-print recovery checks before the first live service.
Certified fiscal, payment and delivery hardware is provider-specific and should be confirmed during rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.