Keeping retail and hospitality sites online
In a shop or a restaurant, an outage is lost revenue by the minute. The useful question is not whether connectivity can fail, but what keeps working when it does, and in what order things come back.
Decide what must survive an outage
Not every system at a site matters equally during an outage. Payment terminals and ordering systems are usually the priority, because they stop trade directly; phones matter for coordination and customers; guest or back-office traffic can wait. Deciding that order in advance turns a vague resilience requirement into a specific one, and tells you what a backup connection actually has to carry.
Then test it. Cause the primary connection to fail and watch what happens to payments, ordering, phones and the rest. Multi-site operators especially benefit from doing this once, properly, because the same design then repeats across the estate. The boundaries matter too: the site network, the connectivity provider and the application suppliers each own part of the outcome, and an outage that is really a payment-provider problem should not be chased as a connectivity fault.
Connectivity that fits a multi-site estate
A consistent design across sites is easier to run than a patchwork. A primary access service with a backup path, and a way to prioritise the systems that matter during a failure, is the usual shape. Netavo provides fibre and Ethernet access, private WAN, mobile data and voice services that can underpin a multi-site estate with a consistent approach. Mobile failover is available on any of Netavo's access types. Connectivity alone does not establish payment-card compliance, which remains the operator's and payment provider's responsibility.
Common questions
What should keep working during a site outage?
Usually payments and ordering first, then phones, then back-office traffic. Decide the priority in advance so a backup connection is sized for what actually has to survive, and test it by failing the primary link.
Is a backup connection enough on its own?
Only if the systems that matter are prioritised onto it and the failover is tested. A backup that everything competes for, or that was never proven, is not resilience.
Does connectivity make my payments compliant?
No. Payment-card compliance is the operator's and payment provider's responsibility. Connectivity supports the service; it does not establish compliance on its own.
Related services and sectors
Connectivity & WAN
Fibre and Ethernet access, private WAN and resilient connectivity, from a single site to a national estate.
Explore connectivity →Cloud Voice & Numbering
Hosted telephony, SIP trunking and numbering on our own platform, for a single user or a contact centre.
Explore voice →Retail & Multi-site Estates
Fibre, Ethernet and private networking for branches and head offices, with mobile failover and estate telephony.
Explore retail and multi-site →Hospitality & Food Service
Site connectivity and mobile failover for trading, private data for connected equipment and telephony for hospitality estates.
Explore hospitality →Keeping your sites trading?
Tell us about your estate and what must stay up, and an engineer will talk through a consistent resilient design.
Work with us →