Offline is not one all-or-nothing capability
A restaurant may retain some local functions during an internet outage while losing others. Entering an order, sending it across the local network, receiving an online order, and completing a card transaction depend on different parts of the setup. Ask the provider to describe each separately. Do not interpret an offline label as permission to continue every normal activity or assume that all devices will share the same information.
Create a simple capability sheet with three columns: confirmed to work, confirmed not to work, and requires a separate approved process. Include the actual terminals and kitchen equipment your team uses. The table-service overview helps map the guest journey, but only a demonstration of the proposed arrangement can establish which steps continue during a particular type of outage.
How will orders reach the kitchen?
Distinguish loss of outside internet from a local network or power failure. A local printer might continue in one situation and be unavailable in another. Have the authorized technical team explain the dependencies rather than disconnecting production equipment during service. Rehearse the provider's documented safe test procedure and confirm how staff will recognize whether an order was actually received, instead of assuming that tapping send proves delivery.
Keep a documented fallback for identifying tables and tracking pending items. If that involves paper, assign responsibility for each handoff and for reconciling the notes afterward. Avoid sending the same order twice when the connection returns. The kitchen-routing guide offers a useful distinction between entering an item and confirming that the correct preparation station has received the current instruction.
What about card payments and uncertain results?
Payment behavior must come from your payment provider's documented instructions. Some arrangements have limited offline options; others require a working connection. Eligibility, risk, authorization, and later processing can differ. Do not invent a workaround, record card details in an order notebook, or promise that a transaction will eventually succeed. Staff should know when to stop and contact the responsible provider or manager.
An interrupted transaction needs a status check before anyone tries again. Keep the approved transaction reference and follow the provider's process for establishing whether payment completed. An apparent error is not sufficient evidence that no charge occurred. The contactless checkout guide provides a broader operating checklist for completion signals, supported alternatives, and avoiding duplicate attempts when the payment step becomes uncertain.
How does the team return to normal service?
Restoring a connection is the beginning of recovery, not proof that every record has synchronized. Review open checks, pending kitchen work, queued online orders, and uncertain payment states using the approved process. Give one manager ownership of the reconciliation so several employees do not independently re-enter the same work. Record unresolved exceptions and the person responsible for following them up after service.
Keep the outage plan brief enough for a new employee to use: recognize the problem, notify the owner, use confirmed functions only, follow the fallback, and reconcile before closing the incident. Test it safely outside a rush. Use the POS buyer's guide to document the demonstrated limits, support contacts, and recovery responsibilities before relying on an offline capability in daily restaurant operations.

