It's Friday at seven. The bar's full. Then the internet connection goes down. A server can't close a check. Online orders stop appearing. Music cuts out. The bartender looks at the register, the kitchen looks at the bartender, and everybody looks at the owner.
This is a terrible moment to find out which systems require a connection to the outside world.
A backup plan isn't glamorous. Neither is turning away a full dining room because nobody knows what to do.
Know what actually depends on the network
Walk through a normal transaction: customer orders, ticket reaches the kitchen, food is prepared, guest pays, receipt prints and the sale gets reconciled. Mark every part that needs internet, local Wi-Fi, a working switch or a vendor's cloud service.
The POS might support an offline mode, or it might only queue certain transactions. A payment terminal may handle some offline transactions but expose you to declined-payment risk and card-network rules. Never assume offline payments are available or safe until your provider confirms the limits.
Also check phones, reservations, online ordering, streaming television, digital signage and cameras. Some might keep working locally; others may not. Write down which is which.
Separate 'internet down' from 'network down'
If your provider loses service, the equipment inside the building may still be healthy. If the router, Wi-Fi or switch fails, a second internet service may not help at all.
Know who to call and what to check safely. Label the equipment. Save vendor support numbers somewhere staff can reach without the internet. Protect admin credentials rather than taping passwords to a wall.
A secondary connection or cellular failover may make sense for a busy venue, but test that it can support the payment and operational systems you actually need. Streaming eight televisions is a different problem from authorizing a credit card.
Write a one-page 'when this happens' sheet
Tell the team who makes the decision to switch modes, how to take and track orders, how to explain a delay to guests, what payment methods are approved and how transactions will be reconciled afterward. Include a clear stop rule for situations where accepting a payment would be unsafe or violate provider policy.
If your fallback uses handwritten tickets, number them and keep a record of what was fulfilled. If cash is an option, establish cash-handling controls. If a system is down, don't improvise insecure workarounds with customers' card details.
The best plan is boring enough that a shift leader can follow it under pressure.
Test on a quiet morning
With your vendors' guidance, schedule a controlled test rather than unexpectedly unplugging equipment during service. Confirm which systems keep working, how staff know they're in backup mode, what data will sync after restoration and who checks for duplicate orders or charges.
Record what failed. Fix the process. Run the test again after major system changes.
Technology is part of hospitality
Guests don't care which vendor's router you bought. They care whether you can take an order, provide an accurate bill and tell them what's going on. A reliable network makes that possible quietly. A poor one becomes part of the guest experience very quickly.
If nobody in the building knows how the technology fits together, that's an operational risk you can address before the next Friday rush.
