The screen goes dark, or it freezes, or the card machine keeps saying it cannot connect. There are eleven people in front of you, six tables waiting on checks, and the kitchen is still calling food. This is the worst possible moment to start learning how your technology fits together.
A restaurant POS system down in the middle of service is a timing problem before it is a technical one, so the sequence below runs the cheapest and fastest checks first.
Table of Contents
Restaurant POS System Down: The First Fifteen Minutes
- Tell the queue plainly that card payments are down, and keep serving.
- Start writing orders on paper. The kitchen keeps cooking, service keeps moving.
- Check power and cables at the till and the card machine.
- Check whether the internet is down, using a phone on the wifi.
- Restart the card machine once, then wait two full minutes.
- Ask your staff what changed in the last hour.
- Call for help while the paper system carries the room.
That sequence works because it protects trade first and diagnosis second. A room that is still being served will wait. A room that has been told nothing will leave. If you already have restaurant and retail technology support in place, step seven happens at the same time as steps three to six, not after them.
Most people treat an outage as a checklist. It is better understood as a clock, because the cost of standing still rises every minute.
Minute 0 to 2: Announce, then switch to paper. Nobody touches a cable yet. Two members of staff take the floor and the door, so the queue stops growing.
Minute 2 to 5: Physical checks only. Plugs, sockets, switched off wall switches, cables pulled loose by a cleaner or a delivery. Then one restart of the card machine, and one only.
Minute 5 to 15: Work out which of the four things below has failed, so that when you do call someone you can say what you saw rather than “it is not working”. Then call. If you are in the Fox Valley and you have nobody to ring, call 630.827.3300.
The point of the clock is that it ends. Fifteen minutes of your own effort is reasonable. An hour of it, during service, is not, and the difference is usually a decision nobody makes because everyone is busy.
Work Out Which of Four Things Actually Failed
Almost every till and card machine failure sits in one of four families, and you can usually tell them apart in under a minute. They are listed here in the order worth checking, because the first two are free to check and the last two are not your job to fix.
| What you can see | What has probably failed |
|---|---|
| Nothing is lit, no fans, no standby light | Power or a cable that has come loose |
| Till works, card machine says no connection | The internet line into the building |
| One card machine fails, another still takes payment | That one device |
| Everything is on and connected, nothing goes through | The system behind the till |
Power and the sockets nobody checks: Start here, always. Power strips under counters get kicked, switched sockets get turned off during cleaning, and a cable behind a fridge gets nudged out by half a centimetre, which is enough. Look for a standby light on every box involved, feel whether it is warm, and push each cable in firmly at both ends rather than just looking at it.
Then settle the easy one. When a single handheld or a single card machine fails while another one works, the fault is almost certainly that device. Take it out of service, use the one that works, and stop troubleshooting it during trade. Operators keep investing in connected technology across ordering, payment and reporting [1], which is exactly why one failed device should never be allowed to stop the whole room.
That leaves the two families that look identical from behind the counter, and this is where most operators guess wrong and lose twenty minutes.
The Internet Line Versus the System Behind It
Your card machine usually needs two different things to work. It needs a working internet line out of the building, which is the connection you pay a monthly bill for, and it needs the system on the other end that actually authorises the payment. Both can fail, and from behind the counter they look the same, but the test that separates them takes ten seconds.
Pick up a phone, turn mobile data off so it is using the restaurant wifi only, and try to load any ordinary web page. If the page will not load, your internet line is the problem, and that is a call to whoever provides that line. If the page loads normally but the card machine still will not authorise, your line is fine and the failure is further down the chain, in the system that processes the payment. That is a different call, and knowing which one to make is most of the value of these fifteen minutes.
Keep Taking Money While You Fix It
Can you write down card numbers if the card machine is down? No. Full card numbers should not be written down or stored, and taking cash, or holding the table and settling when the system returns, will protect more of your revenue than a page of card details ever will.
The reason is simple. The moment a card number is written on paper, that paper is sensitive data sitting in a busy kitchen [2][3]. It can be photographed, dropped, binned, or read by anyone walking past the pass. If paper carrying card details ever does end up in your hands, the published guidance for small merchants is to mark through the data with a thick black marker until it is unreadable, and to lock the paper away until it can be destroyed [2]. Keeping it to “process later” is the version that goes wrong.
What to do instead: Take cash where the customer has it. Most people still carry some, and cash remains in wide everyday use, though it covers a minority of transactions overall, so it will not save a full service on its own [4]. Ask whether the customer can pay by another method they already have on their phone. Keep the table open and take payment when the system returns, if the customer is staying. For regulars and accounts, take the order, serve it, and settle it later in the day. None of these are elegant. All of them beat losing the cover.
Writing Card Details Down, What Is Actually Allowed
The published card security standard is built around a straightforward principle: if you do not need card data, do not keep it, and anything you do keep has to be protected properly [2][3]. Taking a payment by phone, and handling card details spoken aloud, has its own published guidance because it carries its own risks [5]. That guidance exists precisely because the informal version, a number scribbled on a docket by a busy manager, is where small businesses get caught out.
There is one more thing worth knowing. Some payment setups can be configured to hold a payment temporarily and complete it when the connection returns, without anyone writing anything down. Whether that is available to you, and on what terms, depends entirely on your own arrangement, so confirm the correct fallback procedure with whoever processes your payments before you need it, and write down what they tell you. Ask on a quiet Tuesday. Do not ask on a Friday night.
Three Signs the Floor Cannot Fix This
A cable pushed back in is a two minute problem, while a fault on the line into your building, or in the system that authorises payments, can run for hours and is genuinely outside your control, and there is no honest average sitting in between. What you can judge is whether the room can fix it at all, and there are three clear signs that it cannot.
Nothing has changed after one restart: One restart is a fair test. A second and third restart are just hope, and each one costs you five minutes of service.
More than one device is affected: A single failed handheld is a device problem. Two tills and a card machine failing together points at something shared, the line, the network, or the system behind them, and none of those are fixed from the counter.
You cannot say what changed: If nobody knows whether something was unplugged, updated, moved, or replaced this week, you are guessing. Guessing during service is expensive, and the honest move is to stop and let the paper system carry the room while somebody looks at it properly.
None of that is failure on your part. It is the same logic behind planning for the day the system stops, which is a normal part of running any business that depends on equipment it did not build.
What Should Already Be Set Up Before the Next Outage
Preparing for a POS failure before your next busy season comes down to six things, and almost all of them have to exist before the outage starts. Published continuity planning guidance rests on the same idea, which is to decide in advance how critical work carries on when the usual system is unavailable, and then practise it [6].
- A one page outage card taped inside a cupboard by the till, with the steps above in order
- A paper ticket pad, a pen that works, and staff who have actually practised a paper service
- A second way to take payment that does not depend on the same internet line
- Two phone numbers on paper: whoever processes your payments, and whoever supports your technology
- Labelled equipment, so anyone can say which box is the internet line and which is yours, plus two spare cables
- Keeping payment traffic on its own network, separate from guest wifi and everything else
Run it once, on a quiet shift, before you need it. Ten minutes of pretending the system is down will teach your team more than any document, and it will show you which of these six you do not actually have yet.
Getting Help Fast in the Fox Valley
Biz ReTek works with restaurants, shops and small businesses across the Fox Valley, including Romeoville, IL and St. Charles, IL, on point of sale, networks, and the day to day technology a working room depends on. The team brings 95+ years of combined IT experience, and the site lists 24/7 technical support for the hours when a failure actually happens, which is rarely during office hours.
If your till or card machine is down right now, or you want the preparation above put in place before the next busy season, our restaurant IT support starts with a conversation about how your room actually runs. Call 630.827.3300.
Key Takeaways
- Protect trade first: announce the problem, switch to paper, and only then start checking anything
- Work the outage as a clock, not a checklist, and stop your own troubleshooting at fifteen minutes
- Four failure families cover almost everything: power, the internet line, the device, or the system behind the till
- Do not write down full card numbers, and confirm the correct fallback procedure with whoever processes your payments
- The preparation is what shortens the next outage, and almost all of it has to exist before the outage starts
References
Restaurant and Payment Research
[1] 2026 State of the Restaurant Industry. Industry research on operator priorities, including continued investment in technology that supports efficiency and guest experience.
[4] 2026 Diary of Consumer Payment Choice, May 2026. Annual research on how consumers in the United States pay, including how many carry cash and how often they use it.
Card Data Security Guidance
[2] Data Security Essentials for Small Merchants: Guide to Safe Payments, Version 3.0, April 2024. Guidance for small businesses on not storing card data, and on securing and destroying paper that carries it.
[3] PCI Quick Reference Guide: Understanding the Payment Card Industry Data Security Standard. Plain language overview of what counts as cardholder data and how it must be handled.
[5] Information Supplement: Protecting Telephone-based Payment Card Data. Published guidance covering card details taken and handled over the phone.
Continuity Planning Guidance
[6] Business Continuity Planning guidance for businesses. Government guidance on identifying critical work and planning how it continues when normal systems are unavailable.