Free QR menu, free for good Full system free for 30 days, no card
POS and operations

What Happens When the Café's Internet Goes Down

8 min read
In short
  • A cloud till stops when the internet does. Order taking, the kitchen screen, the waiter's phone and the QR menu all talk to the same server, and a connection failure stops them together — there is no offline mode that quietly carries on.
  • The till shows a red banner and refuses to send orders; the basket on the waiter's phone is kept, so nothing typed is lost, only delayed.
  • What carries on is everything that never needed the cloud: cash from the drawer, the card terminal if it has its own connection — check with your provider — and paper.
  • The paper fallback works only if it was prepared: order pads with table numbers, a current price list by the till, and a phone hotspot rehearsed in advance.
  • When the connection returns, re-key the written orders into open bills and carry on; re-sending the same basket does not double-post it, and the screens catch up on their own.
  • In the worked example here, a 40-minute Saturday outage at 09:10 produced 14 paper orders — 11 cash, 3 card — re-keyed by 10:00 with a close that matched to the coin.

Every café that runs on a cloud till carries the same fragility, and pretending otherwise is how a bad morning becomes a terrible one. The truth is simple: the system lives on the internet, the internet sometimes does not, and the difference between an annoying half hour and a lost Saturday is whether you prepared for it. This article is the honest version — what stops, what carries on, and the paper routine that keeps a full room fed and paid while the router reboots.

What a Cloud Till Actually Needs

Not wifi, specifically — internet. The till tablet, the kitchen screen, the waiter's phone and every guest scanning the menu are all talking to the same server somewhere else, over whatever connection the venue has. That is what makes the system work everywhere at once, and it is also why a cut cable, a dead router or an ISP outage lands on all of it simultaneously. There is no local brain that keeps the café running when the line is down; the brain is elsewhere, and the café is holding a tablet.

When the connection dropsStatusWhat you do instead
Taking orders at table or tillStops — red banner, orders cannot be sentPaper pad: table number, items, name
Kitchen displayStops receiving new ordersPaper tickets walked to the pass
QR menu for guestsStops loadingMenu boards, spoken menu, counter ordering
Card terminalOften carries on — its own connectionCheck with your provider beforehand
CashCarries on, alwaysDrawer, change, honesty

The Paper Fallback, Prepared in Advance

The routine that works during an outage is bought in the quiet weeks before it. Order pads — pre-printed or photocopied, with space for a table number, the items, the price and a name — live in a marked drawer by the till, with two pens that write. A current price list is taped inside that same drawer, because the member of staff who can recite every price is always on holiday when the router dies. The phone hotspot has been joined by the till tablet at least once, in a monthly ten-minute test, so it is a procedure and not a theory. Total cost: an hour and a drawer.

During the Outage — a Sequence

  • Declare it out loud. One person says: internet is down, we are on paper. The room relaxes when the staff visibly have a mode.
  • Write every order on the pad — table number, items, name — and walk it to the pass yourself. The paper is now both the order and the ticket.
  • Take cash into the drawer with change from the float, and note the amount on the same paper. Card only if your terminal is genuinely alive; if it is not, say so cheerfully and take cash.
  • Tell guests the truth at the counter — cards or a five-minute wait — rather than discovering the limits order by order.
  • Keep the paper. Every written order is a bill you owe the system later, and the stack is the re-entry list.

Worked example

Saturday, 09:10, a full room and the connection drops. The duty manager calls it — paper mode — and within a minute the counter is taking orders on pads, cash into the drawer, amounts written beside each. The bar keeps making drinks from the walked-over paper tickets; the QR codes stop working and the menu boards absorb it. Fourteen orders land on paper across 40 minutes: 11 paid cash, 3 paid card on a terminal that, as it turned out, still had its own signal. At 09:50 the router comes back, the till's banner clears, and the manager re-keys the stack into open bills — table numbers first, then payments recorded against each — while the Saturday continues around it. By 10:00 all 14 are in, the day's counts are right, and the evening close matches to the coin. Afterwards: the hotspot gets a monthly test, and the pads get their own labelled drawer, because the search for a working pen at 09:11 is the part nobody wants to repeat.

When It Comes Back

The recovery is calmer than the drop. The connection returns; the till's banner clears; the screens refresh themselves — the kitchen board reloads on its own timer rather than needing someone to find a refresh button. The waiter's phone still holds the basket that would not send, and sending it now simply works: the same basket will not post twice, so a nervous double-tap during recovery costs nothing. The work that remains is human — re-keying the paper stack into open bills, recording the payments taken in cash and card against them, and then checking once, at the end, that the day's totals describe the day that actually happened.

The Backup Connection

A café's first backup connection is a phone, and that is usually enough: the till tablet joins the hotspot, the cloud is reachable again, and the outage becomes a footnote. If your venue's line fails more than once or twice a season — some streets are simply like that — a second line or a router with a mobile fallback pays for itself the first time it saves a Saturday. Whatever the answer is, test it monthly and off-peak. The backup that has never been joined by the till is not a backup; it is a plan to read a manual under pressure.

What to Ask Any Provider

If you are choosing a system rather than running one, this failure is worth asking about directly, in boring detail: which parts keep working offline, what happens to an order typed during the drop, and what the recovery looks like. The answers separate vendors quickly. Cloud systems — including Kafe360 — give you the honest version above: order management stops with the connection, the basket is kept on the phone, nothing double-posts on the way back. Hardware-led systems often cache locally and sync later, trading that resilience for the work of maintaining the box under the counter; the comparison is worth making with both eyes open, and cloud versus hardware terminals sets out the trade-offs properly.

Two things Kafe360 does not do, stated plainly because outages are the wrong time to learn them. It does not work offline — no cached order mode, no local fallback. And it stores nothing card-related locally, because it never handles cards at all; the terminal's own offline behaviour is a question for your card provider, not this system. Ask every vendor the same two questions and weigh the answers against how often your connection actually fails.

The Outage Kit

  • Order pads with table numbers, in a labelled drawer by the till, with two pens.
  • Current price list taped inside the drawer, updated when the menu changes.
  • Phone hotspot known by name, tested monthly, data plan that survives a Saturday.
  • The sequence printed on the inside of the drawer: declare, paper, cash, walk, keep.
  • A named decision-maker for declaring paper mode, so it is never a committee.

You cannot prevent outages; you can make them unremarkable. The café that has the drawer, the hotspot and one rehearsed staff member turns a 40-minute connection failure into a story told at closing — not a morning of comped coffees and apologies.

Test the honest version during your trial — join the hotspot, watch the banner, re-key a paper order. Kafe360 is $249 a year, with a 30-day free trial and no card to start.

Start your 30-day free trial

Frequently asked questions

Does Kafe360 work offline?
No. It is a cloud system: the till, the kitchen screen, the waiter's phone and the QR menu all talk to a server over the internet, and when the connection drops they stop — a red banner appears at the till and orders cannot be sent. There is no offline mode that caches orders for later, and we think it is better to say so plainly than to let you find out at 08:40 on a Saturday.
What happens to the order I was typing when the connection dropped?
The basket on the waiter's phone survives — it stays on the screen rather than vanishing — so the order is not lost, only undelivered. When the connection returns, the same basket is sent and the order reaches the kitchen then. Sending it again does not create a duplicate: the system will not double-post the same basket, so an impatient extra tap during the recovery is harmless.
Should I buy a backup connection?
Probably, and it need not be expensive. A phone hotspot is the standard backup for a café — the till tablet joins it in a minute — and if your venue's connection fails more than once or twice a season, a second line or a router with a mobile fallback earns its cost quickly. Whatever the backup is, test it monthly, off-peak, because an untested fallback is a rumour.
Don't traditional terminals keep working offline?
Some hardware-based tills cache orders locally and sync later, and for a café that trades somewhere with genuinely fragile connectivity that is a real argument for them — the trade-offs of cloud versus local systems are worth reading in full before you choose. What matters is that you know, before the outage, which kind of system you are standing in front of, and what its failure mode actually is.
How often should we rehearse the paper routine?
Monthly is plenty, and ten minutes off-peak is all it takes: run one order per staff member from paper, into the till, as if the connection had just returned. The point is not the typing — it is that when the outage comes, the pads are where the sign says and nobody has to invent the process live, mid-rush, with a room full of guests watching.
Can I still take card payments during an outage?
Often, yes — but check with your own provider rather than assuming. Many card terminals carry their own mobile connection or tolerate a short disconnection and settle later, so the terminal can keep working while the café's wifi is down. Yours may not. It is a two-minute question to your card provider, and it changes what your paper routine needs to say about cards.
Kafe360 editorial team

We build point-of-sale and QR menu software for cafés and restaurants, and we write the guides we wish our customers had before they opened. Try Kafe360 free for 30 days.

internet outagecloud poscafé operationsofflinecontingency planningconnectivity
Share

Opening a venue? Start with a free QR menu, move to the full system when you are ready.

More on this topic

POS and operations

Who Owns Your Café's Data — and How to Get It Out

A café's till system quietly accumulates its most valuable archive: years of sales, the menu and its recipes, guest account balances, stock records. This guide covers what that data actually is, the questions to ask a provider before signing, the monthly export habit that makes provider changes survivable, and what guest data obliges you to handle carefully.

13 Oct8 min read
POS and operations

Getting Through the Café Rush Hour

The rush feels like one problem but is always one of three — orders queueing at the till, drinks queueing at the machine, or tables queueing to pay. This guide walks through finding which one jams first from your own sales curve, the half hour of prep that prevents most of it, who owns what while it happens, and the two numbers that tell you whether it worked.

13 Oct7 min read
POS and operations

Running Takeaway Alongside Table Service

Takeaway money is real money — until it collides with your table service at the till, the kitchen and the pass. This guide separates the two flows, gives takeaway a queue of its own, plans packaging and the handover point, and lists what to fix before the morning rush arrives.

13 Oct8 min read
POS and operations

Splitting the Bill Without Slowing Down the Table

Splitting a bill is where service quietly dies: the table waits, the waiter does arithmetic, the till queues. This guide compares splitting by item, by equal share and by amount, walks a five-guest $86.40 bill through all three, and lists the payment-moment mistakes that cost cafés real money.

13 Oct7 min read

The theory is the easy half.

Every article here describes the trade. Kafe360 runs it — thirty days free on your own menu, no card.