Connectivity and continuity
What Happens to Restaurant Orders When the Internet Goes Down?
A restaurant's ordering and payment workflows depend on internet connectivity to different degrees depending on the vendor and the specific workflow — so "does your POS work offline" is not a yes/no question with one correct answer. Some vendor commentary places the direct revenue exposure of a total connectivity outage at roughly $1,200–$3,500 per hour for a small-to-medium restaurant, a commonly cited industry estimate, not a precise or universal figure, and not a VISSTRO-specific number.
Published September 28, 2026 · VISSTRO Editorial Team
What internet-dependent workflows can lose during an outage
Depending on the system, a connectivity interruption can affect: the ability to take new orders at all, the ability to process card payments, the ability to send an order to the kitchen, and the ability to sync sales/inventory data. Not every vendor's system loses all of these at once — but almost none guarantee zero impact across all of them.
Why "offline POS" is an imprecise phrase
Vendors use "offline POS" to describe everything from full offline parity (every workflow keeps working exactly as online) to a narrow fallback (only some order types are captured, everything else is unavailable until connectivity returns). Because there's no fixed industry definition, the phrase alone tells an operator nothing concrete — the only useful information is which specific workflows are covered, not whether the label is used at all.
What VISSTRO's current scope covers — and does not
VISSTRO's currently supported offline behavior covers two specific, verified mechanisms: orders taken while the connection is down are stored durably and submitted once the connection returns, and supported Cash/Card tenders taken while the connection is down are captured and reconciled once the connection returns.
Offline Mixed Tender, Offline Split Bill, and Offline Refund/paid-order recovery are explicitly not part of the current offline scope — this is stated exactly as scoped on the Operational Continuity page, and this article does not imply anything broader than that.
Restaurant offline-readiness checklist
Questions worth asking before you need the answer during a real outage:
- Which specific order types can still be captured if the connection drops — all of them, or only some?
- Which specific tender types (cash, card, other) are still supported if the connection drops?
- What happens to an order that was mid-way through being modified or split when connectivity dropped?
- How does the system behave the moment connectivity returns — does it require a manual step, or does it reconcile automatically?
- Which workflows does the vendor explicitly say are NOT covered offline, in writing — not just what they say IS covered?