A connection failure can turn a quiet checkout into a guessing game. Set a short outage routine before it happens, and your team will know what to pause, record, and check when service returns.

A customer is ready to pay, the line has started to grow, and the register suddenly cannot reach the network. Someone taps the payment button again. A coworker reaches for a notepad. The owner asks whether the sale went through. That is how a small connection hiccup can become a much longer cleanup.

The useful move is to decide what your team will do before the screen freezes. A short outage routine should answer three questions: what still works, which payments are safe to accept, and how you will reconcile the record afterward. It should not assume every point-of-sale system can take card payments without internet. Offline features vary by provider, device, settings, and payment type, so check your own system's instructions before relying on them.

First, find out what actually stopped

"The internet is down" can mean several different things. One register may have lost its Wi-Fi connection while the rest of the shop is online. The router may be working but a payment service could be having trouble. Or the whole building may have lost connectivity. The first response is a quick check, not a burst of button tapping.

Have one person look at the device's connection indicator and, if practical, check whether another device can load a familiar website. Ask a manager to check the internet equipment or service status using the shop's normal process. Do not restart, sign out of, or reinstall a payment app just to see what happens while a transaction may be pending. Those actions can interrupt systems that have work waiting to sync.

Give the team a simple phrase to use with customers, such as, "Our register is having a connection problem. I am checking whether your payment went through before trying again." It is honest, buys a little time, and avoids the awkward double-charge conversation later.

Know your payment choices before the rush

Write down the approved options for your business, rather than leaving each cashier to invent one. Depending on your setup, the options might be to wait briefly, use a second connected register, accept cash, or use an offline card feature that your provider supports. If none of those is available, pausing the sale may be safer than promising that a card payment will work later.

Offline card processing is not simply a paper version of a normal card approval. Some systems store a transaction and attempt to submit it after the device reconnects. Until that happens, the payment may not have a final approval. A card can later be declined, expire, or be disputed, and the merchant may carry the loss. Rules and deadlines differ, so the exact steps must come from your payment provider. Do not tell staff that an offline payment is guaranteed or approved unless the provider says so.

Make the decision rule plain. For example: use offline card processing only on the approved device, only when the feature is enabled, and only after the manager confirms the team's procedure. If staff cannot verify those conditions, use another approved tender or pause. A little delay is frustrating. A mystery charge is worse.

Keep a small outage log

If your system cannot record a sale at the time, keep a numbered paper log or another manager-approved record. Use one sheet for the whole incident, not loose scraps from three pockets and a receipt printer. Record enough to identify the sale and reconcile it later, but do not write down full card numbers, security codes, or other sensitive payment details.

• Note the date and approximate time, register or lane, items and quantities, total, and tender type.
• Mark whether the customer received the goods and whether payment was accepted through an approved offline method.
• Record a receipt or order reference if one exists, plus the staff initials and manager approval when required.
• Give each manual entry a simple incident sequence number so nobody has to match records by handwriting alone.

Keep the record in a controlled place and tell the next shift where it is. If the outage crosses a shift change, ask the outgoing employee and the manager to review the last entry together. That short handoff is much easier than asking the closing cashier to reconstruct a busy hour from memory.

Do not enter the same sale twice

When the connection returns, resist the urge to re-ring every item on the paper list. First look for transactions that may have synced, and check the device or provider's transaction view. Follow the provider's instructions for confirming pending, completed, failed, or declined payments. A sale that appears on a pending list is not necessarily settled, but it may be enough to tell you not to create a duplicate record.

Then reconcile one line at a time. Match the manual log to the register, payment record, and cash drawer. If a card payment failed, use the provider's approved process to contact the customer or collect another payment. If a cash sale was written down but never entered, record it according to your bookkeeping and POS procedures. If you find a duplicate, do not quietly erase one side and hope nobody notices. Ask a manager to document the correction so the drawer and sales report still tell the same story.

A simple reconciliation table can help: incident number, original note, system transaction found, action taken, and person who checked it. The table is not extra paperwork for its own sake. It gives the next person a clear answer to the question, "What happened to this sale?"

Practice the boring version

Pick a quiet moment to walk the team through a pretend outage. Use a sample order, point to the approved backup options, and show where the paper log lives. Make sure everyone knows who can approve offline card use, who checks the connection, and who closes the incident. If you have more than one register, decide which one is the backup and how staff will tell customers about the switch.

After the exercise, check the details that tend to go stale: provider instructions, device settings, manager contact, and the location of the log. A routine that says "ask Maria" is not much help after Maria changes shifts. Name the role, not only the person.

When service comes back, have a manager announce that the system is online, then assign the reconciliation instead of assuming it will happen between customers. Keep the incident log until every line has an outcome, and store or dispose of it under your normal recordkeeping rules. If outages keep happening, note their times and what failed. That information can help you discuss the issue with your internet or payment provider.

A register outage is disruptive, but it does not need to become a second problem at closing. Decide what is safe to accept, keep a tidy record of anything the system could not capture, and reconcile before anyone re-enters a sale. If you are reviewing the tools your team uses at the counter, you can download M&M POS and see whether it fits your shop's workflow.

Direct URL: https://mmpos.app/download