Field notes

POS down? The 15-minute triage before you call anyone

The Golden Gate IT team · July 19, 2026

It's 7:40 on a Friday and the card reader is spinning. Here's the thing that makes the next fifteen minutes calmer: most "POS outages" are not the POS company. They're the network in your back office. Which means the fastest path back to ringing tickets is usually in your building, and it follows an order.

Work this top to bottom. Don't skip ahead.

First, two questions (one minute)

• Does anything else have internet? Put a phone on the venue WiFi, or wiggle the office PC. Internet dead everywhere means network problem. Internet fine elsewhere means POS problem.
• Is it one terminal or all of them? One terminal points at that terminal. All of them points at the network or the platform.

Those two answers route everything below.

If nothing has internet: it's your network

Step 1: look at the lights

Go to the modem and router. No lights or all-red on the modem means the internet service itself. Normal modem lights with a dead network means the router or switch behind it.

Step 2: power-cycle in order

Pull power on the modem, wait thirty seconds, plug it back in, and give it two full minutes to sync. Then the router, then the switch, each with the same patience. Order matters: each box needs the one before it alive first. One round of this clears a large share of small-business outages.

Step 3: check the provider from your phone

On cellular, check your internet provider's outage page or app. If it's a neighborhood outage, no amount of rebooting fixes it, and your energy goes to the next section instead.

Meanwhile: switch to offline mode

Most modern POS platforms can keep taking cards through a short outage, queuing payments until the connection returns. If yours was configured for it, turn it on and keep the line moving while you triage. If you don't know whether yours was configured for it, that's a to-do for Monday, because finding out mid-outage is the expensive way.

If the internet is fine but the POS is not

One terminal down

Reboot that terminal fully. Check its cable seat, or its WiFi if it's wireless (and if your registers are on WiFi, put "wire the registers" on the Monday list too). If you keep a cold spare terminal, this is its moment: swapping hardware turns a dead register into a ten-minute inconvenience.

Every terminal down, internet fine

Check your platform's status page from your phone before touching anything. Cloud POS outages are rare, but they happen, and when it's the platform, the fix is patience plus offline mode, not settings changes. Nothing you reconfigure locally repairs a vendor outage.

What not to do mid-rush

• Don't factory-reset anything. A reset terminal mid-service becomes a setup project instead of a register.
• Don't re-pair payment readers on a hunch. Pairing is where working systems go to die during a panic.
• Don't change WiFi or network settings to "see if it helps." Now there are two problems.
• Don't spend forty minutes on hold with the internet provider while the dining room stalls. That call is your IT provider's job, and they have a faster path.

After service: fix the reasons this keeps happening

One outage is bad luck. A pattern has causes, and they're always the same short list: the free router the internet provider left, everything sharing one flat network, no battery backup on the POS stack, registers on WiFi, and offline mode never configured. The full build-it-right version is in our restaurant IT guide, and the same logic applies to retail counters.

When to stop triaging and call

Give it fifteen minutes or one full round of the steps above, whichever comes first. Past that point you're not triaging, you're gambling with the dinner rush. This is exactly what "business-down" means in our support plans: you can't transact, so the clock and the priority change.

Common questions

Is offline mode safe for taking cards?

It queues payments and settles them when the connection returns, with limits you configure in advance. The tradeoff: a card that would have declined gets discovered at settlement, which is why you set a sane per-transaction cap before you ever need it, and test it on a quiet Tuesday.

Why does our POS drop "randomly" a few times a week?

Random-feeling drops are almost never random. The usual culprits are WiFi congestion during busy hours, a consumer router juggling guests and payments on one network, or a failing switch. The fix is structural: wired terminals, segmented network, business-grade gear.

Should we keep a spare terminal?

If losing a register for a night costs more than a spare terminal, yes. For most multi-register operations the answer is obviously yes; the spare pays for itself the first time hardware dies on a weekend.

The POS vendor blames the network. The internet provider blames the POS. Who's right?

This finger-point is the most expensive phone tree in small business. The structural answer is one team that owns the whole stack, so there's nobody to point at. That's the model we run: one call for everything with a plug.