What a Restaurant POS Must Do When the Internet Fails

A restaurant POS should let your team keep taking and tracking orders during an internet outage, but the exact functions depend on the system and its setup. Before buying, verify whether staff can open checks, send orders to the kitchen, update checks and record payments without an internet connection. Then find out how those records return to the system.

Do not treat “offline mode” as a single yes-or-no feature. A terminal may still take orders while a kitchen display, a second terminal or a payment device cannot communicate. A power outage is a different problem again. The right buying decision starts with the tasks your restaurant cannot afford to lose and a practical fallback for the rest.

Separate internet, local network and power failures

Ask the vendor to explain what happens in each situation, using the devices and connections you expect to have in your restaurant. A useful answer names the device where an order is stored, where staff can see it and what happens when the connection returns.

Internet outage: The restaurant loses its connection to the outside internet, but power remains on and the local network is working. Terminals, printers and kitchen screens may still be powered and connected to one another. That does not establish that they can perform every task without a remote service. Test each task separately.

Local network failure: Power remains on, and the internet connection may still be available, but devices cannot reliably communicate over the restaurant’s local network. One terminal might still show an order while another terminal or a kitchen printer cannot receive it. Ask whether devices can work independently and how their records are combined later.

Power failure: Affected terminals, network equipment, kitchen screens and printers are off unless they have a working backup power source. A battery-powered device alone may not help if the network or payment equipment it needs is off. Decide which devices, if any, must stay powered and for how long. Keep a paper procedure for a longer outage.

The table below turns those distinctions into a buying worksheet. Use the final column to guide a demonstration; it is not a promise that any particular system passes the check.

Write down which of your devices depend on Wi-Fi, wired connections or the internet. Include payment terminals, printers and kitchen displays, not just the main register. Review the proposed restaurant POS hardware with the vendor before assuming an existing device will work in the new setup.

Test orders and open checks without internet

Start with a short list of service actions. A busy counter may need to create and complete an order quickly. A full-service dining room may need to keep several checks open, add items and move them between staff. Ask the vendor to demonstrate the actions that match your service model.

For an internet-only interruption, check whether staff can:

• Open a new check and identify its table, pickup name or order number.
• Add an item, quantity and modifier, then see the complete order on the device.
• Send the order to the intended kitchen station or produce a usable ticket.
• Find an existing open check, add another item and see the updated total.
• Apply an approved correction, discount or void, if your service requires one.
• Record the payment types you intend to accept and close the check.

For every action, ask where the result is visible. A saved order is not enough if the kitchen never receives it. Similarly, an order shown on one terminal may be hard to manage if the server expects to retrieve it on another. Check what staff should do when a printer or screen is unavailable: for example, write a ticket and mark it as delivered to the kitchen.

Use a clearly marked hypothetical drill with a practice menu and a test check. Enter one sandwich with a modifier and one drink. Simulate an internet interruption under the vendor’s guidance, add a second drink, and record the screen or ticket where each item appears. The drill must not create a real card payment, send a guest message or dispatch a courier.

Afterward, restore the connection and look for one complete check with the expected items and total. If the order appears twice, or the second drink is missing, note the result and ask how staff should resolve it. Do not assume that closing a screen means the record has reached every device.

Run a separate local-network exercise if the vendor can provide a safe way to simulate it. Identify whether staff must return to the original terminal to find an open check. For a power failure, walk through the paper process instead of switching off equipment during service. Assign someone to number paper tickets, pass them to the kitchen and keep completed checks together for later entry.

Decide how you will accept payment

Order entry and payment acceptance are separate decisions. A POS may let staff calculate a total offline without being able to authorize a card. Ask the POS vendor and payment provider which payment actions are available for your exact equipment and configuration.

Some providers may offer a way to capture card details for later authorization. Do not assume yours does. When authorization is deferred, the restaurant may not know during the outage whether the card will ultimately be approved. A later decline can leave a completed meal unpaid. Ask how staff can identify a pending payment, how long it can remain pending, what limits apply and how a decline is reported.

Also ask whether a pending payment can be canceled or corrected, and who is responsible for following up on a declined transaction. Have the provider explain any restrictions in its agreement. If the operational or contractual terms are unclear, review them with the appropriate qualified adviser.

For a simple hypothetical check, suppose food and drinks total $28 before any applicable tax or tip. A card transaction recorded for later authorization is a pending $28 payment, not a confirmed $28 receipt. If it is declined later, the check is still unpaid. A processing fee, if charged, is a separate cost; a deposit to the restaurant’s bank account is a separate event. None of those measures should be substituted for the check total when staff reconcile the sale.

Set a fallback before an outage. You might accept cash where practical, pause card service or use another provider-approved method. Tell staff who can make that decision and how to communicate it before a guest orders. Do not collect or write down card details as an improvised workaround. For training, use only the provider’s approved simulation or test environment; never run a real card just to prove the process.

Reconcile before retrying or returning to normal

Restoring the internet is the start of recovery, not proof that every record is complete. Assign one person to coordinate the return to normal service. Keep paper tickets and outage notes in order until that person has checked them against the POS.

1. Mark the outage window. Record when the interruption began and ended, which devices were affected and whether it was an internet, local network or power failure.
2. Collect the records. Gather paper tickets and check numbers. On each affected terminal, identify open checks, locally recorded orders and any items awaiting synchronization.
3. Match orders to checks. Compare each kitchen ticket with the corresponding check. Look for missing items, duplicate orders, corrections and checks that remain open.
4. Review payment outcomes. Separate confirmed payments, pending authorizations, declines and payments recorded on paper. Match each outcome to its check rather than relying on a total alone.
5. Investigate before retrying. If an order or payment appears missing, check its status on the original device and follow the provider’s recovery instructions. An immediate retry could create a duplicate order or charge.
6. Document exceptions. Note unresolved checks, the action taken and the person responsible for follow-up. Keep the paper records until the team has completed its review.

Ask the vendor what a synchronization conflict looks like and whether staff receive a clear warning. For example, if two devices contain different versions of one check, who chooses the correct record? Also ask what happens if connectivity returns briefly and then fails again. Your manager needs a procedure for both situations, not just a promise that data will sync.

Practice the checklist away from live service with simulated records. Then, if you arrange a live service pilot, keep normal ordering and payment procedures in place and have a manager monitor actual records. A live pilot is not a reason to interrupt the network deliberately or create unnecessary guest transactions.

Bring your failure cases to the demo

Compare vendors against the same requirements sheet. List the devices, service types and payment methods you use, then ask for a demonstration of each required action and a written explanation of the fallback when it fails. Include questions about hardware compatibility, payment-provider restrictions and recovery support.

Fleksa offers a restaurant POS alongside direct ordering and reservations tools. Ask which of your required outage tasks are supported in the configuration you would buy. If you are also reviewing day-to-day workflows, consider how your restaurant management software fits the paper and recovery procedures.

Next step: Request a Fleksa demo and bring your device list, payment questions and three failure scenarios. Ask to walk through the hypothetical order drill and the recovery checklist before deciding what your team can rely on.

Frequently asked questions

Can a restaurant POS take orders without internet?

Some setups may support order entry during an internet outage, but the available actions vary. Verify where orders are stored, whether the kitchen receives them and how staff retrieve open checks.

Does offline mode mean card payments are guaranteed?

No. A provider may not permit offline card payments, and a payment submitted for later authorization can be declined. Confirm the rules and risks with the payment provider.

What should staff do if the power goes out?

Use the restaurant’s backup-power plan where equipment remains operational. Otherwise, switch to numbered paper tickets and the agreed payment fallback, then reconcile those records when systems return.