Restaurant POS and kitchen order workflow
POS and KOT

Restaurant Internet Outage Checklist: Orders, Payments and Recovery

Keep restaurant service organized during an internet outage with a practical checklist for offline POS payments, kitchen tickets, backup connections and recovery.

Share this article

Key takeaways

  • Test order entry, kitchen communication and card payments separately; an offline POS label does not establish that every function works.
  • Set both a per-check policy and an aggregate exposure limit for payments awaiting authorization.
  • Recovery requires checking every affected device, payment and order before returning to normal service.

When your restaurant loses internet access, put one manager in charge, identify which systems still work, switch to your tested ordering and payment fallback, and record exceptions for reconciliation. An offline payment feature may let you accept a card, but authorization can happen later, after the guest has left.

This restaurant internet outage checklist helps independent US restaurants prepare before service, manage the interruption and recover without charging guests twice or sending duplicate tickets to the kitchen. Your exact options depend on your POS, payment hardware, network and processor agreement.

Vendor documentation checked November 16, 2026. The procedures below are editorial recommendations to adapt with your providers.

1. Use the first five minutes to establish control

Start by naming an incident lead. That person coordinates support, chooses the fallback and tells staff when procedures change. Give another employee responsibility for guest communication so every server does not invent a different explanation.

  1. Record the start time. Note the error message, affected devices and last known successful order and payment.
  2. Check the scope. Is one handheld affected, every POS terminal, the kitchen display, or only card processing?
  3. Check provider information. Use a phone on cellular data to inspect your ISP and POS or payment provider status information.
  4. Activate the documented fallback. Tell staff which devices, payment methods and ticket process to use.
  5. Assign online-order responsibility. Someone must check whether remote orders are still being accepted.

Pause before repeatedly retrying a payment with an uncertain result. Record the check and transaction reference, then follow your processor's status-check procedure. A timeout alone does not establish that a charge failed.

Use a brief guest explanation: explain the connection problem, state the payment options you have confirmed and give a realistic update about service delays. Tell arriving guests before they order if their payment choices are restricted.

2. Separate internet, local network, provider and power failures

Different failures need different responses. A working Wi-Fi symbol only confirms a wireless connection; it does not prove the restaurant can reach its cloud services.

Possible failureUseful clueNext decision
Internet serviceMultiple devices cannot reach outside services, but local equipment may communicate.Check the ISP and use an approved backup connection if available.
Local networkPOS devices cannot reach printers or other local hardware.Use the documented ticket fallback and contact network support.
POS or payment serviceOther websites load, but a particular service fails.Check that provider's status and disruption procedure.
Single deviceOther terminals continue working.Protect pending transactions and follow device-specific support instructions.
PowerTerminals or network equipment have no power.Follow the restaurant's power-outage and operating-safety procedures.

These clues guide investigation; they are not definitive diagnoses. Lightspeed's K-Series troubleshooting documentation recommends checking another device, ISP outage information, cables and equipment lights. It also warns that rebooting network equipment interrupts connectivity.

A cellular connection may bypass a failed fixed internet line. It cannot repair an unavailable payment service or replace power for the equipment. Have your network provider document the supported failover path before a rush.

3. Build an offline capability checklist for your actual equipment

Ask your POS and payment providers to complete a simple worksheet for your exact app version, terminal model and configuration. Record an answer, limitation and test date for each function:

  • Enter new orders, modifiers and allergy notes.
  • Retrieve open checks and add items to existing tables.
  • Send new tickets and changes to each kitchen station.
  • Accept each supported card presentation method and cash.
  • Apply tips, split checks, void items and issue refunds.
  • Receive website, QR and delivery-platform orders.
  • Use gift cards, loyalty balances and reporting.

Mark untested functions as unconfirmed. Do not make the first experiment a guest's large catering payment.

For example, Square's US offline-payment documentation excludes EBT/SNAP, Square Gift Cards, manually entered card numbers and Tap to Pay on iPhone and Android. A phone that normally accepts payments therefore does not automatically provide an offline backup.

In Toast's preparation documentation, background card processing, transaction limits and employee permissions are separate configuration decisions. Confirm the current settings in your own account instead of relying on a remembered default.

For the normal relationship between order entry and preparation, see our restaurant POS and kitchen order ticket guide. Add the outage behavior beside each normal handoff.

Illustrative pickup order screen and prepared takeaway bags
Illustrative pickup order screen and prepared takeaway bags

4. Set a payment policy before accepting offline cards

Offline card capture can leave the restaurant waiting for authorization. Square states that sellers are responsible for expired, declined or disputed offline payments. Build your policy around the amount your business can afford to leave unresolved.

Decide which payment methods staff may offer, the largest offline check they may accept, who approves exceptions and when the manager must reassess the total. These operating limits should fit within your provider's supported controls.

Worked example: track aggregate exposure

Illustrative assumptions: A neighborhood restaurant accepts 18 offline card checks averaging $42, including tax and tips. The total awaiting authorization is 18 × $42 = $756. If another 30 similar checks arrive, that adds $1,260, bringing the total to $2,016.

This is the value awaiting authorization, not an expected loss or a decline forecast. Even a modest per-check limit can allow substantial aggregate exposure during a long outage. Choose an internal review threshold and assign someone to monitor it.

Do not turn paper tickets into a card-data collection system. Keep full card numbers and security codes out of notebooks, texts and spreadsheets. Use only the payment collection process your provider supports. If no suitable payment option remains, the manager needs to decide whether to restrict new orders rather than improvise.

5. Keep kitchen tickets and online orders under one clear process

Choose one route for new kitchen work during the incident. If digital routing is confirmed to work, keep using the tested process. If it fails, switch affected orders to numbered paper tickets and name the person who hands them to the kitchen.

Each paper ticket should include the time, table or pickup identifier, items, quantities, modifiers, allergy notes, employee initials and payment state. Use a recognizable prefix, such as OUT-001, so staff can distinguish outage tickets during reconciliation.

Label changes and cancellations against the original number. Ask the receiving kitchen employee to acknowledge them. Track preparation, handoff and payment separately: food being ready does not establish that the check is paid.

Remote ordering needs its own owner. A guest may still reach your website over cellular data while the restaurant cannot receive the order. Where provider controls allow it, pause affected channels or adjust availability through the supported process. Confirm the change from the guest-facing side.

Use our guide to coordinating dine-in, takeaway and delivery orders to map those channels. Keep current printed menus available too; our QR, PDF and printed menu comparison explains their different service roles.

Illustrative restaurant host welcoming guests
Illustrative restaurant host welcoming guests

6. Test the backup connection and rehearse a short outage

A backup connection is useful only when the required equipment can use it. Ask your network provider to demonstrate the approved path for terminals, kitchen hardware and payment devices. Moving one tablet to a personal hotspot may leave its printer on another network.

Toast recommends considering cellular backup with an IT professional or networking consultant. Treat coverage, compatible hardware and failover configuration as items to verify at your location.

Schedule a supervised drill outside service, using vendor-approved test procedures. Protect existing transactions first; do not disconnect production equipment without understanding the consequences.

  1. Identify the simulated failure and name the incident lead.
  2. Enter a test order with a modifier and send it to the intended station.
  3. Demonstrate the approved payment fallback without collecting real card details on paper.
  4. Check what a remote guest would see when ordering.
  5. Restore service and reconcile the test records.

Record what worked, what failed and who owns each correction. Repeat after significant equipment or configuration changes. Keep a dated paper response sheet near the manager station, with provider contact details, device identifiers, payment limits and recovery instructions. Exclude passwords and other credentials.

7. Reconcile payments and orders before declaring recovery

One online terminal does not establish that every device has uploaded its transactions. Have the incident lead account for each affected terminal and handheld, including equipment set aside during the interruption.

Use your vendor's recovery sequence. Square warns that signing out, deleting its POS apps, switching modes or locations, or factory resetting with pending offline payments can permanently lose those payments. Its upload deadlines also vary by hardware; check the current instructions and device countdown immediately.

Toast's recovery guide directs operators to confirm device connectivity, review payment status, reconcile denied payments and check queued online orders. It specifically warns against using Capture in Close Out Day while outage payments are processing.

For your incident record, reconcile:

  • Payments: separate pending, approved, declined and unresolved transactions; investigate ambiguous results before another charge.
  • Orders: match paper tickets to digital records and distinguish food already prepared from work still required.
  • Online queues: review delayed orders before releasing them to the kitchen or promising pickup times.
  • Closeout: document cash, tips, refunds and remaining exceptions for follow-up.

When entering a paper sale into the POS, use the supported reconciliation method that avoids firing an already completed order again. Give unresolved items an owner and follow-up time.

8. Ask vendors for specific answers before buying more technology

Use your drill results to identify the next improvement. The answer might be better staff instructions, a supported backup connection or clearer payment permissions. It does not automatically require replacing the POS.

Ask prospective providers which outage types their offline mode handles, where pending records are stored, which payment methods work, when transactions expire and who bears the loss if authorization fails. Request the recovery instructions alongside the feature description.

Also ask whether the proposed capability requires particular hardware, software, account eligibility or an additional service agreement. For backup connectivity, request the equipment charge, recurring service charge, data allowance and support responsibility in writing. This article does not quote vendor prices.

For OrderNow or any other platform under consideration, request evidence for your intended configuration rather than assuming offline ordering, payment processing or integrations are included. A useful demonstration should follow a complete order through interruption and reconciliation.

Finish preparation with a dated checklist, named staff responsibilities and a completed drill. Review those documents whenever your restaurant changes its ordering or payment setup.

Put your restaurant workflow to the test

Explore a connected digital menu with OrderNow.

Try your own menu and service process before choosing the tools your restaurant needs.

Start free

Frequently asked questions

Can a restaurant accept credit cards without internet?

Some supported POS and payment configurations can store card payments offline for later authorization. Eligibility, payment methods, limits and upload deadlines vary. Confirm your exact setup before relying on it, and remember that a stored payment may later be declined.

Will a cellular hotspot restore the entire restaurant POS?

It may help during a fixed-line internet outage, but terminals, printers and other equipment must use a supported network configuration. It will not resolve an unavailable payment provider, a cloud-service outage or equipment without power. Test the complete workflow with your provider.

Should staff restart the POS when payments stop working?

Follow the provider's instructions for the specific failure and pending-payment state. Avoid improvised sign-outs, app deletion or resets. Record affected checks and device identifiers first, and contact support when the correct recovery action is unclear.

How can we prevent duplicate orders after the connection returns?

Number outage tickets, track whether each was prepared and paid, and reconcile them against restored digital queues. Use the POS provider's supported method to record completed paper sales without sending them to the kitchen again.

Sources and further reading

Sources reviewed November 16, 2026. Prices and product details can change; confirm current terms with the provider.

Designed for restaurants, cafés, hotels and food businesses that need a clearer mobile menu and a more connected order flow.
Request Demo Start Free